MCP Server Ecosystem Research

Research, as of July 13, 2026, the Model Context Protocol server ecosystem. Shared research protocol: define the MCP protocol version and July 13, 2026 cutoff. Treat the official specification, release notes, SDK, and repository documentation as authoritative for protocol behavior; use maintained server repositories, package metadata, reproducible tests, vulnerability databases, advisories, and documented incidents for implementation evidence. Cite every material claim with version, date, repository, and test conditions where applicable. Cross-check compatibility, maintenance, adoption, and security claims; label unknown, single-source, stale, or conflicting evidence. Separate protocol guarantees from SDK behavior, implementation choices, directory metadata, and future proposals. Common outputs must include scope, sampling, evidence grades, reproducible checks, limitations, unresolved questions, and references. Task module: Map resources, prompts, tools, implementation patterns, hosting, and ecosystem gaps; deliver a protocol capability map, server taxonomy, implementation comparison, maintenance evidence, gaps, and evaluation checklist. Do not infer compatibility or security from listing metadata, popularity, or self-description; do not use directory totals as security evidence.

Research, as of July 13, 2026, the Model Context Protocol server ecosystem. Shared research protocol: define the MCP protocol version and July 13, 2026 cutoff. Treat the official specification, release notes, SDK, and repository documentation as authoritative for protocol behavior; use maintained server repositories, package metadata, reproducible tests, vulnerability databases, advisories, and documented incidents for implementation evidence. Cite every material claim with version, date, repository, and test conditions where applicable. Cross-check compatibility, maintenance, adoption, and security claims; label unknown, single-source, stale, or conflicting evidence. Separate protocol guarantees from SDK behavior, implementation choices, directory metadata, and future proposals. Common outputs must include scope, sampling, evidence grades, reproducible checks, limitations, unresolved questions, and references. Task module: Map resources, prompts, tools, implementation patterns, hosting, and ecosystem gaps; deliver a protocol capability map, server taxonomy, implementation comparison, maintenance evidence, gaps, and evaluation checklist. Do not infer compatibility or security from listing metadata, popularity, or self-description; do not use directory totals as security evidence.