# io.github.thisis-najeeb/api-test-mcp (npm · api-test-mcp)

Call the real API and check the response against your OpenAPI spec.

- Trust score: 79/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-24

## Components

- npm · `api-test-mcp`: 79/100 (this document), [markdown](https://verifymcp.io/servers/thisis-najeeb-api-test-mcp/api-test-mcp.md), [page](https://verifymcp.io/servers/thisis-najeeb-api-test-mcp/api-test-mcp)

## Channel facts

- Registry: `npm`
- Package: `api-test-mcp`
- Version: `1.0.2`
- 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-09-24.

- **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.
  - 37 of 105 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 23 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1053 tokens (~131/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 82/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 45% 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 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 io.github.thisis-najeeb/api-test-mcp server?

io.github.thisis-najeeb/api-test-mcp runs locally as an npm package, launched with npx -y api-test-mcp. 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 thisis-najeeb-api-test-mcp -- npx -y api-test-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "thisis-najeeb-api-test-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "api-test-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "thisis-najeeb-api-test-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "api-test-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add thisis-najeeb-api-test-mcp -- npx -y api-test-mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add thisis-najeeb-api-test-mcp --command npx --arg -y --arg api-test-mcp
```

### Hermes

```yaml
mcp_servers:
  thisis-najeeb-api-test-mcp:
    command: "npx"
    args: ["-y", "api-test-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "thisis-najeeb-api-test-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "api-test-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add thisis-najeeb-api-test-mcp -t stdio -c npx -a -y api-test-mcp
```

### Other

```json
{
  "mcpServers": {
    "thisis-najeeb-api-test-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "api-test-mcp"
      ]
    }
  }
}
```

## 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-09-23 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-21 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 75, +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-09-12 (score 74, +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-09-10 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-08 (score 72, +4)

- [functional improvement] Stability: unverified → 0.27

## MCP tools (8)

### `load_api_spec` (~84 tokens)

Load an OpenAPI/Swagger spec

Load and fully dereference an OpenAPI/Swagger spec from a URL or local file path (JSON or YAML). Call this first. Returns the API title, servers, and every documented endpoint.

Input parameters:

- `source` (string, required): URL or local file path to the OpenAPI/Swagger document, e.g. https://petstore3.swagger.io/api/v3/openapi.json

### `list_endpoints` (~24 tokens)

List loaded endpoints

List every endpoint (method + path) from the currently loaded API spec.

### `call_endpoint` (~196 tokens)

Call a real API endpoint

Make an actual HTTP call to a documented endpoint and return the real status, headers, and body. Does not validate the response — use test_endpoint if you also want schema validation.

Input parameters:

- `auth` (object): Auth preset applied to the request. Examples: {"type":"bearer","token":"..."}, {"type":"apiKey","in":"header","name":"X-API-Key","value":"..."}, {"type":"basic","username":"...","password":"..."}
- `baseUrl` (string): Override the spec's default server URL
- `body`
- `headers` (object)
- `method` (string, required): HTTP method, e.g. GET, POST
- `path` (string, required): The documented path template, e.g. /pets/{id}
- `pathParams` (object)
- `queryParams` (object)
- `timeoutMs` (number): Abort the request after this many milliseconds.

### `validate_response` (~54 tokens)

Validate a response against the spec

Check a response body against the JSON schema documented for a given method + path + status code.

Input parameters:

- `method` (string, required)
- `path` (string, required)
- `responseBody` (required)
- `status` (number, required)

### `test_endpoint` (~176 tokens)

Call and validate an endpoint in one step

Call a documented endpoint with real parameters, then validate the real response against its documented schema. Returns pass/fail plus the specific mismatches found. This is the main tool for 'does this endpoint actually work as documented'.

Input parameters:

- `auth` (object): Auth preset applied to the request. Examples: {"type":"bearer","token":"..."}, {"type":"apiKey","in":"header","name":"X-API-Key","value":"..."}, {"type":"basic","username":"...","password":"..."}
- `baseUrl` (string)
- `body`
- `headers` (object)
- `method` (string, required)
- `path` (string, required)
- `pathParams` (object)
- `queryParams` (object)
- `timeoutMs` (number): Abort the request after this many milliseconds.

### `run_all_tests` (~210 tokens)

Run a contract-test pass across the whole API

Best-effort run across every GET endpoint that needs no required parameters: calls each one for real and validates the response against the documented schema. Endpoints needing parameters are listed as skipped (use test_endpoint for those individually), and DELETE/OPTIONS/HEAD are never auto-run. Set includeMutating: true to also auto-generate example params/bodies from the schema and attempt POST/PUT/PATCH endpoints — off by default because that can create or modify real data on the live API.

Input parameters:

- `auth` (object): Auth preset applied to the request. Examples: {"type":"bearer","token":"..."}, {"type":"apiKey","in":"header","name":"X-API-Key","value":"..."}, {"type":"basic","username":"...","password":"..."}
- `baseUrl` (string)
- `includeMutating` (boolean): Attempt POST/PUT/PATCH with auto-generated example data. Default false — may write real data.
- `timeoutMs` (number)

### `check_health` (~179 tokens)

Ping a set of endpoints and report reachability/latency

One-shot health check: calls each given endpoint (or, if none given, every parameter-free GET in the loaded spec) and reports whether it responded, its status code, and latency. Useful for a quick 'is the API up' pass, e.g. before a demo or as part of CI.

Input parameters:

- `auth` (object): Auth preset applied to the request. Examples: {"type":"bearer","token":"..."}, {"type":"apiKey","in":"header","name":"X-API-Key","value":"..."}, {"type":"basic","username":"...","password":"..."}
- `baseUrl` (string)
- `endpoints` (array): Explicit list to check. Defaults to every parameter-free GET endpoint in the loaded spec.
- `timeoutMs` (number): Per-endpoint timeout in ms. Default 5000.

### `diff_api_specs` (~130 tokens)

Diff two versions of an OpenAPI spec for breaking changes

Compare two OpenAPI/Swagger specs (each a URL or local file path — e.g. an old tag vs. the current main) and report added/removed endpoints plus request/response schema changes, flagging which ones are likely to break existing clients (removed fields, newly-required fields, type changes, removed enum values) versus safe additive changes. Does not affect the spec currently loaded for the other tools.

Input parameters:

- `sourceA` (string, required): The 'before' spec — URL or local file path.
- `sourceB` (string, required): The 'after' spec — URL or local file path.

## Diagnostics

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

## Score history

- 2026-09-24: 79
- 2026-09-23: 79
- 2026-09-22: 78
- 2026-09-21: 78
- 2026-09-20: 77
- 2026-09-19: 77
- 2026-09-18: 76
- 2026-09-17: 76
- 2026-09-16: 75
- 2026-09-15: 75
- 2026-09-14: 75
- 2026-09-13: 74
- 2026-09-12: 74
- 2026-09-11: 73
- 2026-09-10: 73
- 2026-09-09: 72
- 2026-09-08: 72
- 2026-09-07: 68
- 2026-09-06: 68
- 2026-09-05: 68
- 2026-09-04: 68
- 2026-09-03: 68
- 2026-09-02: 68
- 2026-09-01: 68
- 2026-08-31: 68

## Common questions

### What is the io.github.thisis-najeeb/api-test-mcp server?

io.github.thisis-najeeb/api-test-mcp is listed in the public MCP registry as io.github.thisis-najeeb/api-test-mcp. Call the real API and check the response against your OpenAPI spec. This page covers its npm package (api-test-mcp).

### Is the io.github.thisis-najeeb/api-test-mcp server safe to use?

io.github.thisis-najeeb/api-test-mcp scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 September 2026. It declares no install or post-install scripts. 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 io.github.thisis-najeeb/api-test-mcp server expose?

io.github.thisis-najeeb/api-test-mcp exposes 8 tools: load_api_spec, list_endpoints, call_endpoint, validate_response, test_endpoint, and 3 more. Their descriptions and schemas cost roughly 1,053 tokens of context every time the server is loaded.

### Is the io.github.thisis-najeeb/api-test-mcp server still maintained?

io.github.thisis-najeeb/api-test-mcp is still listed as active in the MCP registry. We last reached this channel on 24 September 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 io.github.thisis-najeeb/api-test-mcp server under?

io.github.thisis-najeeb/api-test-mcp declares the MIT 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/api-test-mcp
- Socket report: https://socket.dev/npm/package/api-test-mcp
- Repository: https://github.com/thisis-najeeb/api-test-mcp
- Changelog RSS feed: https://verifymcp.io/servers/thisis-najeeb-api-test-mcp/api-test-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/thisis-najeeb-api-test-mcp/api-test-mcp.json
- HTML version of this page: https://verifymcp.io/servers/thisis-najeeb-api-test-mcp/api-test-mcp