EVMole
NPM · EVMOLE-MCP
Local structured analysis of deployed EVM runtime bytecode
Available components
Last scanned (5 hours ago)
Scores higher than 91% of npm servers
Category Crypto and Web3
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 1.30.0, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 94 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 22 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
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
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.
- 2 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 31 Oct 26 +1
- Stability: 0.97 → pass security
- 30 Oct 26 −1
- Stability: pass → 0.97 functional
- 28 Oct 26 0
- GHSA-f897-62hf-6gxq affects this package: high ▼ security
- 27 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 26 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 24 Oct 26 +1
- CVE-2023-54404 affects this package: high ▼ security
- Stability: 0.97 → pass security
- Security disclosure: unverified → fail ▼ functional
- 23 Oct 26 −1
- Security disclosure: fail → unverified ▼ functional
- Stability: pass → 0.97 functional
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 5 Nov 2026 · Analysed npm/evmole-mcp@0.9.4
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 | 3243814741 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:069c4bdd67d32917cb61f73c2b512ae93cb0bba30baca69f61a37b8af324720f84544682e76829f8f75757877e445d29dd7b5895c03e1504084269c5e |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 7 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-22jm-h49p-29qw | CVE-2026-111767 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L | yes |
| GHSA-46jr-4wx8-v453 | CVE-2026-111768 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-6prh-2h8m-c8cw | CVE-2026-111769 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N | yes |
| GHSA-6qxp-vccf-f47h | CVE-2026-104850 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N | yes |
| GHSA-f897-62hf-6gxq | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes | |
| GHSA-rvq5-wwqv-78pq | CVE-2026-111771 | medium | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N | yes |
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 94 packages
| Packages resolved | 94 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
analyze_evm_bytecode 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.
| Name | Type | Req | Description |
|---|---|---|---|
| bytecode | string | yes | Deployed EVM runtime bytecode as hexadecimal; maximum 1 MiB. |
| include | array | – | Analysis features to include: selectors, arguments, stateMutability, storage, transientStorage, metadata, disassembly, basicBlocks, controlFlowGraph. arguments and stateMutability imply selectors. |
| limit | number | – | – |
| offset | number | – | – |
No output schema declared.
No examples provided.
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
claude mcp add cdump-evmole -- npx -y evmole-mcp
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 87 out of 100 on VerifyMCP. We recorded 7 known advisories against it as of 5 November 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 5 November 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.