What is the key difference between Guardvibe and Scanpay?

Guardvibe belongs to the Security category with local stdio execution, while Scanpay belongs to the Security category with local stdio execution.

How do I install Guardvibe or Scanpay in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Guardvibe and Scanpay free or paid?

Guardvibe operates under a Free / Open Source model (No auth required). Scanpay operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Guardvibe lists 39 tools with 2 views and 5 GitHub stars. Scanpay lists 6 tools with 0 views and 0 GitHub stars.

Can I use both Guardvibe and Scanpay together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Guardvibe vs Scanpay

In-depth architectural comparison of the Guardvibe and Scanpay 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

Guardvibe

Security · Local stdio

Quality: 65/100 (Great) | Auth: No auth required

Scanpay

Security · Local stdio

Quality: 41/100 (Fair) | Auth: No auth required

Verdict Summary: Choose Guardvibe if you need specialized Security tools running via a local process. Choose Scanpay 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 Guardvibe 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).
Primary tools included: check_code, check_project, get_security_docs.

Explore Guardvibe Details

Choose Scanpay 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: SCANPAY_URL, SCANPAY_PAYMENT_MODE, SCANPAY_MERCHANT_WALLET, SCANPAY_PRICE_LAMPORTS, SCANPAY_RPC_URL, SCANPAY_PORT.
Primary tools included: 45+ deterministic vulnerability patterns, Python and JavaScript/TypeScript AST analysis, MCP `scan_code` tool.

Feature & Specification Comparison

Specification	Guardvibe goklab Security	Scanpay Security
Summary	Security MCP for vibe coding with 330 rules and 29 tools. Purpose-built for AI-generated code — scans Next.js, Supabase, Clerk, Stripe, Prisma, Hono, GraphQL, and 25+ modules. Cross-file taint analysis, host security audit, auto-fix, SARIF export, pre-commit hook, and CVE version detection. Zero config, runs locally.	Code security scanner for AI agents. 45+ vulnerability patterns, AST analysis, Solana micropayments.
Category & Scope	Security

Tools & Capabilities Breakdown

Guardvibe Tools (39)

check_code

Analyze 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_project

Scan multiple files for security vulnerabilities and generate a project-wide security report with a security score. Use this for comprehensive security audits.

get_security_docs

Get 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_dependencies

Check 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_directory

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Guardvibe Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "goklab-guardvibe": {
      "command": "npx",
      "args": [
        "-y",
        "guardvibe"
      ]
    }
  }
}

Scanpay Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "scanpay": {
      "command": "npx",
      "args": [
        "-y",
        "scanpay-mcp-server"
      ],
      "env": {
        "SCANPAY_URL": "YOUR_SCANPAY_URL_HERE",
        "SCANPAY_PAYMENT_MODE": "YOUR_SCANPAY_PAYMENT_MODE_HERE",
        "SCANPAY_MERCHANT_WALLET": "YOUR_SCANPAY_MERCHANT_WALLET_HERE",
        "SCANPAY_PRICE_LAMPORTS": "YOUR_SCANPAY_PRICE_LAMPORTS_HERE",
        "SCANPAY_RPC_URL": "YOUR_SCANPAY_RPC_URL_HERE",
        "SCANPAY_PORT": "YOUR_SCANPAY_PORT_HERE"
      }
    }
  }
}

Frequently Asked Questions

Guardvibe is categorized under Security and uses a local stdio subprocess. In contrast, Scanpay belongs to Security using local stdio subprocess. Select Guardvibe when you need capabilities focused on security and Scanpay when you require tools for security.

More alternatives to Guardvibe More alternatives to Scanpay Security category hub