X402 Notary MCP vs Guardvibe

A side-by-side look at the X402 Notary MCP and Guardvibe MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

X402 Notary MCP logoX402 Notary MCPSecurity · Local subprocess (stdio)Cryptographic receipts for AI outputs: notarize any model inference with a signed Ed25519 attestation, sha256 content hash, and Merkle chain-anchor on Base or Solana. $0.001 per call via x402 USDC micropayments; verification is free and needs no wallet. Notarizes the hash, never your prompts. npx -y @forgemeshlabs/x402-notary-mcp63GoodAuth: not declaredGuardvibe logoGuardvibeSecurity · Local subprocess (stdio)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.65GreatAuth: no auth required

Verdict: choose X402 Notary MCP for security work as a local process; choose Guardvibe for security as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

X402 Notary MCP logoChoose X402 Notary MCP when

  • You need dedicated capabilities in the Security domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: WALLET_PRIVATE_KEY, NOTARY_RAIL, NOTARY_BASE_URL, SOLANA_PRIVATE_KEY.
  • You want tools like notarize_inference, notarize_batch, verify_attestation.
Explore X402 Notary MCP

Guardvibe logoChoose 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.
Explore Guardvibe

Feature & specification comparison

Rows where the two servers differ are marked.

SpecX402 Notary MCP logoX402 Notary MCPGuardvibe logoGuardvibe
CategorySecuritySecurity
Quality signal63/100 · Good65/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsWALLET_PRIVATE_KEYNOTARY_RAILNOTARY_BASE_URLSOLANA_PRIVATE_KEYNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars06
Directory activity 2 views 0 installs 0 upvotes 3 views 0 installs 0 upvotes
Tools639

Tools & capabilities

X402 Notary MCP tools 6

  • notarize_inferenceGet a cryptographic receipt for one AI inference. Returns a signed Ed25519 attestation, sha256 content hash, and Merkle chain-anchor status for {prompt, response, model_id}. The notary does NOT store your prompt or response — only the hash is retained. Costs $0.001 USDC via x402 (requires WALLET_PRIVATE_KEY for a Base wallet).
  • notarize_batchNotarize up to 20 AI inferences in one call — one signed attestation per record. Ideal for audit trails and agent pipelines. Costs $0.005 USDC via x402 (requires WALLET_PRIVATE_KEY for a Base wallet).
  • verify_attestationFREE — verify any attestation issued by the notary. Supply the attestation_id plus either the original content ({prompt, response, model_id}) or its content_hash. Returns the Ed25519 signature check, hash comparison, and a Merkle inclusion proof once the batch is sealed. No wallet needed.
  • get_receiptFREE — fetch the public receipt for an attestation: content hash, model, timestamps, Ed25519 signature, and Merkle anchor proof. Raw prompt/response are never stored, so receipts contain proof material only. No wallet needed.
  • notary_statsFREE — live aggregate stats: total notarizations, 24h volume, top models by attestation count, sealed/anchored Merkle batches. No wallet needed.
  • notary_pubkeyFREE — the notary's Ed25519 public key (base64, raw 32 bytes) for fully offline signature verification. No wallet needed.

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

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.

X402 Notary MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "forgemeshlabs-x402-notary-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@forgemeshlabs/x402-notary-mcp"
      ],
      "env": {
        "WALLET_PRIVATE_KEY": "YOUR_WALLET_PRIVATE_KEY_HERE",
        "NOTARY_RAIL": "YOUR_NOTARY_RAIL_HERE",
        "NOTARY_BASE_URL": "YOUR_NOTARY_BASE_URL_HERE",
        "SOLANA_PRIVATE_KEY": "YOUR_SOLANA_PRIVATE_KEY_HERE"
      }
    }
  }
}

Guardvibe

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "goklab-guardvibe": {
      "command": "npx",
      "args": [
        "-y",
        "guardvibe"
      ]
    }
  }
}

Frequently asked questions

X402 Notary MCP is categorized under Security and uses a local stdio subprocess. Guardvibe belongs to Security and uses a local stdio subprocess. Pick X402 Notary MCP for security work and Guardvibe 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.

X402 Notary MCP has no declared pricing — check the project's own site. Guardvibe is listed as free. Auth: no auth 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 forgemeshlabs-x402-notary-mcp and goklab-guardvibe as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, X402 Notary MCP has a quality signal of 63/100 (Good) with 2 views, 0 installs and 0 GitHub stars. Guardvibe has 65/100 (Great) with 3 views, 0 installs and 6 GitHub stars.