
Mcp Openapi
io.github.infoinlet-marketplacePublished by GitHub account infoinlet-marketplacev0.1.1Updated Oct 24, 2026
Turn any OpenAPI/Swagger spec into MCP tools — each operation an SSRF-guarded tool.
Overview
Converts an OpenAPI or Swagger specification into MCP tools, exposing each API operation as a callable tool with SSRF protection.
- What you can do
- This local MCP server reads an OpenAPI or Swagger specification and generates one MCP tool per API operation, so an assistant can call those HTTP endpoints directly. It is described as SSRF-guarded, meaning requests are filtered to reduce server-side request forgery risk. The manifest lists no tools, so the exact generated tool names and parameters depend on the spec you supply.
- When to use it
- Useful when you have an OpenAPI or Swagger spec for an HTTP API and want an assistant to call its operations without writing a custom MCP server for each endpoint. Best suited to desktop setups where the API is reachable from the local machine.
- Requirements
- Runs as a local process over stdio, installed from the npm package @infoinlet/mcp-openapi, so Node.js and npm are needed. Desktop only; no web execution. The manifest declares no authentication, environment variables, or headers, but the target API may still require its own credentials.
Installation
In SourceWeft
- Open Mcp Openapi in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v0.1.1LatestSep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.