MCP manifest
A machine-readable list of the read endpoints.
GET /api/rest/v1/mcp returns a short JSON description of the read endpoints, so a script or an AI assistant can discover what it may call with your API key.
curl -H "Authorization: Bearer $APPS_PATROL_API_KEY" https://www.apps-patrol.com/api/rest/v1/mcp
{
"name": "apps-patrol",
"version": "1.0",
"description": "Read-only Apps Patrol MCP tools over the REST API",
"tools": [
{ "name": "overview", "method": "GET", "path": "/api/rest/v1/overview" },
{ "name": "apps", "method": "GET", "path": "/api/rest/v1/apps" },
{ "name": "keywords", "method": "GET", "path": "/api/rest/v1/keywords" }
]
}
What this is and is not
This is a manifest, not a Model Context Protocol server: an MCP client cannot connect to it directly. To use the data from an assistant today, give it the REST API endpoints and a key. A real MCP server is planned.
For AI assistants reading this site
A plain-text summary of the product is at /llms.txt.