io.github.thisis-najeeb/api-test-mcp
NPM · API-TEST-MCP · SCANNED SEP 24
Call the real API and check the response against your OpenAPI spec.
Available components
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
- 37 of 105 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 23 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
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 Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
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
claude mcp add thisis-najeeb-api-test-mcp -- npx -y api-test-mcp
{
"mcpServers": {
"thisis-najeeb-api-test-mcp": {
"command": "npx",
"args": [
"-y",
"api-test-mcp"
]
}
}
} {
"servers": {
"thisis-najeeb-api-test-mcp": {
"command": "npx",
"args": [
"-y",
"api-test-mcp"
]
}
}
} codex mcp add thisis-najeeb-api-test-mcp -- npx -y api-test-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"thisis-najeeb-api-test-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"api-test-mcp"
],
"enabled": true
}
}
} openclaw mcp add thisis-najeeb-api-test-mcp --command npx --arg -y --arg api-test-mcp
mcp_servers:
thisis-najeeb-api-test-mcp:
command: "npx"
args: ["-y", "api-test-mcp"] {
"McpServers": {
"thisis-najeeb-api-test-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"api-test-mcp"
]
}
}
} assistant mcp add thisis-najeeb-api-test-mcp -t stdio -c npx -a -y api-test-mcp
{
"mcpServers": {
"thisis-najeeb-api-test-mcp": {
"command": "npx",
"args": [
"-y",
"api-test-mcp"
]
}
}
} 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.
- 23 Sept 26 +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.
- 21 Sept 26 +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.
- 19 Sept 26 +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.
- 17 Sept 26 +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.
- 14 Sept 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.
- 12 Sept 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.
- 10 Sept 26 +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.
- 8 Sept 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 24 Sept 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 105 packages
| Packages resolved | 105 |
|---|---|
| Stale | 37 |
| 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 →
call_endpoint Call a real API 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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | HTTP method, e.g. GET, POST |
| path | string | yes | The documented path template, e.g. /pets/{id} |
| pathParams | object | – | – |
| queryParams | object | – | – |
| timeoutMs | number | – | Abort the request after this many milliseconds. |
No output schema declared.
No examples provided.
check_health Ping a set of endpoints and report reachability/latency ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
diff_api_specs Diff two versions of an OpenAPI spec for breaking changes ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| sourceA | string | yes | The 'before' spec — URL or local file path. |
| sourceB | string | yes | The 'after' spec — URL or local file path. |
No output schema declared.
No examples provided.
list_endpoints List loaded 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 Load an OpenAPI/Swagger 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.
| Name | Type | Req | Description |
|---|---|---|---|
| source | string | yes | URL 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 Run a contract-test pass across the whole API ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | – |
No output schema declared.
No examples provided.
test_endpoint Call and validate an endpoint in one step ~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'.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
| path | string | yes | – |
| pathParams | object | – | – |
| queryParams | object | – | – |
| timeoutMs | number | – | Abort the request after this many milliseconds. |
No output schema declared.
No examples provided.
validate_response Validate a response against the spec ~54
Check a response body against the JSON schema documented for a given method + path + status code.
| Name | Type | Req | Description |
|---|---|---|---|
| method | string | yes | – |
| path | string | yes | – |
| responseBody | – | yes | – |
| status | number | yes | – |
No output schema declared.
No examples provided.
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.