MCP API Translator
NPM · MCP-API-TRANSLATOR
Turn OpenAPI / Postman specs into runnable MCP servers, or serve any API as live MCP tools.
Available components
Last scanned (19 minutes ago)
Scores higher than 93% of npm servers
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 35 of 111 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to krishgok/mcp-api-translator). View diagnostics → Pass
- Clear OSI-approved license (AGPL-3.0-or-later).Pass
- Actively maintained (last published 25 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 846 tokens (~211/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 97% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +4
- Stability: unverified → 0.27 ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/mcp-api-translator@0.4.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | krishgok/mcp-api-translator |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/krishgok/mcp-api-translator/.github/workflows/release.yml@refs/tags/v0.4.1 |
| Rekor log index | 3197050154 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:759e792e40a3dd1a1655b37ee169ef009e9feed846816e353a41c18a731687fe499ef2483b649428ce13b650182fbf7c7babd58a366ecfb11379545c1 |
Background: How many MCP packages publish verified provenance →
Dependencies 111 packages
| Packages resolved | 111 |
|---|---|
| Stale | 35 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
analyze_spec Analyze API spec (preview) ~170
Parse an OpenAPI or Postman spec and preview the MCP tools that would be generated, without writing any files. Use this to curate (filter/inspect) before generating.
| Name | Type | Req | Description |
|---|---|---|---|
| excludeOperations | array | – | Drop operations by operationId, tool name, or tag. |
| format | string | – | Force a format; defaults to auto-detect. |
| includeTags | array | – | Keep only operations with these tags. |
| methods | array | – | Keep only these HTTP methods, e.g. [GET, POST]. |
| pathGlob | string | – | Keep only matching paths, e.g. "/v1/**". |
| spec | string | – | Inline spec text (OpenAPI or Postman; JSON or YAML). |
| specPath | string | – | Path to a local spec file (JSON or YAML). |
No output schema declared.
No examples provided.
extend_mcp_server Extend an existing generated MCP server ~285
Append the operations from another spec to an already-generated project (identified by its .mcp-translator.json manifest). Idempotent: operations already present are skipped, and hand-edited tool files are preserved unless force is set. Enables aggregating multiple APIs into one MCP server.
| Name | Type | Req | Description |
|---|---|---|---|
| auth | – | – | Auth to use when the spec declares no security schemes of its own. Applied only to operations whose own security list is empty; credentials are read from env vars as usual. |
| excludeOperations | array | – | Drop operations by operationId, tool name, or tag. |
| force | boolean | – | Overwrite existing tool files of the same name. |
| format | string | – | Force a format; defaults to auto-detect. |
| includeTags | array | – | Keep only operations with these tags. |
| methods | array | – | Keep only these HTTP methods, e.g. [GET, POST]. |
| pathGlob | string | – | Keep only matching paths, e.g. "/v1/**". |
| projectDir | string | yes | Path to an existing generated project. |
| spec | string | – | Inline spec text (OpenAPI or Postman; JSON or YAML). |
| specPath | string | – | Path to a local spec file (JSON or YAML). |
| toolCatalog | boolean | – | Also write tool-catalog.json; defaults to refreshing it if the project has one. |
No output schema declared.
No examples provided.
generate_mcp_server Generate MCP server ~366
Generate a complete, runnable TypeScript MCP server project from an OpenAPI or Postman spec. Writes the project to outputDir. Use force to overwrite a non-empty directory.
| Name | Type | Req | Description |
|---|---|---|---|
| auth | – | – | Auth to use when the spec declares no security schemes of its own. Applied only to operations whose own security list is empty; credentials are read from env vars as usual. |
| excludeOperations | array | – | Drop operations by operationId, tool name, or tag. |
| force | boolean | – | Overwrite a non-empty / existing project. |
| format | string | – | Force a format; defaults to auto-detect. |
| includeTags | array | – | Keep only operations with these tags. |
| language | string | – | Output language. Defaults to typescript. |
| methods | array | – | Keep only these HTTP methods, e.g. [GET, POST]. |
| outputDir | string | yes | Directory to write the generated project into. |
| pathGlob | string | – | Keep only matching paths, e.g. "/v1/**". |
| pythonVariant | string | – | Python server flavor (requires language: python): the low-level MCP SDK (default) or FastMCP. Both serve the same raw JSON-Schema tool inputs. |
| serverName | string | – | npm/package name; defaults from the API title. |
| serverVersion | string | – | – |
| spec | string | – | Inline spec text (OpenAPI or Postman; JSON or YAML). |
| specPath | string | – | Path to a local spec file (JSON or YAML). |
| toolCatalog | boolean | – | Also write tool-catalog.json (name/summary/tags per tool) for discovery layers. |
| transport | string | – | Transport(s) to generate (TypeScript only). Defaults to stdio. |
No output schema declared.
No examples provided.
list_supported_features List supported features ~25
Report the input formats, auth schemes, transports, and limits this tool supports.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the MCP API Translator server?
MCP API Translator runs locally as an npm package, launched with npx -y mcp-api-translator. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mcp-api-translator
claude mcp add krishgok-mcp-api-translator -- npx -y mcp-api-translator
What is the MCP API Translator server?
MCP API Translator is listed in the public MCP registry as io.github.krishgok/mcp-api-translator. Turn OpenAPI / Postman specs into runnable MCP servers, or serve any API as live MCP tools. This page covers its npm package (mcp-api-translator).
Is the MCP API Translator server safe to use?
MCP API Translator scores 89 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the MCP API Translator server expose?
MCP API Translator exposes 4 tools: analyze_spec, generate_mcp_server, extend_mcp_server, list_supported_features. Their descriptions and schemas cost roughly 846 tokens of context every time the server is loaded.
Is the MCP API Translator server still maintained?
MCP API Translator is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the MCP API Translator server under?
MCP API Translator declares the AGPL-3.0-or-later licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.