OX Security Finds Governance Gaps Across 15,465 Public MCP Servers
Summary
OX Security analyzed 15,465 publicly indexed MCP servers across five registries and warns that marketplaces lack vetting and governance. The company calls for vetting, code signing, and origin verification.
Key points
- OX Security analyzed 15,465 publicly indexed MCP servers across five registries, deduplicating them to 5,095 unique hostnames.
- The article says MCP marketplaces lack equivalent safeguards such as automated scanning, consistent review, or security policies.
- Remote MCP servers may run backend code that differs from the code shown in their public repositories.
- Server operators could change where traffic is routed after launching from a clean IP address.
- The company says the full report includes its methodology, a prompt-injection proof of concept, and threat scenarios.
- OX Security recommends marketplace vetting, code signing, and origin verification, while enterprises apply their own safeguards.
Article Details
- Event Type
- Security research analyzing publicly indexed MCP servers and identifying governance and trust risks.
- Impact
- Researchers analyzed 15,465 publicly indexed servers across five registries, deduplicated to 5,095 unique hostnames. The article describes risks including absent marketplace vetting, differences between public repository code and remotely run server code, and the possibility that server locations may change. It reports no specific compromise or victim impact.