Metrics
Public numbers for ccpedia.xyz. MCP, API and search figures are live; page-visit figures refresh every 15 minutes (as of 2026-11-15 10:00 UTC) and count a visit as human only when its session viewed two or more pages, which leaves out single-view hits from crawlers that keep no cookie. Sources: page visits, MCP calls, REST API, search log.
The index
Records per source · Governance
8,820 recordsIndex share by area
of 48,014 records- Governance8,82018%
- Learn5,36411%
- Community8,53918%
- Code & network25,29153%
All time
Recording since 2026-06-30.
Before 2026-11-01, visit counts included link prefetches, about six rows for every page view. Until 2026-11-04, a browser's first visit also logged a second row for the page its service worker caches in the background. Page visits and actives therefore count from 2026-11-05, the first full day without either, and fill up from there.
Headlines, 30-day windows
Daily trends, 30 days
Before 2026-11-01, visit counts included link prefetches, about six rows for every page view. Until 2026-11-04, a browser's first visit also logged a second row for the page its service worker caches in the background. Page visits and actives therefore count from 2026-11-05, the first full day without either, and fill up from there.
Who calls the MCP server
MCP calls by caller class
all time, tools/list included- External clients11,30011%
- Ours1,6652%
- Crawlers and probes40,30639%
- Unattributable50,01648%
Integrations
30 daysDistinct user-agents that called MCP at least 3 times in the last 30 days. Most of this list is MCP-directory crawlers, trust/tool-poisoning scanners, and uptime probes discovering the server (see “MCP sources” below), not agents asking Canton questions. Treat this count as reach into the MCP ecosystem's infrastructure, not confirmed product usage.
Breakdowns, 30 days
External sessions by tool calls
sessions that ran a toolPage revalidates every 5 minutes. For machine-readable status:/status/data