EVMole vs Froglet

A side-by-side look at the EVMole and Froglet 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 declaredFroglet logoFrogletDeveloper Tools · Local subprocess (stdio)Run hosted proofs, signed receipts, service discovery, and local install planning.45FairAuth: not declared

Verdict: choose EVMole for developer tools work as a local process; choose Froglet for developer tools as a local process. 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

Froglet logoChoose Froglet when

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

Feature & specification comparison

Rows where the two servers differ are marked.

SpecEVMole logoEVMoleFroglet logoFroglet
CategoryDeveloper ToolsDeveloper Tools
Quality signal51/100 · Good45/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars4728
Directory activity 0 views 0 installs 0 upvotes 3 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.

Froglet 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"
      ]
    }
  }
}

Froglet

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

Frequently asked questions

EVMole is categorized under Developer Tools and uses a local stdio subprocess. Froglet belongs to Developer Tools and uses a local stdio subprocess. Pick EVMole for developer tools work and Froglet 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.

EVMole has no declared pricing — check the project's own site. Froglet is listed as free. 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 froglet 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. Froglet has 45/100 (Fair) with 3 views, 0 installs and 8 GitHub stars.