Ext Ops Panel
Open dashboard
Comparison

Agent Utils (x402) vs io.github.BlockRunAI/blockrun-mcp

Agent Utils (x402) is an MCP server published by agent-utils-x402-production.revenue-agent-jw.workers.dev. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.BlockRunAI/blockrun-mcp is an MCP server published by BlockRunAI. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). 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
MarketplaceAgent Utils (x402)io.github.BlockRunAI/blockrun-mcp
Official MCP Registry Listed
Version: 1.9.0
No figure published
Not marked · First seen
Listed
Version: 0.55.8
Downloads/month (npm): 4 670
Downloads/week (npm): 1 974
Forks (GitHub): 42
Stars (GitHub): 390
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 0.55.7
Downloads/month (npm): 4 670
Downloads/week (npm): 1 974
Forks (GitHub): 42
Stars (GitHub): 390
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

Agent Utils (x402) vs io.github.BlockRunAI/blockrun-mcp
FactAgent Utils (x402)io.github.BlockRunAI/blockrun-mcp
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub390
Forks (GitHub) (differs)No figure on GitHub42
Last release (differs)2026-11-09 (worse)2026-11-10 (better)
Where it runs (differs)Remote server (agent-utils-x402-production.revenue-agent-jw.workers.dev/mcp)On your machine (@blockrun/mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published3, secrets among them: 3
Licence (differs)Not statedMIT
Repository (differs)Not statedgithub.com/blockrunai/blockrun-mcp
Changes in the last 7 days (differs)96
First seen (differs)2026-10-222026-10-11
Endpoint at the last check (differs)Responded 5 h agono remote endpoint we check

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

Agent Utils (x402)

In its own words, on Official MCP Registry:

Public records, email-auth, OSV vulns, PII redact and web reader for agents. x402 USDC

io.github.BlockRunAI/blockrun-mcp

In its own words, on Official MCP Registry:

Web search, deep research, prediction markets & crypto data for AI agents. Pay per call via x402.

How to run each

Agent Utils (x402) As a remote MCP server

Claude Code
claude mcp add --transport http agent-utils https://agent-utils-x402-production.revenue-agent-jw.workers.dev/mcp

io.github.BlockRunAI/blockrun-mcp As a local MCP server: npm package

Claude Code
claude mcp add --env "BLOCKRUN_API_KEY=<YOUR_BLOCKRUN_API_KEY>" --env "BLOCKRUN_WALLET_KEY=<YOUR_BLOCKRUN_WALLET_KEY>" --env "SOLANA_WALLET_KEY=<YOUR_SOLANA_WALLET_KEY>" --transport stdio blockrun-mcp -- npx -y @blockrun/mcp

Requires: BLOCKRUN_API_KEY (secret), BLOCKRUN_WALLET_KEY (secret), SOLANA_WALLET_KEY (secret)

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

Only Agent Utils (x402) has a remote endpoint we 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

The marketplaces of Agent Utils (x402) publish no settings it asks for, so we do not compare settings.

What it can do: Agent Utils (x402) · What it can do: io.github.BlockRunAI/blockrun-mcp · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). 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