# MCP API Translator (npm · mcp-api-translator)

Turn OpenAPI / Postman specs into runnable MCP servers, or serve any API as live MCP tools.

- Trust score: 89/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `mcp-api-translator`: 89/100 (this document), [markdown](https://verifymcp.io/servers/krishgok-mcp-api-translator/mcp-api-translator.md), [page](https://verifymcp.io/servers/krishgok-mcp-api-translator/mcp-api-translator)

## Channel facts

- Registry: `npm`
- Package: `mcp-api-translator`
- Version: `0.4.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 35 of 111 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to krishgok/mcp-api-translator).
  - Clear OSI-approved license (AGPL-3.0-or-later).
  - Actively maintained (last published 25 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 99/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 97% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add krishgok-mcp-api-translator -- npx -y mcp-api-translator
```

### Cursor

```json
{
  "mcpServers": {
    "krishgok-mcp-api-translator": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-api-translator"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "krishgok-mcp-api-translator": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-api-translator"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add krishgok-mcp-api-translator -- npx -y mcp-api-translator
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "krishgok-mcp-api-translator": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "mcp-api-translator"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add krishgok-mcp-api-translator --command npx --arg -y --arg mcp-api-translator
```

### Hermes

```yaml
mcp_servers:
  krishgok-mcp-api-translator:
    command: "npx"
    args: ["-y", "mcp-api-translator"]
```

### Netclaw

```json
{
  "McpServers": {
    "krishgok-mcp-api-translator": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "mcp-api-translator"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add krishgok-mcp-api-translator -t stdio -c npx -a -y mcp-api-translator
```

### Other

```json
{
  "mcpServers": {
    "krishgok-mcp-api-translator": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-api-translator"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 89, +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.

### 2026-11-03 (score 88, +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.

### 2026-11-01 (score 87, +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.

### 2026-10-30 (score 86, +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.

### 2026-10-28 (score 85, +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.

### 2026-10-26 (score 84, +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.

### 2026-10-23 (score 83, +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.

### 2026-10-22 (score 82, +4)

- [functional improvement] Stability: unverified → 0.27

## MCP tools (4)

### `analyze_spec` (~170 tokens)

Analyze API spec (preview)

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.

Input parameters:

- `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).

### `generate_mcp_server` (~366 tokens)

Generate MCP server

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.

Input parameters:

- `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, required): 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.

### `extend_mcp_server` (~285 tokens)

Extend an existing generated MCP server

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.

Input parameters:

- `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, required): 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.

### `list_supported_features` (~25 tokens)

List supported features

Report the input formats, auth schemes, transports, and limits this tool supports.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/krishgok-mcp-api-translator/mcp-api-translator#diagnostics

## Score history

- 2026-11-05: 89
- 2026-11-04: 88
- 2026-11-03: 88
- 2026-11-02: 87
- 2026-11-01: 87
- 2026-10-31: 86
- 2026-10-30: 86
- 2026-10-29: 85
- 2026-10-28: 85
- 2026-10-27: 84
- 2026-10-26: 84
- 2026-10-25: 83
- 2026-10-24: 83
- 2026-10-23: 83
- 2026-10-22: 82
- 2026-10-21: 78
- 2026-10-20: 78
- 2026-10-19: 78
- 2026-10-18: 78
- 2026-10-17: 78
- 2026-10-16: 78
- 2026-10-15: 78
- 2026-10-14: 78
- 2026-10-13: 49
- 2026-10-12: 49

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/mcp-api-translator
- Socket report: https://socket.dev/npm/package/mcp-api-translator
- Repository: https://github.com/krishgok/mcp-api-translator
- Changelog RSS feed: https://verifymcp.io/servers/krishgok-mcp-api-translator/mcp-api-translator.xml
- Changelog JSON feed: https://verifymcp.io/servers/krishgok-mcp-api-translator/mcp-api-translator.json
- HTML version of this page: https://verifymcp.io/servers/krishgok-mcp-api-translator/mcp-api-translator