SpecBridge MCP (heecheon92/specbridge-mcp) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: there is no public source to read and no endpoint we can reach, so there is nothing for us to inspect. No publisher has claimed this listing.
A clone-and-own MCP server that exposes OpenAPI/Huma contract intelligence to AI agents by turning API specifications into deterministic endpoint metadata, schemas, validation facts, and TypeScript declarations.
Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.
How we verified
Verified is a snapshot. Live keeps it current, and builds your track record.
⚡ Connect GitHub → continuous verification on every pushwhy connect →Who stands behind it
heecheon92
Source: Glama
Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →
Install from
M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.
Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.
yaml is vulnerable to Stack Overflow via deeply nested YAML collections
DEFAULT_BACKEND_IDselects the default backend. If unset, SpecBridge uses swagger-petstore.MCP_HTTP_HOSTHTTP bind hostMCP_HTTP_PATHMCP endpoint path, such as /mcpMCP_HTTP_PORTMCP_HTTP_STATELESSset to true for stateless HTTP modeMCP_TRANSPORTstdio or httpOPENAPI_BACKENDSAlternatively, point OPENAPI_BACKENDS_FILE at another JSON file or set directly.OPENAPI_BACKENDS_FILEAlternatively, point at another JSON file or set OPENAPI_BACKENDS directly.OPENAPI_CACHE_TTL_MSin-memory spec cache TTLOPENAPI_FETCH_TIMEOUT_MSfetch timeout for spec loadingPORTTool annotations
No tools have read-only/destructive annotations
Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.
All four hints declared on every tool
6/6 tools missing one or more hints — list_backends (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); load_openapi_spec (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_api_endpoints (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +3 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.
For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.
Tool inputs are validated
5/6 tool handlers declare input schemas (83%)
Declare an inputSchema with zod/joi/yup on every tool definition.
Tool handlers catch errors
Only 1/6 tool handlers wrap calls in try/catch (17%)
Wrap each tool handler body in try/catch and return a structured error response.
License file
No license file
Add a LICENSE file (MIT, Apache-2.0, etc.).
Tests exist
No test files found
Add tests that exercise each declared tool.
Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.
[](https://m8ven.ai/mcp/heecheon92-specbridge-mcp-yysnf9)?variant=verified to the badge URL.Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.
https://m8ven.ai/api/mcp/tool-check