A side-by-side look at the Hlido MCP and Vorim MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Hlido MCP for security work over a hosted endpoint; choose Vorim MCP Server for security as a local process. You can also run both side by side in one mcpServers block.
trust_check, find_trusted, verify_claim.VORIM_API_KEY, VORIM_BASE_URL.vorim_ping, vorim_verify_trust, vorim_onboard_start.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Security | Security |
| Quality signal | 48/100 · Fair | 65/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | No auth required | API key required |
| Pricing | Free | Free |
| Required env vars | None listed | VORIM_API_KEYVORIM_BASE_URL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 66 |
| Directory activity | 3 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 9 | 4 |
| Full listing | View Hlido MCP | View Vorim MCP Server |
trust_check"Is agent X trustworthy?" — score, tier, verdict for a slugfind_trusted"Find me a trusted agent for <need>" — filtered registry searchverify_claim"Does X really do Y?" — per-claim PASS/FAIL evidencecompare_agentsSide-by-side scorecard comparisonget_scorecardFull sanitized scorecard JSON for a slugfind_similar_agentsSemantic nearest neighbours to a given agentsubmit_agentNominate an agent for reviewreport_review_issueFlag a problem with a published reviewrequest_quick_auditAsk for a fast re-check of a stale reviewvorim_pingCheck Vorim AI API health and connectivity. Returns status, version, and service health.vorim_verify_trustVerify 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_startStart 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_checkCheck 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).Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
{
"mcpServers": {
"ankitkapur1992-hlido-hlido-mcp": {
"url": "https://hlido.eu/mcp"
}
}
}
{
"mcpServers": {
"vorim-mcp-server": {
"command": "npx",
"args": [
"-y",
"@vorim/mcp-server"
],
"env": {
"VORIM_API_KEY": "YOUR_VORIM_API_KEY_HERE",
"VORIM_BASE_URL": "YOUR_VORIM_BASE_URL_HERE"
}
}
}
}