The coverage of an MCP server’s tools
const url = 'https://beta-api.plune.ai/v1/mcp-servers/example/coverage';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://beta-api.plune.ai/v1/mcp-servers/example/coverage \ --header 'Authorization: Bearer <token>'Every tool the server lists now (listed: true) by name, with its live cases (an explicit link, PUT /v1/mcp-tools/{id}/cases; never a match by name), the newest result of each, and the requirements those cases are linked to. A tool with no case is uncovered; one whose cases have no result is notRun, never a pass. A case of a tool that the newest snapshot pair changed (breaking, or changed) is «May be out of date» until a person takes the mark off for that snapshot. A tool the newest snapshot no longer lists is neither shown nor counted: it stays in the catalog, unlisted, with its cases. Anyone in the project.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”The server’s id
Responses
Section titled “ Responses ”The coverage
Counts, no percentage: a server whose tools have no case is covered: 0, never 100%.
object
The newest snapshot; null - none taken
object
object
Tools with at least one live case
Tools with no live case
Tools whose cases have no result yet
Live cases still marked «May be out of date», summed over all tools (a tool with two marked cases counts 2)
By name; the order a page shows them in is its own
object
uncovered - no live case; notRun - its cases have no result yet (not a pass, not 0%); otherwise the counted status of the newest result among its cases
The change of the newest snapshot pair that marks its cases: a breaking class, or a changed tool. null - none
object
object
The tool’s change marks it and nobody took the mark off for that snapshot. Advice: no gate reads it, and the case is not changed
The requirements its cases are linked to
object
Example
{ "serverId": "6f1c2b3a-0000-4000-8000-000000002458", "snapshot": { "id": "6f1c2b3a-0000-4000-8000-000000002460", "number": 2 }, "summary": { "tools": 2, "covered": 1, "uncovered": 1, "notRun": 0, "mayBeOutOfDate": 1 }, "tools": [ { "toolId": "6f1c2b3a-0000-4000-8000-000000002459", "name": "get_order", "listed": true, "state": "passed", "lastResultAt": "2026-11-13T09:00:00.000Z", "change": { "snapshotId": "6f1c2b3a-0000-4000-8000-000000002460", "snapshotNumber": 2, "kind": "changed", "class": "breaking" }, "cases": [ { "id": "6f1c2b3a-0000-4000-8000-0000000000c1", "title": "Read an order", "latestStatus": "passed", "lastResultAt": "2026-11-13T09:00:00.000Z", "mayBeOutOfDate": true } ], "requirements": [ { "id": "6f1c2b3a-0000-4000-8000-0000000000f5", "key": "REQ-1", "title": "Order lookup" } ] } ]}No / invalid token or session
No such MCP server in your project
object
Example generated
{ "error": "example"}