Guardvibe vs Vorim MCP Server
A side-by-side look at the Guardvibe 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 Guardvibe for security work as a local process; choose Vorim MCP Server for security as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Guardvibe when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
check_code, check_project, get_security_docs.
Choose Vorim MCP Server when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
VORIM_API_KEY, VORIM_BASE_URL. - You want tools like
vorim_ping, vorim_verify_trust, vorim_onboard_start.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Security | Security |
| Quality signal | 65/100 · Great | 47/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | 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 | 6 | 66 |
| Directory activity | 3 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 39 | 4 |
| Full listing | View Guardvibe | View Vorim MCP Server |
Tools & capabilities
Guardvibe tools 39
check_codeAnalyze inline code for security vulnerabilities (OWASP Top 10, XSS, SQL injection, insecure patterns). Pass code as a string parameter. For scanning files on disk, use scan_file instead. Example: check_code({code: 'app.get(...)', language: 'javascript'})check_projectScan multiple files for security vulnerabilities and generate a project-wide security report with a security score. Use this for comprehensive security audits.get_security_docsGet security best practices and remediation guidance for a specific topic, framework, or vulnerability type. Covers OWASP Top 10, framework-specific hardening (Next.js, Supabase, Stripe), and secure coding patterns. Returns actionable guidance with code examples.check_dependenciesCheck npm, PyPI, or Go packages for known security vulnerabilities (CVEs) using the OSV database. Use this before adding new dependencies or to audit existing ones.scan_directoryScan all files in a directory on disk for security vulnerabilities. Pass a directory path — reads files from filesystem. Returns security score (A-F) and findings. Results may be truncated for large projects — check fileRanking in JSON output for top files. Example: scan_directory({path: './src'})scan_dependenciesParse a lockfile or manifest (package.json, package-lock.json, requirements.txt, go.mod) and check all dependencies for known CVEs via the OSV database. Reads the file directly. Use this after installing dependencies, during CI, or when auditing existing projects for vulnerable packages.scan_hallucinated_packagesDetect AI-hallucinated and slopsquatted packages in a repo — the supply-chain seam commodity SCA misses. OFFLINE (deterministic): flags phantom imports (a package imported in source but absent from every package.json — a classic LLM hallucination tell) and typosquats of popular packages. ONLINE (opt-in, default on; gracefully degrades offline): adds npm-registry truth — packages that return 404 (definitive hallucination) and brand-new low-download packages (slopsquat-registration pattern). Run on AI-generated code at PR time, before `npm install`. Pass online:false for a fully deterministic, air-gapped scan.scan_secretsScan files and directories for leaked secrets, API keys, tokens, and credentials. Detects high-entropy strings, known API key patterns (AWS, Stripe, OpenAI, GitHub, Supabase), exposed .env files, and missing .gitignore coverage. Returns findings with exact line numbers and remediation steps.scan_stagedScan git-staged files for security vulnerabilities before committing. Run this before every commit to catch issues early. No input needed — automatically reads staged files. Diff-aware by default: reports only issues on newly-staged lines (set diff_aware:false for whole staged files).compliance_reportMap security findings to compliance controls (SOC2, PCI-DSS, HIPAA, GDPR, ISO27001, EUAIACT). Scans a directory and groups issues by control. Output includes a summary section at the top; for large projects, findings are truncated to top 50. Use mode=executive for C-level summary. Example: compliance_report({path: '.', framework: 'SOC2'})export_sarifScan a directory and export results in SARIF v2.1.0 format for CI/CD integration (GitHub, GitLab, Azure DevOps). Returns JSON string.check_package_healthCheck npm packages for typosquat risk, maintenance status, adoption metrics, and deprecation. Use this before adding new dependencies to catch suspicious or risky packages.- +27 more on the listing page
Vorim MCP Server tools 4
vorim_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).
Ready-to-paste client configs
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.
Guardvibe
{
"mcpServers": {
"goklab-guardvibe": {
"command": "npx",
"args": [
"-y",
"guardvibe"
]
}
}
}
Vorim MCP Server
{
"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"
}
}
}
}
Frequently asked questions
Guardvibe is categorized under Security and uses a local stdio subprocess. Vorim MCP Server belongs to Security and uses a local stdio subprocess. Pick Guardvibe for security work and Vorim MCP Server for security.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Guardvibe is listed as free. Auth: no auth required. Vorim MCP Server is listed as free. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add goklab-guardvibe and vorim-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Guardvibe has a quality signal of 65/100 (Great) with 3 views, 0 installs and 6 GitHub stars. Vorim MCP Server has 47/100 (Fair) with 3 views, 0 installs and 66 GitHub stars.