API statistics.
The catalog, measured.

Which API profiles list an official MCP?

Expanded MCP review, October 21, 2026

We have documented official MCP implementations for 121 profiles in the 18,250-profile export, plus 23 curated profiles outside that export. These are reviewed associations, not the total number of providers offering MCP.

Missing evidence means unknown—not “no MCP.” The catalog includes legacy products, developer tools and companies without a confirmed public API. We cannot use it to conclude that most APIs do or do not have official MCPs.

What the expanded review covered

• 110 of 110 entries in our publisher collection now link to existing profiles. All collection entries now have a reviewed profile association; connection requirements were documented for the 21 entries added in revision 3, and revision 4 adds Fathom, matched by the endpoint in its own MCP documentation.
• All 81 previously excluded associations were reviewed; 27 now have explicit official evidence.
• Official and community counts overlap where a provider has a current official implementation and an archived reference. Archived references are not evidence of active support.

Provider ownership and implementation scope are reviewed separately. Developer tools are labeled separately from API/data access. Official status does not promise full API coverage, endpoint availability or security. Source-review dates are preserved per entry; this expansion does not reclassify registry records.

Download expanded associations and evidence (JSON) · Original 30-profile review

This revision is separate from the eight frozen catalog-field findings above. Profiles are counted once within each group; multiple implementations do not inflate the profile count.

Source, definitions & limitations

Source: API Tracker’s local provider-catalog export, analyzed October 21, 2026. Identity-matched corrections from our reviewed profile dataset are applied to developer-portal and API-reference fields. This is not a new survey or live provider crawl. The 18,250-record export can differ from the hosted directory count because their observation dates and inclusion rules differ.

1. Count each exact catalog profile ID once. Do not merge brands or count embedded API records as separate providers.
2. Documentation, reference, status, changelog and limits use developerPortalUrl, apiReferenceUrl, statusUrl, apiChangelogUrl and apiLimitsUrl respectively. Accept HTTP(S) URLs without embedded credentials; deduplicate URLs within each field group.
3. SDK coverage requires a URL in websiteUrl, githubUrl or url on an SDK record. It does not establish that the SDK is official, supported or downloadable.
4. Specification coverage requires a url in apiTracker.specs or embedded apis[].specs. Other free-text links, specRepo and unresolved external API references are excluded. Files are not parsed or validated as OpenAPI.
5. Missing fields remain unknown. URLs are not fetched for this analysis; syntax validation cannot establish correctness, liveness, API availability or security. Categories overlap and are not additive.

The download preserves each profile ID and the exact counted resource URLs. Source-export and correction-file hashes are included in the aggregate report. Catalog coverage percentages should not be quoted as API industry adoption rates.

Aggregate report & SHA-256 hashes · Reproduction script · Directory methodology