developer tools
The MCP Ecosystem Gets a Relational Map
MCP-Eco links server projects, consumer configurations, declared interfaces and repository activity across 19 Parquet tables.
Summary
MCP-Eco links server projects, consumer configurations, declared interfaces and repository activity across 19 Parquet tables.
The frozen release contains 16,880,899 records covering 78,302 candidate server projects, 16,165 candidate consumer repositories and 9,200 configuration declarations. Matching resolves 5,975 declarations into 5,138 distinct repository-server pairs. Provenance separates directory claims from live probing and records how declarations were matched. The public dataset enables ecosystem research and schema inspection, but its use of candidate projects and inferred links means the numbers are not a census of verified, active or safe MCP deployments.
Why it matters
MCP-Eco links server projects, consumer configurations, declared interfaces and repository activity across 19 Parquet tables.
Limits and context
- The public dataset enables ecosystem research and schema inspection, but its use of candidate projects and inferred links means the numbers are not a census of verified, active or safe MCP deployments.
Key claims
MCP-Eco links server projects, consumer configurations, declared interfaces and repository activity across 19 Parquet tables.
Qualification: The public dataset enables ecosystem research and schema inspection, but its use of candidate projects and inferred links means the numbers are not a census of verified, active or safe MCP deployments.
Evidence: source-2026-11-05-012
Sources
- arXiv preprint 2611.06897, original v1arXiv · primary research
Corrections
No corrections have been recorded for this story.