Cocaxcode Api Testing MCP Server

@cocaxcode/api-testing-mcp npm v0.13.4

Published by @cocaxcode — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

The most complete MCP server for API testing. 36 tools: HTTP requests (with token-optimized responses), assertions, request flows, OpenAPI import, mock data, load testing, collections, environments, native export/import, Postman import/export, cURL export

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 42

Each tool and what it can reach — statically extracted from the published source.

  • export_curlnetwork egress
  • requestnetwork egress
  • api_endpoint_detailno sensitive capability
  • api_endpointsno sensitive capability
  • api_importno sensitive capability
  • api_spec_listno sensitive capability
  • assertno sensitive capability
  • bulk_testno sensitive capability
  • collection_deleteno sensitive capability
  • collection_getno sensitive capability
Show 32 more tools ↓
  • collection_listno sensitive capability
  • collection_saveno sensitive capability
  • diff_responsesno sensitive capability
  • env_createno sensitive capability
  • env_deleteno sensitive capability
  • env_getno sensitive capability
  • env_group_add_scopeno sensitive capability
  • env_group_createno sensitive capability
  • env_group_deleteno sensitive capability
  • env_group_listno sensitive capability
  • env_group_remove_scopeno sensitive capability
  • env_listno sensitive capability
  • env_project_clearno sensitive capability
  • env_project_listno sensitive capability
  • env_renameno sensitive capability
  • env_setno sensitive capability
  • env_set_defaultno sensitive capability
  • env_set_groupno sensitive capability
  • env_specno sensitive capability
  • env_switchno sensitive capability
  • export_collectionno sensitive capability
  • export_environmentno sensitive capability
  • export_postman_collectionno sensitive capability
  • export_postman_environmentno sensitive capability
  • flow_runno sensitive capability
  • import_collectionno sensitive capability
  • import_environmentno sensitive capability
  • import_postman_collectionno sensitive capability
  • import_postman_environmentno sensitive capability
  • inspect_last_responseno sensitive capability
  • load_testno sensitive capability
  • mockno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.13.4 latest A 96/100 0 1.13.0 2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/cocaxcode-api-testing-mcp/badge.svg)](https://mcptrustchecker.com/registry/cocaxcode-api-testing-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/cocaxcode-api-testing-mcp"><img src="https://mcptrustchecker.com/registry/cocaxcode-api-testing-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/cocaxcode-api-testing-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @cocaxcode/api-testing-mcp --online

Use the free API → How scoring works

Other implementations of Cocaxcode Api Testing 1

Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →

More in Security & Testing