Ext Ops Panel
Open dashboard
Comparison

dev.onchainforensics/forensics-mcp vs io.github.junct-bot/blockscout-mcp

dev.onchainforensics/forensics-mcp is an MCP server published by onchainforensics.dev. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.junct-bot/blockscout-mcp is an MCP server published by junct-bot. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacedev.onchainforensics/forensics-mcpio.github.junct-bot/blockscout-mcp
Official MCP Registry Listed
Version: 1.1.1
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.1.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

dev.onchainforensics/forensics-mcp vs io.github.junct-bot/blockscout-mcp
Factdev.onchainforensics/forensics-mcpio.github.junct-bot/blockscout-mcp
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Remote server or your machineRemote server (blockscout.mcp.junct.dev/mcp)
Transport (differs)stdio, Streamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/leohoudinisanders-byte/forensics-mcpgithub.com/junct-bot/blockscout-mcp
Changes in the last 7 days (differs)30
First seen (differs)2026-10-202026-10-11
Endpoint at the last check (differs)Status out of date: last check 31 h ago returned HTTP 200No HTTP response at the last check (7 h ago)

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

dev.onchainforensics/forensics-mcp

In its own words, on Official MCP Registry:

Token due-diligence for AI agents: grade verdicts, mint activity, settlement safety.

io.github.junct-bot/blockscout-mcp

In its own words, on Official MCP Registry:

Blockscout - 56 tools for data, metrics, and on-chain analytics

How to run each

dev.onchainforensics/forensics-mcp As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio forensics-mcp -- npx -y onchain-forensics-mcp

io.github.junct-bot/blockscout-mcp As a remote MCP server

Claude Code
claude mcp add --transport http blockscout-mcp https://blockscout.mcp.junct.dev/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only the endpoint of dev.onchainforensics/forensics-mcp responded at the last daily check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: dev.onchainforensics/forensics-mcp · What it can do: io.github.junct-bot/blockscout-mcp · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built