MCP.Market

API Test MCP server

by thisis-najeeb·io.github.thisis-najeeb/api-test-mcp·v1.0.2
No reviews yet

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

A85/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A85/100

full report

Adoption
New

0 stars41 downloads/wk

Reviews

Write one

Nobody has reviewed API Test yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

API Test tools (8, 1 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • call_endpoint

    Make an actual HTTP call to a documented endpoint and return the real status, headers, and body.

  • check_health

    One-shot health check: calls each given endpoint (or, if none given, every parameter-free GET in the

  • diff_api_specs

    Compare two OpenAPI/Swagger specs (each a URL or local file path — e.g. an old tag vs. the current main)

  • list_endpoints

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

  • load_api_spec

    Load and fully dereference an OpenAPI/Swagger spec from a URL or local file path (JSON or YAML).

  • run_all_testswrite action

    Best-effort run across every GET endpoint that needs no required parameters: calls each one for real and

  • test_endpoint

    Call a documented endpoint with real parameters, then validate the real response against its documented schema.

  • validate_response

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

Public scan report

scanner v0.1.10 · 2026-10-29 · same rubric, same numbers if you re-run it

no findings
  • Code scan4 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 59 days ago12/15
  • Maintainer identityregistry namespace matches repository owner6/10
Overall 85/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How API Test compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
85/100
higher than 70% of 48,243 servers
Tools
8
the typical server has 7
Tools that change things
13%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
41
more than 31% of 12,306 servers with a package

What its tools let an agent do: 7 read · 1 run or deploy

Install API Test in Claude Code, Cursor or VS Code

Runs npx -y api-test-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add api-test-mcp -- npx -y api-test-mcp
Add to Cursor

What the publisher says

From the API Test repository's README, as published. We do not edit it. Read it on GitHub

api-test-mcp

An MCP server that gives Claude Code, Cursor, Windsurf, or any MCP-compatible AI agent the ability to actually call your API and check the response against what your OpenAPI spec promises — not just read the docs and guess.

No API keys, no config, no cost. Works with any OpenAPI/Swagger 3.x spec (URL or local file).

Why this exists

AI agents are great at reading an OpenAPI spec and writing code against it — but they're guessing about whether the real API actually behaves the way the spec says. This gives an agent (or you, in a normal chat) a way to find out for real: call the live endpoint, and check whether the response actually matches the documented schema.

Install

git clone <this repo>
cd api-test-mcp
npm install

Add it to your MCP client config, e.g. for Claude Code:

claude mcp add api-test -- node /absolute/path/to/api-test-mcp/src/index.js

Or in claudedesktopconfig.json / Cursor's MCP settings:

{
  "mcpServers": {
    "api-test": {
      "command": "node",
      "args": ["/absolute/path/to/api-test-mcp/src/index.js"]
    }
  }
}

Tools

All of the above accept an optional auth preset (bearer, apiKey in a header or query param, or basic) so authenticated APIs aren't limited to hand-building raw headers, and an optional timeoutMs.

Example (what an agent conversation looks like)

You: Load my API spec at https://api.example.com/openapi.json and check whether /users/{id} actually returns what it documents.

Agent: (calls loadapispec, then testendpoint with a real user id) → "Called it — got a 200, but the response is missing the createdat field your spec marks as required, and role is documented as an enum of 3 values but the API returned "superadmin", which isn't one of them."

For an authenticated API:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

API Test: common questions

Is API Test MCP server safe?
Yes, by our scan: it is graded A (85/100). Read the API Test safety report
How do I install API Test?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does API Test need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is API Test maintained?
The last commit was 66 days ago (2026-08-31). The latest release is v1.0.2.
What can I use instead of API Test?
Servers from other publishers that do the same job: Keploy MCP server.
How does API Test compare with other MCP servers?
safety score 85/100 (higher than 70% of 48,243 servers); tools 8 (the typical server has 7); tools that change things 13% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to API Test

Same job from other publishers: the closest match first, then the best rated.

  • Keploy
    End-to-end API testing — generate and run tests from OpenAPI, curl, Postman, or real user traffic.
    A