What is the key difference between Shieldapi MCP and Trustsource?

Shieldapi MCP belongs to the Security category with local stdio execution, while Trustsource belongs to the Security category with cloud HTTP/SSE execution.

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

Shieldapi MCP operates under a Freemium model (other). Trustsource operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Shieldapi MCP lists 10 tools with 4 views and 1 GitHub stars. Trustsource lists 6 tools with 1 views and 0 GitHub stars.

Can I use both Shieldapi MCP and Trustsource 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

Shieldapi MCP vs Trustsource

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

Shieldapi MCP

Security · Local stdio

Quality: 56/100 (Good) | Auth: other

Trustsource

Security · Remote HTTP/SSE

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

Verdict Summary: Choose Shieldapi MCP if you need specialized Security tools running via a local process. Choose Trustsource if your workspace requires Security integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Shieldapi MCP when:

You need dedicated capabilities in the Security domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: other (Freemium).
You have access to required keys: SHIELDAPI_URL, SHIELDAPI_WALLET_PRIVATE_KEY.
Primary tools included: check_url, check_password, check_password_range.

Explore Shieldapi MCP Details

Choose Trustsource when:

You need dedicated capabilities in the Security domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: PAY_TO_ADDRESS.
Primary tools included: Prompt-injection-aware safe page fetching, Composite URL safety verdicts, Domain trust scoring.

Feature & Specification Comparison

Specification	Shieldapi MCP alberthild Security	Trustsource Security
Summary	Security intelligence for AI agents: password breach checks (900M+ HIBP hashes), email/domain/IP/URL reputation, prompt injection detection (200+ patterns), and skill supply chain scanning. Pay-per-request via x402 USDC micropayments or free demo mode, no API key needed.	x402-paid domain verification for AI agents — trustscore, SSL, security headers, robots.
Category & Scope	Security

Tools & Capabilities Breakdown

Shieldapi MCP Tools (10)

check_url

Check a URL for malware, phishing, and other threats. Uses URLhaus + heuristic analysis.

check_password

Check if a password hash (SHA-1) has been exposed in known data breaches via HIBP.

check_password_range

Look up a SHA-1 hash prefix in the HIBP k-Anonymity database.

check_domain

Check domain reputation: DNS records, blacklists (Spamhaus, SpamCop, SORBS), SPF/DMARC, SSL.

check_ip

Check IP reputation: blacklists, Tor exit node detection, reverse DNS.

check_email

Check if an email address has been exposed in known data breaches via HIBP.

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

Shieldapi MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "alberthild-shieldapi-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "shieldapi-mcp"
      ],
      "env": {
        "SHIELDAPI_URL": "YOUR_SHIELDAPI_URL_HERE",
        "SHIELDAPI_WALLET_PRIVATE_KEY": "YOUR_SHIELDAPI_WALLET_PRIVATE_KEY_HERE"
      }
    }
  }
}

Trustsource Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "trustsource": {
      "url": "https://api.cdp.coinbase.com/platform/v2/x402"
    }
  }
}

Frequently Asked Questions

Shieldapi MCP is categorized under Security and uses a local stdio subprocess. In contrast, Trustsource belongs to Security using remote streaming HTTP/SSE transport. Select Shieldapi MCP when you need capabilities focused on security and Trustsource when you require tools for security.

More alternatives to Shieldapi MCP More alternatives to Trustsource Security category hub