io.github.calintzy/evmscope
NPM · EVMSCOPE · SCANNED SEP 20
EVM blockchain intelligence toolkit for AI agents. 20 tools across 5 chains. Zero config.
Available components
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 111 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 193 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1697 tokens (~84/item across 20 items; 20 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 20 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 20 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
How do I install the io.github.calintzy/evmscope MCP server?
io.github.calintzy/evmscope runs locally as an npm package, launched with npx -y evmscope. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · evmscope
claude mcp add calintzy-evmscope -- npx -y evmscope
{
"mcpServers": {
"calintzy-evmscope": {
"command": "npx",
"args": [
"-y",
"evmscope"
]
}
}
} {
"servers": {
"calintzy-evmscope": {
"command": "npx",
"args": [
"-y",
"evmscope"
]
}
}
} codex mcp add calintzy-evmscope -- npx -y evmscope
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"calintzy-evmscope": {
"type": "local",
"command": [
"npx",
"-y",
"evmscope"
],
"enabled": true
}
}
} openclaw mcp add calintzy-evmscope --command npx --arg -y --arg evmscope
mcp_servers:
calintzy-evmscope:
command: "npx"
args: ["-y", "evmscope"] {
"McpServers": {
"calintzy-evmscope": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"evmscope"
]
}
}
} assistant mcp add calintzy-evmscope -t stdio -c npx -a -y evmscope
{
"mcpServers": {
"calintzy-evmscope": {
"command": "npx",
"args": [
"-y",
"evmscope"
]
}
}
} 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.
- 19 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.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 14 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.
- 12 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.
- 10 Sept 26 −3
- Stability: pass → 0.80 functional
- 9 Sept 26 +1
- Stability: 0.97 → pass security
- 7 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.
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/evmscope@1.5.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 111 packages
| Packages resolved | 111 |
|---|---|
| Stale | 31 |
| 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 →
checkHoneypot ~77
토큰의 허니팟(사기) 여부를 탐지합니다 (매수/매도 세금, 위험도, 플래그, Honeypot.is 기반)
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | EVM 체인 |
| token | string | yes | 토큰 주소 (0x...) 또는 심볼 |
No output schema declared.
No examples provided.
compareGas ~37
5개 EVM 체인의 가스비를 한 번에 비교합니다 (최저가 순 정렬, USD 예상 비용 포함)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
decodeTx ~77
트랜잭션을 구조화된 JSON으로 해석합니다 (함수명, 파라미터, 이벤트 로그, 가스 정보)
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | 체인 (ethereum, polygon, arbitrum, base, optimism) |
| txHash | string | yes | 트랜잭션 해시 (0x...) |
No output schema declared.
No examples provided.
getApprovalStatus ~101
ERC-20 토큰 승인(allowance) 상태를 조회합니다. 주요 프로토콜 자동 체크, 리스크 레벨 판정
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | EVM 체인 |
| owner | string | yes | 지갑 주소 |
| spender | string | – | 특정 spender 주소 (미지정 시 주요 프로토콜 자동 조회) |
| token | string | yes | 토큰 심볼 (USDC, USDT) 또는 contract address |
No output schema declared.
No examples provided.
getBalance ~91
지갑 주소의 네이티브 토큰 + ERC-20 토큰 잔고를 조회합니다 (USD 환산 포함)
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | 조회할 지갑 주소 (0x...) |
| chain | string | – | EVM 체인 |
| tokens | array | – | 조회할 토큰 심볼 목록 (기본: USDC, USDT, DAI, WETH) |
No output schema declared.
No examples provided.
getBridgeRoutes ~116
크로스체인 브릿지 경로를 조회합니다 (LI.FI 기반, 비용/시간/경로 비교, 최적 경로 추천)
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | 전송 수량 (사람이 읽을 수 있는 단위, 예: '100') |
| fromChain | string | yes | 출발 체인 |
| toChain | string | yes | 도착 체인 |
| token | string | yes | 토큰 심볼 (USDC, ETH 등) 또는 컨트랙트 주소 |
No output schema declared.
No examples provided.
getContractABI ~68
컨트랙트 ABI를 조회합니다 (Etherscan → Sourcify 폴백, verified contract 필요)
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | 컨트랙트 주소 (0x...) |
| chain | string | – | 체인 (ethereum, polygon, arbitrum, base, optimism) |
No output schema declared.
No examples provided.
getContractEvents ~102
컨트랙트 이벤트 로그를 조회합니다 (ABI 자동 디코딩, 최근 1000블록 기본, 블록 범위 지정 가능)
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | 컨트랙트 주소 (0x...) |
| chain | string | – | EVM 체인 |
| fromBlock | number | – | 시작 블록 (기본: 최근 1000블록) |
| limit | number | – | 최대 이벤트 수 (기본 20) |
No output schema declared.
No examples provided.
getGasPrice ~45
현재 가스비를 slow/normal/fast 3단계로 조회합니다 (Gwei + USD 예상 비용)
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | EVM 체인 |
No output schema declared.
No examples provided.
getProtocolTVL ~73
DeFi 프로토콜의 TVL(Total Value Locked)을 조회합니다 (DefiLlama 기반, 체인별 분포, 24h/7d 변동률)
| Name | Type | Req | Description |
|---|---|---|---|
| protocol | string | yes | 프로토콜 이름 (Aave, Uniswap 등) 또는 DefiLlama slug |
No output schema declared.
No examples provided.
getSwapQuote ~129
DEX 스왑 견적을 조회합니다 (ParaSwap 기반, 최적 경로, 가스비 포함, ETH→WETH 자동 치환)
| Name | Type | Req | Description |
|---|---|---|---|
| amountIn | string | yes | 매도 수량 (사람이 읽을 수 있는 단위, 예: '1.5') |
| chain | string | – | EVM 체인 |
| tokenIn | string | yes | 매도 토큰 심볼 (ETH, USDC) 또는 contract address |
| tokenOut | string | yes | 매수 토큰 심볼 (USDC, WETH) 또는 contract address |
No output schema declared.
No examples provided.
getTokenHolders ~101
토큰의 상위 홀더를 조회합니다 (Ethereum: Ethplorer, 기타 체인: Etherscan 집계, 주소/점유율/잔고)
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | EVM 체인 |
| limit | number | – | 조회할 홀더 수 (기본 10, 최대 100) |
| token | string | yes | 토큰 주소 (0x...) 또는 심볼 (USDC, WETH 등) |
No output schema declared.
No examples provided.
getTokenInfo ~70
ERC-20 토큰의 메타데이터(이름, 심볼, 소수점, 총공급량)를 조회합니다
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | EVM 체인 |
| token | string | yes | 토큰 심볼 (USDC) 또는 contract address (0x...) |
No output schema declared.
No examples provided.
getTokenPrice ~67
토큰의 현재 가격(USD)과 24시간 변동률, 시가총액, 거래량을 조회합니다
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | EVM 체인 |
| token | string | yes | 토큰 심볼 (ETH, USDC) 또는 contract address |
No output schema declared.
No examples provided.
getTxStatus ~69
트랜잭션 상태를 조회합니다 (pending/success/failed, confirmations, gas 사용량)
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | 체인 (ethereum, polygon, arbitrum, base, optimism) |
| txHash | string | yes | 트랜잭션 해시 (0x...) |
No output schema declared.
No examples provided.
getWhaleMovements ~113
대규모 토큰 전송(고래 이동)을 추적합니다. 거래소 입출금 방향 판정, 요약 통계 포함
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | EVM 체인 |
| limit | number | – | 반환할 최대 이동 수 (기본: 10) |
| minValueUsd | number | – | 최소 USD 금액 (기본: $100,000) |
| token | string | yes | 토큰 심볼 (USDC, USDT) 또는 contract address |
No output schema declared.
No examples provided.
getYieldRates ~104
DeFi 수익률(APY)을 조회합니다 (DefiLlama 기반, 프로토콜/체인별 필터, TVL 기준 상위 10개 풀)
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | 체인 필터 (Ethereum, Polygon 등) |
| minTvl | number | – | 최소 TVL (USD, 기본 $1M) |
| protocol | string | – | 프로토콜 이름 필터 (aave-v3, compound-v3 등) |
No output schema declared.
No examples provided.
identifyAddress ~74
주소를 식별합니다 (거래소, DeFi 프로토콜, 고래 지갑, 컨트랙트/EOA 분류)
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | 이더리움 주소 (0x...) |
| chain | string | – | 체인 (ethereum, polygon, arbitrum, base, optimism) |
No output schema declared.
No examples provided.
resolveENS ~58
ENS 이름 ↔ 이더리움 주소를 양방향으로 해석합니다 (Ethereum mainnet 전용)
| Name | Type | Req | Description |
|---|---|---|---|
| nameOrAddress | string | yes | ENS 이름 (vitalik.eth) 또는 이더리움 주소 (0x...) |
No output schema declared.
No examples provided.
simulateTx ~125
트랜잭션을 시뮬레이션합니다 (eth_call + estimateGas, 가스비 USD 환산, revert reason 디코딩)
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | EVM 체인 |
| data | string | – | 호출 데이터 (hex, 0x...) |
| from | string | yes | 발신자 주소 (0x...) |
| to | string | yes | 수신자/컨트랙트 주소 (0x...) |
| value | string | – | 전송할 네이티브 토큰 수량 (예: '0.1') |
No output schema declared.
No examples provided.
What is the io.github.calintzy/evmscope MCP server?
io.github.calintzy/evmscope is an MCP server listed in the public MCP registry as io.github.calintzy/evmscope. EVM blockchain intelligence toolkit for AI agents. 20 tools across 5 chains. Zero config. This page covers its npm package (evmscope).
Is the io.github.calintzy/evmscope MCP server safe to use?
io.github.calintzy/evmscope scores 83 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. 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 io.github.calintzy/evmscope MCP server expose?
io.github.calintzy/evmscope exposes 20 tools: getTokenPrice, getGasPrice, getBalance, getTokenInfo, resolveENS, and 15 more. Their descriptions and schemas cost roughly 1,697 tokens of context every time the server is loaded.
Is the io.github.calintzy/evmscope MCP server still maintained?
io.github.calintzy/evmscope 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 io.github.calintzy/evmscope MCP server under?
io.github.calintzy/evmscope declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.