What is the key difference between Scamverify MCP and Shield?

Scamverify MCP belongs to the Security category with local stdio execution, while Shield belongs to the Security category with local stdio execution.

How do I install Scamverify MCP or Shield 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 Scamverify MCP and Shield free or paid?

Scamverify MCP operates under a Freemium model (API Key required). Shield operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Scamverify MCP lists 10 tools with 3 views and 1 GitHub stars. Shield lists 6 tools with 4 views and 11 GitHub stars.

Can I use both Scamverify MCP and Shield 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

Scamverify MCP vs Shield

In-depth architectural comparison of the Scamverify MCP and Shield 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

Scamverify MCP

Security · Local stdio

Quality: 55/100 (Good) | Auth: API Key required

Shield

Security · Local stdio

Quality: 63/100 (Good) | Auth: No auth required

Verdict Summary: Choose Scamverify MCP if you need specialized Security tools running via a local process. Choose Shield 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 Scamverify MCP when:

You need dedicated capabilities in the Security domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Freemium).
You have access to required keys: SCAMVERIFY_API_KEY.
Primary tools included: check_phone, check_url, check_text.

Explore Scamverify MCP Details

Choose Shield 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: Pre-execution MCP call guardrails, TOFU tool-catalog pinning, Tool description and result scanning.

Feature & Specification Comparison

Specification	Scamverify MCP scamverifyai Security	Shield AperionAI Security
Summary	AI-powered scam and threat verification MCP server. Check phone numbers, URLs, text messages, emails, documents, and QR codes against 8M+ threat intelligence records (FTC/FCC complaints, carrier analysis, URLhaus, ThreatFox). Returns risk scores, verdicts, and detailed signals. 10 tools, OAuth 2.1 + API key auth, Streamable HTTP transport.	Local guardrail proxy for AI coding agents. Wraps any MCP server (stdio or Streamable HTTP) and blocks destructive tool calls — DROP TABLE, rm -rf, force-push — before they execute. MCP supply-chain protection: TOFU tool-catalog pinning against rug pulls, plus tool-description and tool-result scanning for tool poisoning and prompt injection. 51 starter rules, approval gates, audit logging. Single binary, Apache-2.0.

Tools & Capabilities Breakdown

Scamverify MCP Tools (10)

check_phone

Look up a US phone number for scam reports, carrier info, robocall flags, and community reports. Returns risk score (0-100), verdict, and detailed signals from FTC, FCC, carrier, and community data.

check_url

Check a website URL for safety. Analyzes domain age, SSL certificate, redirect chains, brand impersonation, Google Web Risk, URLhaus, ThreatFox, and community reports.

check_text

Analyze a text/SMS message for scam indicators. Extracts and cross-references embedded phone numbers and URLs. AI identifies scam type, red flags, and risk level.

check_email

Analyze an email for phishing indicators. Checks sender domain, email headers (SPF/DKIM/DMARC), brand impersonation, embedded URLs and phone numbers.

check_document

Analyze a document image for scam indicators. Uses vision AI to extract entities (addresses, officials, citations, phone numbers) and verifies them against government databases.

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).

Scamverify MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "scamverifyai-scamverify-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@scamverifyai/scamverify-mcp"
      ],
      "env": {
        "SCAMVERIFY_API_KEY": "YOUR_SCAMVERIFY_API_KEY_HERE"
      }
    }
  }
}

Shield Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "aperionai-shield": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-postgres"
      ]
    }
  }
}

Frequently Asked Questions

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

More alternatives to Scamverify MCP More alternatives to Shield Security category hub Canonical compare URL