The project’s MCP servers
const url = 'https://beta-api.plune.ai/v1/mcp-servers';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 \ --header 'Authorization: Bearer <token>'The servers the project tests, in the order they were added, each with how many tools its latest snapshot lists and how many snapshots it has. Anyone in the project.
Authorizations
Section titled “Authorizations ”Responses
Section titled “ Responses ”The servers
object
In the order they were added
object
The project’s once, whatever its case
How the server is reached. Not where: the catalog has no field for an address, command, header or variable
How it came into the catalog: manual - a person added it; mission - an mcp source of a mission named it, and the catalog took it in at once
confirmed - a person added it; derived - inferred from a mission source. A mission source that names a server already here links it and leaves its trust as it was
The mission source that named it; null for a server no source names, and once that source is taken off (the server stays)
Tools the latest snapshot lists
Snapshots taken; also the number of the latest
Example
{ "servers": [ { "id": "6f1c2b3a-0000-4000-8000-000000002458", "projectId": "u-shop::default", "name": "Shop MCP", "transport": "stdio", "description": "The shop’s order tools", "source": "manual", "trust": "confirmed", "missionSourceId": null, "tools": 2, "snapshots": 2, "createdBy": "6f1c2b3a-0000-4000-8000-0000000000a2", "createdAt": "2026-11-13T09:00:00.000Z", "updatedAt": "2026-11-13T09:00:00.000Z" } ]}No / invalid token or session