@pipeworx/mcp-blockscout
Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.
Needs to start: nothing
Returns a result when called with no setup: 1 of 1 tool tried
Contacts while installing and starting: gateway.pipeworx.io
What it contacted
gateway.pipeworx.io
Hosts it looked up or connected to while installing and starting with no input, watched from outside its sandbox. The npm registry is left out. Says nothing about what its tools contact when called.
Starting it
npx -y @pipeworx/mcp-blockscout@0.2.1
Installing a package runs its code. Use a sandbox for anything you have not read.
Calling its tools
1 tool that takes no input and looks read-only was called once with nothing. 1 returned a result.
blockscout_list_chains | Returned a result 1.9 s · 1,345 characters |
During the calls it contacted nothing it had not already contacted.
Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.
What its tools tell an agent
In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.
Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.
Tools
blockscout_get_address chain, address
"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.
get_address_txns chain, address, limit, filter
"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.
get_address_token_transfers chain, address, token, limit
"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).
blockscout_get_transaction chain, tx_hash
"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.
blockscout_get_token chain, contract
"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.
blockscout_get_block chain, block_number_or_hash
"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.
blockscout_search chain, query
"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.
blockscout_list_chains
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.
Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.
Install facts
| License | MIT |
|---|---|
| Needs | node >=18 |
| Source | github.com/pipeworx-io/mcp-blockscout |
| Install scripts | None declared by it or anything installed with it. |
| Tarball | sha512-wuk2UkHCFPamt0IZbAJih6bhQ/VbyBZr3JLJAiwysNCqiMe9aaEtDe58swe5HerR5OgCxopB8esWftUug7OvFw== |
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/%40pipeworx/mcp-blockscout)
New version out? Ask for a fresh report.