evalstate/mcp-clients

MCP Clients Dataset

MCP client identity and capability observations from huggingface.co/mcp.

The pipeline incrementally processes completed daily source partitions. Each release records its source revision and watermark in state/mcp-clients-v1.json and a sanitized 60-day dashboard snapshot in reports/dashboard-v1.json. Its window is the requested UTC date range. Omitted client traffic dates are unavailable data, not zero traffic.

Protocol traffic before 2026-07-27 is a one-time, immutable backfill from legacy initialize records; newer traffic is derived from requests. Each traffic point identifies its source. Historical capability evidence is limited to elicitation, URL elicitation, and MCP Apps; Skills and Tasks are request-only. Historical “All other clients” traffic is a best-effort initialization-based aggregate of unclassified names with at least 1,000 legacy tool calls. Current “All other clients” traffic remains request-based and requires at least 1,000 valid-protocol tool calls in the report window.

Successful extension-method observations that were available only in cumulative transport metrics are published as a sanitized, restart-aware capability backfill. Evidence applies only while its observation date overlaps the rolling dashboard window and does not contribute to protocol traffic volume.

Configurations

raw

One row per distinct (name, version, capabilities) with its latest observed last_seen time.

deduplicated

One row per normalized (name, capabilities). mcp-remote suffixes are removed from names; observed versions are stored as a comma-separated string.

Client-provided fields are untrusted telemetry. Consumers should not treat names, versions, or capability values as verified claims.

Reproducibility

Every successful release atomically publishes both configurations, state/mcp-clients-v1.json, and reports/dashboard-v1.json. The state file identifies the immutable source revision and completed source-date watermark used for that release.