BY THE APIDECK TEAM
Know what’s behind the directory.
Explore the coverage, sources, and public data that power API Tracker.
Two catalogs. Different evidence.
API profiles describe providers and their developer resources. The MCP catalog indexes namespaced server records from the Official MCP Registry, normalized with MCP Connect. These are different units; the counts should not be added together as unique providers.
Provider descriptions and registry metadata can change. Review dates apply to the specific evidence displayed, rather than every field in a profile.
PUBLIC MCP CATALOG
Inspect the data.
The read-only JSON endpoint supports q, publisher, transport, offset, and limit (1–100). It returns matching server records, result counts, and the snapshot date.
GET /api/mcp/catalog?publisher=official&limit=24name- Namespaced registry identity used to distinguish servers.
title / description- Display name and description supplied in the catalog.
version- Version listed in the registry snapshot.
repository / website- Source and website links, when provided.
remoteUrl / transports- Published connection endpoint and transport metadata.
publisher- Reviewed affiliation status, with evidence and a review date when available.
“Official” describes reviewed publisher affiliation. It does not certify security, uptime, or client compatibility. API Tracker lists the servers; connections and tool execution happen with their providers.
Help keep the directory accurate.
Send a correction with the profile URL and a supporting publisher source, or submit an API or MCP server for review.