What is the key difference between Basescope and Sicarius Guard?

Basescope belongs to the Security category with local stdio execution, while Sicarius Guard belongs to the Security category with local stdio execution.

How do I install Basescope or Sicarius Guard 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 Basescope and Sicarius Guard free or paid?

Basescope operates under a Free / Open Source model (No auth required). Sicarius Guard operates under a Freemium model (No auth required).

Which MCP server has more tools and community activity?

Basescope lists 12 tools with 1 views and 1 GitHub stars. Sicarius Guard lists 11 tools with 2 views and 2 GitHub stars.

Can I use both Basescope and Sicarius Guard 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

Basescope vs Sicarius Guard

In-depth architectural comparison of the Basescope and Sicarius Guard 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

Basescope

Security · Local stdio

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

Sicarius Guard

Security · Local stdio

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

Verdict Summary: Choose Basescope if you need specialized Security tools running via a local process. Choose Sicarius Guard 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 Basescope 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_token_safety, check_address_safety, get_token_approvals.

Explore Basescope Details

Choose Sicarius Guard when:

You need dedicated capabilities in the Security domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Freemium).
You have access to required keys: HELIUS_RPC_URL, BIRDEYE_API_KEY.
Primary tools included: check_token_safety, check_honeypot, check_holder_concentration.

Explore Sicarius Guard Details

Feature & Specification Comparison

Specification	Basescope chasdaddy Security	Sicarius Guard Chronolapse411 Security
Summary	The read-only safety layer for onchain AI agents. 13 read-only tools on Base + EVM: token/contract safety (honeypot & rug-pull checks cross-referenced across GoPlus + honeypot.is), risky-approval detection, verified-source lookup, balances, ENS + Basenames, gas, and prices. No private keys, no required API keys. npx -y basescope	Solana token safety oracle for AI agents and trading bots. Byte-level SPL mint analysis, honeypot detection, freeze/mint authority checks, Birdeye market enrichment, and composite risk scoring. Deployed on Google Cloud Run.
Category & Scope

Tools & Capabilities Breakdown

Basescope Tools (12)

check_token_safety

Honeypot / rug assessment: honeypot check, buy/sell tax, mint/blacklist/pausable/self-destruct authority, verified source, holder count → a normalized `riskLevel` (`critical`/`high`/`medium`/`low`). Cross-checks GoPlus + honeypot.is.

check_address_safety

Reputation check against known-malicious databases (phishing, sanctioned, scam, money-laundering, mixer, …).

get_token_approvals

Lists a wallet's outstanding ERC-20 approvals and flags risky spenders — the #1 wallet-drain vector — surfacing risky ones first.

get_verified_source

Whether a contract's source is verified (via Sourcify) + its name, compiler, and function list.

inspect_contract

Is the address a contract? Bytecode size + transaction count.

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

Basescope Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "chasdaddy-basescope": {
      "command": "npx",
      "args": [
        "-y",
        "basescope"
      ]
    }
  }
}

Sicarius Guard Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "chronolapse411-sicarius-guard": {
      "command": "npx",
      "args": [
        "-y",
        "sicarius-guard"
      ],
      "env": {
        "HELIUS_RPC_URL": "YOUR_HELIUS_RPC_URL_HERE",
        "BIRDEYE_API_KEY": "YOUR_BIRDEYE_API_KEY_HERE"
      }
    }
  }
}

Frequently Asked Questions

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

More alternatives to Basescope More alternatives to Sicarius Guard Security category hub