mcp-openapi-server (ivo-toby/mcp-openapi-server) is an MCP server listed on the M8ven Trust Index. It scores 55 out of 100, grade D. It declares 3 tools. No publisher has claimed this listing.

D
Caution
55/100

mcp-openapi-server

MCP Server (Model Context Protocol) for turning OpenAPI specifications into a MCP Resource

ivo-toby/mcp-openapi-server· npm: @ivotoby/openapi-mcp-server· listed on npm

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

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

ivo-toby

Source: npm · also listed on github_code, ModelScope

Is this your MCP?

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

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
🚨
Known vulnerabilities in dependencies: 1 critical, 12 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
// known CVEs in dependencies1 critical12 high6 medium13 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

criticalvitest@3.2.4GHSA-5xrq-8626-4rwp

When Vitest UI server is listening, arbitrary file can be read and executed

high@modelcontextprotocol/sdk@1.24.1GHSA-345p-7cg4-v4c7

@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse

high@modelcontextprotocol/sdk@1.24.1GHSA-8r9q-7v3j-jr4g

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

highaxios@1.13.6GHSA-35jp-ww65-95wh

axios Vulnerable to Full Man-in-the-Middle via Prototype Pollution Gadget in `config.proxy`

highaxios@1.13.6GHSA-3g43-6gmg-66jw

axios Vulnerable to Credential Theft and Response Hijacking via Prototype Pollution Gadget in Config Merge

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configAPI_BASE_URLThe base URL of your API
configAPI_HEADERSComma-separated key:value pairs for API authentication headers
configCA_CERT_PATHPath to custom CA certificate PEM file for private/internal CAs
configCLIENT_CERT_PATHPath to client certificate PEM file for mutual TLS
configCLIENT_KEY_PASSPHRASEPassphrase for an encrypted client private key
configCLIENT_KEY_PATHPath to client private key PEM file for mutual TLS
configDISABLE_ABBREVIATIONDisable name optimization (this could throw errors when name is > 64 chars)
configENDPOINT_PATHEndpoint path for HTTP transport (default: "/mcp")
configHTTP_HOSTHost for HTTP transport (default: "127.0.0.1")
configHTTP_PORTPort for HTTP transport (default: 3000)
configOPENAPI_SPEC_FROM_STDINSet to "true" to read OpenAPI spec from standard input
configOPENAPI_SPEC_INLINEProvide OpenAPI spec content directly as a string
configOPENAPI_SPEC_PATHURL or path to your OpenAPI specification
configPROMPTS_INLINEProvide prompts directly as JSON string
configPROMPTS_PATHPath or URL to prompts JSON/YAML file
configREJECT_UNAUTHORIZEDWhether to reject untrusted server certificates (default: true)
configRESOURCES_INLINEProvide resources directly as JSON string
configRESOURCES_PATHPath or URL to resources JSON/YAML file
configSERVER_NAMEName for the MCP server (default: "mcp-openapi-server")
configSERVER_VERSIONVersion of the server (default: "1.0.0")
configTOOLS_MODETools loading mode: "all" (load all endpoint-based tools), "dynamic" (load only meta-tools), or "explicit" (load only tools specified in includeTools) (default: "all")
// quality suggestions

Tool 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

3/3 tools missing one or more hints — list-api-endpoints (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get-api-endpoint-schema (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); invoke-api-endpoint (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint). 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.

Production dependencies are patched

0 critical, 12 high severity in production deps — @modelcontextprotocol/sdk@1.24.1 (high), @modelcontextprotocol/sdk@1.24.1 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Dev dependencies

1 critical/high in dev-only deps (does not ship to users)

Upgrade dev dependencies when convenient.

Dependency freshness

1/4 production deps stale: openapi-types@2023-05-24 (3.3y)

Domain consistency

npm scope @ivotoby doesn't match GitHub owner ivo-toby

Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.

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.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 5 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/ivo-toby/mcp-openapi-server?variant=verified)](https://m8ven.ai/mcp/ivo-toby/mcp-openapi-server)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 5cc37bc4df8de5bf1d1327a1017dcfd1d2165f3f
code hash: f7ba8561070ebee527737f9759b15765dc7585d1fbe13f1e13ce19a3c0ce5c3b
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

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
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client