MCP Hub
Back to servers

VibeGuard MCP

Enables policy-style auditing of content through the audit_vibe MCP tool to enforce configurable guardrails. Supports both local stdio and serverless Streamable HTTP deployment via Vercel for flexible integration with MCP clients.

glama
Updated
Apr 4, 2026

VibeGuard MCP

Policy-style checks exposed as an MCP tool (audit_vibe).

Local (stdio, Cursor)

npm install
npm start

Point Cursor at index.js with the node command (see your global mcp.json).

Vercel (Streamable HTTP)

Deploy with Root Directory set to this folder (vibeguard-mcp), or from here:

npx vercel
  • MCP endpoint (after deploy): https://<your-deployment>.vercel.app/mcp
    (vercel.json rewrites /mcp/api/mcp.)

Configure your MCP client for Streamable HTTP to that URL (same transport family as the SDK’s remote servers). This deployment is stateless (sessionIdGenerator: undefined), which fits serverless.

Security: The HTTP endpoint is public unless you add Vercel authentication, a custom gate in api/mcp.js, or a reverse proxy. Do not expose internal guardrails to the open internet without controls.

Layout

PathRole
index.jsstdio server for local tools
api/mcp.jsVercel function, Streamable HTTP
lib/handlers.jsShared tool registration

Reviews

No reviews yet

Sign in to write a review