# Blockscout (npm · @pipeworx/mcp-blockscout)

Blockscout MCP — multi-chain block-explorer aggregate

- Trust score: 83/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-blockscout/blockscout-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-blockscout/blockscout-mcp)
- npm · `@pipeworx/mcp-blockscout`: 83/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-blockscout/pipeworx-mcp-blockscout.md), [page](https://verifymcp.io/servers/pipeworx-io-blockscout/pipeworx-mcp-blockscout)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-blockscout`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-blockscout).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 5 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 854 tokens (~106/item across 8 items; 8 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 80/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 39% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Blockscout MCP server?

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

### Claude

```bash
claude mcp add pipeworx-io-blockscout -- npx -y @pipeworx/mcp-blockscout
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-blockscout": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-blockscout"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-blockscout": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-blockscout"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-blockscout -- npx -y @pipeworx/mcp-blockscout
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-blockscout": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-blockscout"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-blockscout --command npx --arg -y --arg @pipeworx/mcp-blockscout
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-blockscout:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-blockscout"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-blockscout": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-blockscout"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-blockscout -t stdio -c npx -a -y @pipeworx/mcp-blockscout
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-blockscout": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-blockscout"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 83, +1)

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

### 2026-11-03 (score 82, +1)

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

### 2026-11-01 (score 81, +1)

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

### 2026-10-31 (score 80, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-30 (score 65, −14)

- [security regression] Malware scan: pass → unverified
- [functional regression] Security disclosure: unverified → fail
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-29 (score 79)

First indexed and scored.

## MCP tools (8)

### `get_address` (~142 tokens)

"What's the balance of [wallet]" / "Ethereum / Polygon / Arbitrum / Base wallet info" / "address summary for [0x...]" / "what tokens does [wallet] hold" — on-chain address summary across 20+ EVM chains (Ethereum, Optimism, Polygon, Arbitrum, Base, BNB, Gnosis, Celo, zkSync, Scroll, Linea, Blast, …). Returns balance, transaction count, token-holding stats. Pass chain slug + 0x address.

Input parameters:

- `address` (string, required): 0x address
- `chain` (string, required): Chain slug (see list_chains)

### `get_address_txns` (~117 tokens)

"Recent transactions of [wallet]" / "tx history for [0x...]" / "what has [address] done lately" — recent transactions for an EVM address. Pass chain + 0x address; optionally filter by direction (to/from). Use for wallet-activity audit, fund-flow tracing.

Input parameters:

- `address` (string, required)
- `chain` (string, required)
- `filter` (string): to | from (default both)
- `limit` (number): Max returned (default 25, max ~50)

### `get_address_token_transfers` (~130 tokens)

"Token transfers / NFT activity for [wallet]" / "ERC-20 / ERC-721 / ERC-1155 transfers in/out of [0x...]" / "what tokens did [address] send or receive" — token transfer log for an EVM address. Use for tracing NFT activity, stablecoin flows, airdrops, or specific-token movement (filter via `token` arg).

Input parameters:

- `address` (string, required)
- `chain` (string, required)
- `limit` (number): Default 25
- `token` (string): Restrict to a specific token contract

### `get_transaction` (~88 tokens)

"Look up transaction [0xhash]" / "what happened in tx [hash]" / "decode tx [X]" — full transaction detail (from, to, value, method, status, gas, decoded calldata). Pass chain + tx_hash. Use for forensic tx analysis, MEV inspection, contract-call breakdown.

Input parameters:

- `chain` (string, required)
- `tx_hash` (string, required)

### `get_token` (~81 tokens)

"Token info for [contract]" / "what is contract [0x...]" / "ERC-20 / NFT metadata for [token]" — token contract metadata: name, symbol, decimals, total supply, holder count, contract type. Use for on-chain token characterization.

Input parameters:

- `chain` (string, required)
- `contract` (string, required): Token contract address

### `get_block` (~87 tokens)

"Block [N] details" / "what was in block [hash]" / "miner / proposer of block [X]" — block detail by number or hash. Returns timestamp, gas used, transaction count, miner / validator, parent / next blocks. Use for chain forensics, block-time analysis.

Input parameters:

- `block_number_or_hash` (string, required)
- `chain` (string, required)

### `search` (~90 tokens)

"Search [chain] for [query]" / "is [string] a token / contract / address on [chain]" — universal block-explorer search across addresses, transactions, blocks, tokens, and ENS-style names on a specific EVM chain. Use when you don't know yet whether the input is an address / hash / token symbol.

Input parameters:

- `chain` (string, required)
- `query` (string, required)

### `list_chains` (~65 tokens)

List all EVM chain slugs and Blockscout host URLs supported by this pack (20+ chains: eth, polygon, arbitrum, base, optimism, bnb, gnosis, zksync-era, etc.). Use to discover valid chain values for other tools.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-blockscout/pipeworx-mcp-blockscout#diagnostics

## Score history

- 2026-11-05: 83
- 2026-11-04: 82
- 2026-11-03: 82
- 2026-11-02: 81
- 2026-11-01: 81
- 2026-10-31: 80
- 2026-10-30: 65
- 2026-10-29: 79

## Common questions

### What is the Blockscout MCP server?

Blockscout is an MCP server listed in the public MCP registry as io.github.pipeworx-io/blockscout. Blockscout MCP, multi-chain block-explorer aggregate. This page covers its npm package (@pipeworx/mcp-blockscout).

### Is the Blockscout MCP server safe to use?

Blockscout scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting 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 Blockscout MCP server expose?

Blockscout exposes 8 tools: get_address, get_address_txns, get_address_token_transfers, get_transaction, get_token, and 3 more. Their descriptions and schemas cost roughly 800 tokens of context every time the server is loaded.

### Is the Blockscout MCP server still maintained?

Blockscout 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 Blockscout MCP server under?

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

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-blockscout
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-blockscout
- Repository: https://github.com/pipeworx-io/mcp-blockscout
- Website: https://pipeworx.io/packs/blockscout
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-blockscout/pipeworx-mcp-blockscout.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-blockscout/pipeworx-mcp-blockscout.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-blockscout/pipeworx-mcp-blockscout