MCP API Guardian MCP server
Local OpenAPI contract and breaking-change checks for AI agents.
0 stars
Reviews
Write oneNobody has reviewed MCP API Guardian yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
MCP API Guardian tools (2)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
audit_openapiStatic OpenAPI 3.0/3.1 lint and authentication declaration review. Does not call endpoints.
compare_openapiFind selected breaking changes between two OpenAPI documents; not exhaustive schema compatibility.
Public scan report
scanner v0.1.10 · 2026-10-09 · same rubric, same numbers if you re-run it
- Code scan5 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 0 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Install MCP API Guardian in Claude Code, Cursor or VS Code
Runs npx -y mcp-api-guardian on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add mcp-api-guardian -- npx -y mcp-api-guardian
What the publisher says
From the MCP API Guardian repository's README, as published. We do not edit it. Read it on GitHub
MCP API Guardian
Local OpenAPI contract checks for AI coding agents. MVP 0.1.0, no runtime dependencies, Node.js 22+.
Transport: newline-delimited JSON-RPC over stdio, with the initialize-based MCP protocol family through 2025-11-25. The newer 2026-07-28 stateless protocol is not implemented. Test with your target client before deployment. Protocol reference: https://modelcontextprotocol.io/specification/2025-11-25/basic/transports
Install in your AI client
Works with any MCP client over stdio; no account or API key needed for the local server.
Claude Code
claude mcp add api-guardian -- npx -y mcp-api-guardianCodex CLI
codex mcp add api-guardian -- npx -y mcp-api-guardianClaude Desktop, Cursor, Windsurf, Cline, Gemini CLI — add to the client's MCP config (claudedesktopconfig.json, ~/.cursor/mcp.json, ~/.codeium/windsurf/mcp_config.json, Cline MCP settings, ~/.gemini/settings.json):
{
"mcpServers": {
"api-guardian": {
"command": "npx",
"args": [
"-y",
"mcp-api-guardian"
]
}
}
}VS Code / GitHub Copilot — .vscode/mcp.json:
{
"servers": {
"api-guardian": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"mcp-api-guardian"
]
}
}
}Zed — settings.json:
{
"context_servers": {
"api-guardian": {
"command": "npx",
"args": [
"-y",
"mcp-api-guardian"
]
}
}
}Run from source
npm test
npm startAdd to an MCP client's configuration, replacing the absolute path:
{"mcpServers":{"api-guardian":{"command":"node","args":["/absolute/path/mcp-api-guardian/src/server.js"]}}}Tools
- audit_openapi({spec}): checks selected contract errors, references, operation IDs, required path parameters, public operations and risky authentication declarations.
- compare_openapi({before, after}): detects removed operations, changed operation IDs, added inline required parameters, newly required request bodies, removed response codes and changed authentication requirements.
Pass parsed JSON OpenAPI 3.0.x or 3.1.x documents as objects. YAML parsing, filesystem access, external reference fetching and live HTTP probes are not implemented. No credentials or source documents leave the process.
This is a targeted linter, not a complete OpenAPI validator. Schema compatibility (including request versus response variance), composed schemas and referenced parameter comparisons require a later release. Public endpoints may be intentional; warnings are not proof of a vulnerability. Reports explicitly state coverage.
Packaging
npm run check
npm test
npm packClients can use npx -y mcp-api-guardian.
Hosted path (quotas via control plane)
The local stdio MCP server above stays fully useful without an account or network. Quotas are enforced only by a separate hosted HTTP process that reserves units on mcp-control-plane before running the same analysis core.
# Terminal 1 — control plane (see its README for ADMIN_TOKEN)
node --env-file=.env src/server.js # in mcp-control-plane
# Terminal 2 — hosted api-guardian
cp .env.example .env # set CONTROL_PLANE_URL
npm run start:hostedBootstrap a customer key with the control-plane admin API (POST /v1/admin/accounts, POST /v1/admin/keys). Then:
Customer routes require Authorization: Bearer mcp…. On success the response includes report and usage. Over quota returns 429 with { "error": "quotaexceeded" } and does not run analysis. Default bind: 127.0.0.1:3100. Production needs an HTTPS reverse proxy.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
MCP API Guardian: common questions
- Is MCP API Guardian MCP server safe?
- Yes, by our scan: it is graded A (92/100). Read the MCP API Guardian safety report
- How do I install MCP API Guardian?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does MCP API Guardian need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is MCP API Guardian maintained?
- The last commit was 4 days ago (2026-10-09). The latest release is v0.1.1.