EVMole vs Roc MCP

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

EVMole logoEVMoleDeveloper Tools · Local subprocess (stdio)Local structured analysis of deployed EVM runtime bytecode51GoodAuth: not declared
R
Roc MCPDeveloper Tools
ROC biometrics & computer vision: face, LPR, OCR, pedestrian, vehicle, gun detection.37FairAuth: not declared

Verdict: choose EVMole for developer tools work as a local process; choose Roc MCP for developer tools. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

EVMole logoChoose EVMole when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
Explore EVMole

R
Choose Roc MCP when

  • You need dedicated capabilities in the Developer Tools domain.
Explore Roc MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecEVMole logoEVMole
R
Roc MCP
CategoryDeveloper ToolsDeveloper Tools
Quality signal51/100 · Good37/100 · Fair
Install commandConfirmedNot confirmed yet
TransportLocal subprocess (stdio)—
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars472—
Directory activity 0 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

EVMole tools

No tool names declared yet. Check the project README from the listing page.

Roc MCP tools

No tool names declared yet. Check the project README from 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.

EVMole

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

Roc MCP

No confirmed install command for Roc MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.

Frequently asked questions

EVMole is categorized under Developer Tools and uses a local stdio subprocess. Roc MCP belongs to Developer Tools and uses an install path we have not confirmed yet. Pick EVMole for developer tools work and Roc MCP for developer tools.

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. Roc MCP has no confirmed install command yet — follow its own setup instructions.

EVMole has no declared pricing — check the project's own site. Roc MCP has no declared pricing — check the project's own site. 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 evmole and mcp-23 as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, EVMole has a quality signal of 51/100 (Good) with 0 views, 0 installs and 472 GitHub stars. Roc MCP has 37/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.