Ecosystem Dashboard
Aggregated security posture across every MCP server we've discovered. Updates every 5 minutes.
Findings by Severity 8,640
Cross-server toxic flowconfig-scoped
Individual server scores on this registry are intrinsic - each measures one server on its own. Compositional risk is different: a private-data reader on one server and an external-egress sink on another are each harmless alone but can form a toxic flow once wired into the same client config. That is a config-scoped property of the wiring, never a score against any one server.
We do not publish a registry-wide co-existence count here. A cross-server flow is only real once specific servers share one config, so an ecosystem-wide number would be hypothetical - and we will not print a figure the data does not support.
Category Breakdown
Recently Discovered10
Scan Coverage
21,168 servers awaiting scan
Detection Rules184
184 rules across 21 categories — every server is evaluated against all applicable rules.
OWASP MCP Top 10 Coverage
Detection rules mapped to all 10 OWASP MCP categories. Every server is evaluated against each category on every scan.