Results are records containing Domain, Category, Description, and an Endpoints array. Each endpoint contains its URL, whether authentication is required, its supported Tools (methods), and its complete Overview discovery object when available. Overview can include instructions, protocolVersion, serverInfo, capabilities, and additional fields reported by the remote MCP server. Results are sorted alphabetically by domain, up to 100 per page.
[
{
"Domain": "example.com",
"Category": "Developer Tools",
"Description": "Example MCP server description",
"Endpoints": [
{
"Endpoint": "https://example.com/mcp",
"AuthRequired": true,
"Tools": [
{ "Name": "search_orders", "Description": "Search orders by customer or status" }
],
"Overview": {
"instructions": "Use this server to search and manage orders.",
"protocolVersion": "2025-06-18",
"serverInfo": { "name": "example-orders", "version": "1.0.0" },
"capabilities": { "tools": { "listChanged": false } }
}
}
]
}
]
CSV and TXT responses flatten Endpoints into a single column and include a separate Overview column containing the endpoint URL and its JSON overview. TXT is tab-separated with no header row.
Domain,Category,Description,Endpoints,Overview
example.com,Developer Tools,Example MCP server description,"https://example.com/mcp [search_orders, get_order]","https://example.com/mcp: {""instructions"":""Use this server to search and manage orders.""}"
SEARCH matches against the domain, description, endpoint URLs, tool names/descriptions, and overview instructions - so searching for a method name or an instruction keyword finds matching MCP servers, not just matching domains.
Pagination metadata is returned as response headers rather than in the body: X-TOTAL-COUNT (total matches), X-OFFSET (the requested offset), X-PAGE-SIZE (always 100), and X-HAS-MORE (true/false). Pass a larger OFFSET to fetch the next page.