Contract Security Scanner vs TokenSave

In-depth architectural comparison of the Contract Security Scanner and TokenSave 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.

Which MCP Server Should You Choose?

C

Choose Contract Security Scanner when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: scan_contract, compare_security_models, audit_checklist.

Explore Contract Security Scanner Details

Choose TokenSave when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore TokenSave Details

Feature & Specification Comparison

Specification	C Contract Security Scanner Developer Tools	TokenSave Developer Tools
Summary	MCP smart contract scanner with NEAR-focused security context.	Code intelligence for 15+ languages: semantic graph queries instead of file reads. 37 MCP tools.
Category & Scope	Developer Tools	Developer Tools
Quality signal

Tools & Capabilities Breakdown

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

{
  "mcpServers": {
    "contract-security-scanner-2": {
      "command": "npx",
      "args": [
        "-y",
        "contract-security-scanner-2"
      ]
    }
  }
}

{
  "mcpServers": {
    "tokensave": {
      "command": "npx",
      "args": [
        "-y",
        "@colbymchenry/codegraph"
      ]
    }
  }
}

Related MCP Server Comparisons