Why the MCP Trust Registry Exists
MCP servers are rapidly becoming the default way to connect AI agents to tools, files, and SaaS systems. But the ecosystem is exploding with unofficial, third‑party servers — many with hidden security risks. Teams lack a standardized, trusted way to evaluate whether an MCP server is safe to run in sensitive environments.
The MCP Registry provides code-level evaluations mapped to OWASP, MCP best practices, and Maestro so security teams can quickly assess, harden, or block risky connectors.
See the MCP Trust Registry in Action
Understand how BlueRock evaluates MCP servers for security risks.
What You Get in Every MCP Trust Scan Result
Risk rating: Low, Medium, High, or Critical with severity rationale.
Deep findings: Impacted rules and vulnerability explanations.
Tool inventory: Every tool exposed by the server, including destructive operations.
Rescan on release changes, full trend view.
Developer + admin steps.
Choose safe MCP servers and tools before you connect.
What the Trust Registry Evaluates
Exposure & Authentication
Unrestricted endpoints
Unsafe token/secret handling
Missing scopes, overbroad permissions
Tool Risk
Dangerous verbs (delete/drop/export)
Tool namespace collisions
User input sanitization failures
Data & Egress
Unbounded outbound fetch (SSRF)
Lack of egress controls
Mass data extraction patterns
Runtime & Dependencies
Unpinned packages + CVEs
Sandbox/exec risks
Deserialization / injection sinks
BlueRock MCP Trust Registry FAQ
Q: What is the MCP Trust Registry?
A: The MCP Trust Registry is a catalog of MCP servers and tools with security-focused scorecards. Each entry captures exposed tools, read/write capabilities, likely risks (e.g., RCE, data exfil, full-schema poisoning), and practical remediation notes so you can decide what’s safe to wire into your agents.
Q: How do you assess risk for MCP servers and tools?
A: We combine static and runtime-informed checks: tool discovery, permission analysis (read vs write, destructive verbs), configuration drift, and exposure to known vulnerability patterns from OWASP agentic/LLM work and real-world MCP incidents. The output is a risk band plus concrete guidance, not just a vague score.
Q: Can I use the registry without deploying BlueRock?
A: Yes. You can use the MCP Trust Registry as a standalone reference to vet servers and tools before you connect them. When you do deploy BlueRock, registry entries can seed allow-lists and guardrails so the tools you approve are automatically governed at runtime.
Q: How often are registry entries updated?
A: Entries are periodically updated as new vulnerabilities, configuration changes, or tool behaviors emerge. Our goal is to keep the registry aligned with current MCP exploits and agentic attack research, not just a one-time scan.
Q: How does this help with “shadow” or unknown MCP usage?
A: The registry helps you evaluate known MCP servers up front, and BlueRock’s runtime visibility helps you discover servers, tools, and agents that slipped in outside formal review. Together, they close the gap between what you think is connected and what’s actually in use in production.
