Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

EVMole

NPM · EVMOLE-MCP · SCANNED SEP 20

Local structured analysis of deployed EVM runtime bytecode

Available components

npm · evmole-mcp 92
0 this week 92 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 97 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to cdump/evmole). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 50 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 156 tokens (~156/item across 1 items; 1 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage83
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 50% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the EVMole MCP server?

EVMole runs locally as an npm package, launched with npx -y evmole-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · evmole-mcp

# add to Claude Code
claude mcp add cdump-evmole -- npx -y evmole-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "cdump-evmole": {
      "command": "npx",
      "args": [
        "-y",
        "evmole-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "cdump-evmole": {
      "command": "npx",
      "args": [
        "-y",
        "evmole-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add cdump-evmole -- npx -y evmole-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cdump-evmole": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "evmole-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add cdump-evmole --command npx --arg -y --arg evmole-mcp
# ~/.hermes/config.yaml
mcp_servers:
  cdump-evmole:
    command: "npx"
    args: ["-y", "evmole-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "cdump-evmole": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "evmole-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add cdump-evmole -t stdio -c npx -a -y evmole-mcp
// mcp.json
{
  "mcpServers": {
    "cdump-evmole": {
      "command": "npx",
      "args": [
        "-y",
        "evmole-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Sept 26 +1
    • Stability: 0.97 → pass security
  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 13 Sept 26 +1
    • Stability: 0.97 → pass security
  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 7 Sept 26 −3
    • Stability: pass → 0.80 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed npm/evmole-mcp@0.9.3

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo cdump/evmole
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/cdump/evmole/.github/workflows/build.yml@refs/heads/master
Rekor log index 2299111631
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:332ef9dba58dd0ae8315c142f86228efdf549dee4d07d838c52c6030241aa22f64c471a703cf278385e834a0dddd776c6db6c2efb2988a4ab5fe83240

Background: How many MCP packages publish verified provenance →

Dependencies 97 packages
Packages resolved 97
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 1 exposed · ~156 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
analyze_evm_bytecode ~156

Analyze deployed EVM runtime bytecode locally with EVMole. Extract function selectors, inferred arguments and mutability, persistent or transient storage access, metadata, disassembly, basic blocks, or a control-flow graph. This tool does not fetch contracts, decode calldata, verify source code, or fully decompile a contract.

NameTypeReqDescription
bytecodestringyesDeployed EVM runtime bytecode as hexadecimal; maximum 1 MiB.
includearray–Analysis features to include: selectors, arguments, stateMutability, storage, transientStorage, metadata, disassembly, basicBlocks, controlFlowGraph. arguments and stateMutability imply selectors.
limitnumber––
offsetnumber––

No output schema declared.

No examples provided.

Common questions

What is the EVMole MCP server?

EVMole is an MCP server listed in the public MCP registry as io.github.cdump/evmole. Local structured analysis of deployed EVM runtime bytecode. This page covers its npm package (evmole-mcp).

Is the EVMole MCP server safe to use?

EVMole scores 92 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the EVMole MCP server expose?

EVMole exposes 1 tool: analyze_evm_bytecode. Their descriptions and schemas cost roughly 156 tokens of context every time the server is loaded.

Is the EVMole MCP server still maintained?

EVMole is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the EVMole MCP server under?

EVMole declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.