mcpSecurity.cloud
MCP ECOSYSTEM RESEARCH · LIVE CATALOG RANKING

Companies with the most community-associated MCP servers

Which company product ecosystems attract the largest independently published or attribution-unresolved MCP surface—and how much official and current-version evidence exists alongside it.

9company product ecosystems compared
25community or unresolved company associations
Amazon & AWSlargest community-associated surface in this cohort
PRIMARY FINDING

Amazon & AWS leads the current ranking with 7 community-associated implementations.

Community means the catalog has not retained sufficient first-party publisher evidence for the referenced company. It does not mean malicious, vulnerable, unofficially branded, or low quality.

#Company ecosystemCommunity / unresolvedOfficial evidenceTotal associatedDistribution presenceCurrent verificationUnderlying records
01Amazon & AWS6 mapped product families7
00.0% with retained official evidence7npm 1PyPI 5remote 10.0%0 current versions verifiedOpen evidence →
02Microsoft & Azure15 mapped product families6
440.0% with retained official evidence10npm 6PyPI 1remote 230.0%3 current versions verifiedOpen evidence →
03Google9 mapped product families3
125.0% with retained official evidence4npm 2PyPI 0remote 125.0%1 current versions verifiedOpen evidence →
04MongoDB2 mapped product families3
00.0% with retained official evidence3npm 3PyPI 0remote 033.3%1 current versions verifiedOpen evidence →
05Salesforce4 mapped product families2
133.3% with retained official evidence3npm 2PyPI 0remote 00.0%0 current versions verifiedOpen evidence →
06Docker2 mapped product families1
150.0% with retained official evidence2npm 0PyPI 0remote 050.0%1 current versions verifiedOpen evidence →
07Atlassian5 mapped product families1
00.0% with retained official evidence1npm 0PyPI 0remote 10.0%0 current versions verifiedOpen evidence →
08Cloudflare5 mapped product families1
00.0% with retained official evidence1npm 1PyPI 0remote 00.0%0 current versions verifiedOpen evidence →
09OpenAI4 mapped product families1
00.0% with retained official evidence1npm 1PyPI 0remote 0100.0%1 current versions verifiedOpen evidence →

Methodology and limitations

  1. The unit is a deduplicated, canonical MCP implementation in the current published and indexable catalog cohort.
  2. Association uses strong retained identity fields: implementation name, canonical package or repository, and active listing name or namespace. Generic description prose is excluded.
  3. An implementation may be associated with more than one company ecosystem, so company rows and aggregate association totals are not a count of unique MCPs across the full report.
  4. Official means retained publisher evidence. Community or unresolved means that evidence is absent; neither category is a security verdict.
  5. npm, PyPI, and remote counts overlap. Verification applies only to selected exact current versions with a completed eligible run.
  6. The catalog is not a complete census of every MCP implementation that exists. Rankings change as discovery, attribution, publication, and verification evidence changes.

Generated September 8, 2026 UTC · Review publisher definitions

Let’s talk about MCP security.

Share your details and our security team will contact you.