Ext Ops Panel
Open dashboard
Comparison

io.github.Bichev/agentradar vs io.github.verixiaapps/trustdex-x402

io.github.Bichev/agentradar is an MCP server published by Bichev. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.verixiaapps/trustdex-x402 is an MCP server published by verixiaapps. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-30. 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
Marketplaceio.github.Bichev/agentradario.github.verixiaapps/trustdex-x402
Official MCP Registry Listed
Version: 0.1.3
Downloads/month (npm): 194
Downloads/week (npm): 29
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 1.2.0
No figure published
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

io.github.Bichev/agentradar vs io.github.verixiaapps/trustdex-x402
Factio.github.Bichev/agentradario.github.verixiaapps/trustdex-x402
Marketplaces that list it11
Stars (GitHub) (differs)1No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@agentradar/mcp)Remote server (trustdex.app/api/v1/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 1Not published
LicenceNot statedNot stated
Repository (differs)github.com/bichev/agentradar-mcpNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkAnswered with HTTP 404 (7 days 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

io.github.Bichev/agentradar

In its own words, on Official MCP Registry:

Trust scoring, scam detection, and EAS attestations for ERC-8004 + x402 agents on Base.

io.github.verixiaapps/trustdex-x402

In its own words, on Official MCP Registry:

Free token-safety scans + paid x402 verdicts, signals, radar & EVM swap quotes for AI agents.

How to run each

io.github.Bichev/agentradar As a local MCP server: npm package

Claude Code
claude mcp add --env "AGENTRADAR_OPERATOR_KEY=<YOUR_AGENTRADAR_OPERATOR_KEY>" --transport stdio agentradar -- npx -y @agentradar/mcp

Requires: AGENTRADAR_OPERATOR_KEY (secret)

io.github.verixiaapps/trustdex-x402 As a remote MCP server

Claude Code
claude mcp add --transport http trustdex-x402 https://trustdex.app/api/v1/mcp

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

Only io.github.verixiaapps/trustdex-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 io.github.verixiaapps/trustdex-x402 publish no settings it asks for, so we do not compare settings.

What it can do: io.github.Bichev/agentradar · What it can do: io.github.verixiaapps/trustdex-x402 · 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