io.github.saurav61091/mcp-openapi-runner
io.github.saurav61091/mcp-openapi-runner
Is the io.github.saurav61091/mcp-openapi-runner MCP server down? No. It is up and needs env, probed 2026-10-31.
Turn any OpenAPI 3.x spec into callable MCP tools for Claude. No custom integration code needed.
needs env probed 2026-11-14 · unchanged since 2026-10-31
MCP error -32000: Connection closed Error: --spec <url-or-path> is required Run with --help for usage information
- Run it
- npx -y mcp-openapi-runner@1.0.1 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/saurav61091/mcp-openapi
- Registry
- active, updated 2026-03-18 · registry entry
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- Standup from your activity io.github.sathvic-kollu/standup-mcp · alive
- io.github.satoshkin-dev/satoshkin-aml-mcp · alive
- io.github.sauliusbeconis/axongate · crashed on start
- Search Console MCP io.github.saurabhsharma2u/search-console-mcp · alive
- io.github.savhascelik/meta-api-mcp-server · alive
- io.github.saxenakapil/setup-doctor · alive
- Sayba Skill Market io.github.saybanet/sayba-skill-market · alive
- Page Scanner io.github.sbd530/page-scanner · alive
Servers that mention openapi.
- HAPI MCP Server ai.com.mcp/hapi-mcp · needs your URL
- ai.enginy/mcp · needs auth
- Kaiva Bridge ai.kaiv/bridge · not MCP
- Data APIs SEC Event Intelligence API com.data-apis.api/sec-event-intelligence · server error
- com.htagai/htag-docs · alive
- Routebase dev.routebase/routebase · needs auth
- Typeship dev.typeship/typeship · needs auth
- AGS API io.github.AccelByte/ags-api-mcp-server · needs your URL
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server exits because an environment variable is missing. The probe starts the package without secrets. A server that starts without secrets and asks for them on the first tool call is measured.