Ext Ops Panel
Open dashboard
Comparison

DYOE Trust Tools (x402) vs Fairquery Agent Trust & Data Safety

DYOE Trust Tools (x402) is an MCP server published by bjyoe2016. Marketplaces we read that list it: 1 (Official MCP Registry). Fairquery Agent Trust & Data Safety is an MCP server published by fairquery. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. 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
MarketplaceDYOE Trust Tools (x402)Fairquery Agent Trust & Data Safety
Official MCP Registry Listed
Version: 1.0.0
Downloads/month (npm): 192
Downloads/week (npm): 96
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.1.2
Downloads/month (npm): 4 181
Downloads/week (npm): 2 434
Forks (GitHub): 0 (last published figure)
Stars (GitHub): 0 (last published figure)
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

DYOE Trust Tools (x402) vs Fairquery Agent Trust & Data Safety
FactDYOE Trust Tools (x402)Fairquery Agent Trust & Data Safety
Marketplaces that list it11
Stars (GitHub) (differs)00 (last published figure)
Forks (GitHub) (differs)00 (last published figure)
Last release (differs)Not published2026-10-27
Where it runs (differs)On your machine (dyoe-trust-mcp)Remote server or your machine
Transport (differs)stdiostdio, Streamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 11, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/bjyoe2016/dyoe-agent-tools-mcpgithub.com/fairquery/fairquery-agent-trust-mcp
Changes in the last 7 days00
First seen (differs)2026-10-212026-10-17
Endpoint at the last check (differs)no remote endpoint we checkResponded 26 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

DYOE Trust Tools (x402)

In its own words, on Official MCP Registry:

22 pay-per-call x402 tools for agents: scam checks, payment pre-flight, approvals, data. USDC/Base

Fairquery Agent Trust & Data Safety

In its own words, on Official MCP Registry:

PII/secret redaction, email checks, sanctions screening and OSV vulnerability lookups for AI agents.

How to run each

DYOE Trust Tools (x402) As a local MCP server: npm package

Claude Code
claude mcp add --env "WALLET_PRIVATE_KEY=<YOUR_WALLET_PRIVATE_KEY>" --transport stdio dyoe-trust-mcp -- npx -y dyoe-trust-mcp

Requires: WALLET_PRIVATE_KEY (secret)

Fairquery Agent Trust & Data Safety As a local MCP server: npm package

Claude Code
claude mcp add --env "APIFY_TOKEN=<YOUR_APIFY_TOKEN>" --transport stdio fairquery-agent-trust-mcp -- npx -y @fairquery/agent-trust-mcp

Requires: APIFY_TOKEN (secret)

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

Only Fairquery Agent Trust & Data Safety 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

Only DYOE Trust Tools (x402) asks for

  • DYOE_MAX_PAYMENT_USD
  • WALLET_PRIVATE_KEY (secret)

Only Fairquery Agent Trust & Data Safety asks for

  • APIFY_TOKEN (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: DYOE Trust Tools (x402) · What it can do: Fairquery Agent Trust & Data Safety · 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