Agent Trust Stack MCP vs Vorim MCP Server | AllMCPs
Side-by-Side Model Context Protocol Comparison
Agent Trust Stack MCP vs Vorim MCP Server
In-depth architectural comparison of the Agent Trust Stack MCP and Vorim MCP Server MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Agent Trust Stack MCP
Security · Local stdio
Quality: 55/100 (Good) | Auth: No auth required
Vorim MCP Server
Security · Local stdio
Quality: 65/100 (Great) | Auth: API Key required
Verdict Summary: Choose Agent Trust Stack MCP if you need specialized Security tools running via a local process. Choose Vorim MCP Server if your workspace requires Security integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Agent Trust Stack MCP when:
You need dedicated capabilities in the Security domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: COC_CHAIN_DIR, ARP_RATINGS_DIR.
Agent Trust Stack MCP is categorized under Security and uses a local stdio subprocess. In contrast, Vorim MCP Server belongs to Security using local stdio subprocess. Select Agent Trust Stack MCP when you need capabilities focused on security and Vorim MCP Server when you require tools for security.
Get info about all 7 protocols with whitepaper links
verify_agent_identity
Verify an agent's identity via Agent Card URL
get_trust_evidence
Get combined trust evidence (CoC + ARP) for an agent
Vorim MCP Server Tools (4)
vorim_ping
Check Vorim AI API health and connectivity. Returns status, version, and service health.
vorim_verify_trust
Verify an agent's identity and trust score. Public endpoint, no authentication required. Returns the trust score (0-100), trust band, status, owning organisation name and a signed attestation. Active scopes and key fingerprint are not shown publicly; the owning organisation can see them with vorim_list_permissions and vorim_get_agent.
vorim_onboard_start
Start onboarding a user who does NOT yet have a Vorim API key (device-authorization flow). Returns a user_code and an activation URL. You MUST show the human the user_code and verification_uri VERBATIM and ask them to approve in their browser. Then call vorim_onboard_check with the returned device_code to obtain the API key. No VORIM_API_KEY is required for this tool.
vorim_onboard_check
Check whether the human has approved the onboarding request from vorim_onboard_start. Pass the device_code you received. Returns the new API key once approved; otherwise returns a status (authorization_pending — wait ~5s and call again; slow_down — wait longer; access_denied; expired_token).