Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.thisis-najeeb/api-test-mcp

NPM · API-TEST-MCP

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

Available components

0 this week 82 Trust /100

Last scanned (14 hours ago)

Scores higher than 71% of npm servers

Category Testing and QA

Trust breakdown (7 categories)

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
  • 38 of 103 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability72
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage82
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 45% 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 16 Nov 26 0
    • Stability: 0.97 → pass security
  • 15 Nov 26 0
    • Stability: pass → 0.97 functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 +1

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

  • 6 Nov 26 +1

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

  • 4 Nov 26 −2
    • Stability: pass → 0.83 functional
  • 29 Oct 26 0
    • Stability: 0.97 → pass security
  • 28 Oct 26 0
    • Stability: pass → 0.97 functional
Diagnostics

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 21 Nov 2026 · Analysed npm/api-test-mcp@1.0.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 103 packages
Packages resolved 103
Stale 38
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 8 exposed · ~1,053 tokens

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 →

Tool Tokens
call_endpoint ~196

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.

NameTypeReqDescription
authobject–Auth preset applied to the request. Examples: {"type":"bearer","token":"..."}, {"type":"apiKey","in":"header","name":"X-API-Key","value":"..."}, {"type":"basic","username":"...","password":"..."}
baseUrlstring–Override the spec's default server URL
body–––
headersobject––
methodstringyesHTTP method, e.g. GET, POST
pathstringyesThe documented path template, e.g. /pets/{id}
pathParamsobject––
queryParamsobject––
timeoutMsnumber–Abort the request after this many milliseconds.

No output schema declared.

No examples provided.

check_health ~179

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.

NameTypeReqDescription
authobject–Auth preset applied to the request. Examples: {"type":"bearer","token":"..."}, {"type":"apiKey","in":"header","name":"X-API-Key","value":"..."}, {"type":"basic","username":"...","password":"..."}
baseUrlstring––
endpointsarray–Explicit list to check. Defaults to every parameter-free GET endpoint in the loaded spec.
timeoutMsnumber–Per-endpoint timeout in ms. Default 5000.

No output schema declared.

No examples provided.

diff_api_specs ~130

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.

NameTypeReqDescription
sourceAstringyesThe 'before' spec — URL or local file path.
sourceBstringyesThe 'after' spec — URL or local file path.

No output schema declared.

No examples provided.

list_endpoints ~24

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

load_api_spec ~84

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.

NameTypeReqDescription
sourcestringyesURL or local file path to the OpenAPI/Swagger document, e.g. https://petstore3.swagger.io/api/v3/openapi.json

No output schema declared.

No examples provided.

run_all_tests ~210

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.

NameTypeReqDescription
authobject–Auth preset applied to the request. Examples: {"type":"bearer","token":"..."}, {"type":"apiKey","in":"header","name":"X-API-Key","value":"..."}, {"type":"basic","username":"...","password":"..."}
baseUrlstring––
includeMutatingboolean–Attempt POST/PUT/PATCH with auto-generated example data. Default false — may write real data.
timeoutMsnumber––

No output schema declared.

No examples provided.

test_endpoint ~176

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

NameTypeReqDescription
authobject–Auth preset applied to the request. Examples: {"type":"bearer","token":"..."}, {"type":"apiKey","in":"header","name":"X-API-Key","value":"..."}, {"type":"basic","username":"...","password":"..."}
baseUrlstring––
body–––
headersobject––
methodstringyes–
pathstringyes–
pathParamsobject––
queryParamsobject––
timeoutMsnumber–Abort the request after this many milliseconds.

No output schema declared.

No examples provided.

validate_response ~54

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

NameTypeReqDescription
methodstringyes–
pathstringyes–
responseBody–yes–
statusnumberyes–

No output schema declared.

No examples provided.

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.

npm · api-test-mcp

# add to Claude Code
claude mcp add thisis-najeeb-api-test-mcp -- npx -y api-test-mcp
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 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 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 21 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 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.

What did VerifyMCP test on the io.github.thisis-najeeb/api-test-mcp server?

VerifyMCP ran 16 checks on io.github.thisis-najeeb/api-test-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.