MCP Radar
Servidor MCP

What Agents Buy

com.whatagentsbuy/whatagentsbuy
Pagos y fintech Búsqueda e investigación Público y accesible MCP 2026-07-28

Qué hace este MCP

Evaluates x402 API sellers, checks payment safety and value, ranks providers by accuracy or demand, and reports on marketplace activity.

Capacidades

Herramientas

7 herramientas
check_before_paying
The one check before your agent pays
USE WHEN your agent is about to pay an x402 API and you want to know if it is safe and worth it. Returns one verdict for a URL or host in the `verdict` field (gate on that; `light` is the same decision as a colour, for display): CLEAR (nothing alarming), HOLD (pay but resolve the reasons), ABORT (do not pay without checking the live 402), UNRATED (no data). Also returns a confidence tier (verified = a payment to this seller settled AND produced a gradeable result, checked = free probe measured) and its payment history. Folds live price and payTo honesty, phantom paywalls, delivery receipts, and the wash/real-demand read into that one light. Pass detail:true for the full read. Whatever it says, still read the payTo and amount out of the live 402 and sign against those. (Formerly named preflight.)
Esquema de entrada 
{'type': 'object', 'required': ['url'], 'properties': {'url': {'type': 'string', 'description': 'Full URL or bare hostname, e.g. https://blockrun.ai/api/v1/exa/search or blockrun.ai'}, 'detail': {'type': 'boolean', 'description': 'Include the full payment-safety detail (live-402 honesty, demand shape, grades). Default false.'}}}
find_api
Find a payable API for a task
USE WHEN you need an API that does something and want payable options. Searches the whole x402 market for what you describe and returns a ranked, pre-vetted shortlist, proven-accurate sellers first, then payment-safety, then price. Covers every reachable endpoint, not just ones we have bought from. Next step: check_before_paying on your pick, then read the payTo from the live 402 and sign against it.
Esquema de entrada 
{'type': 'object', 'required': ['task'], 'properties': {'task': {'type': 'string', 'description': "What you need, in words or keywords, e.g. 'validate an email address', 'BTC price', 'geocode an address'"}, 'limit': {'type': 'integer', 'description': 'How many results (default 8, max 25)'}, 'max_price_usdc': {'type': 'number', 'description': 'Optional ceiling on the per-call price in USDC'}, 'min_reliability': {'type': 'integer', 'description': 'Optional floor on the reliability score 0-100 (default 0 = no floor; the whole reachable market)'}, 'allowed_verdicts': {'type': 'array', 'items': {'enum': ['CLEAR', 'HOLD', 'ABORT', 'UNRATED'], 'type': 'string'}, 'description': 'Optional policy filter: only return sellers whose current preflight verdict is in this list, e.g. ["CLEAR"]. Default: no filter, every result carries its verdict so you can decide.'}}}
known_payment_traps
How agents lose money paying APIs
USE WHEN writing payment code, or before trusting an unfamiliar seller. The field notes: each is a specific way an agent paying an API loses money or is misled, what it cost to learn, and what to do instead. (Formerly named list_traps.)
Esquema de entrada 
{'type': 'object', 'properties': {'query': {'type': 'string', 'description': "Optional filter, e.g. 'price', 'delivery'"}}}
look_up_seller
Everything known about one seller
USE WHEN you have a specific seller host and want its full track record. Returns every grade earned by actually paying it, what was quoted versus charged, whether goods arrived, its settlement volume, and its Organic Demand Score with the demand-shape read (is the volume real independent demand, or one wallet supplying almost all of it). The deep dossier on one seller; for a quick go/no-go before paying, use check_before_paying instead. (Formerly named get_service.)
Esquema de entrada 
{'type': 'object', 'required': ['host'], 'properties': {'host': {'type': 'string', 'description': 'Hostname, e.g. blockrun.ai or api.bitrefill.com'}}}
market_size
How big is the x402 market
USE WHEN asked how big x402 is, whether it is growing, or what settled recently. Returns both what actually settled on Base over the last day (from chain logs, per tracked seller) and the live market pulse (24h volume and payments with day-over-day change, a 7-day series, and stablecoin circulation). All measured from chain, not registry counters, which are not demand and can be bought. (Merges the former market_summary and market_pulse.)
Esquema de entrada 
{'type': 'object', 'properties': {}}
rank_by_accuracy
Who returns the most accurate value in a category
USE WHEN a category has an objective right answer (crypto-price, stock-price, fx-rate, gas-price, wallet-balance, weather) and you want the sellers we PAID ranked by how close their returned value was to a primary source that cannot be a reseller (exchange median, chain balanceOf, ECB rates, FMP quote). Top rows are the cheapest accurate sellers. Call with no category to list the available ones. (Formerly named most_accurate.)
Esquema de entrada 
{'type': 'object', 'properties': {'limit': {'type': 'integer', 'description': 'How many results (default 10, max 50)'}, 'category': {'type': 'string', 'description': 'One of: crypto-price, stock-price, fx-rate, gas-price, wallet-balance, weather. Omit to list categories.'}}}
rank_sellers
The leaderboard: biggest, or most real
USE WHEN you want a ranked list of sellers across the market. by='revenue' ranks by raw USDC received (who is busy); by='real_demand' ranks by Organic Demand Score (whose money comes from many independent wallets rather than one wallet supplying almost all of it). The two disagree often, and the disagreement is the point. For accuracy ranking within an objective category, use rank_by_accuracy. (Formerly named top_services.)
Esquema de entrada 
{'type': 'object', 'properties': {'by': {'enum': ['revenue', 'real_demand'], 'type': 'string', 'default': 'revenue'}, 'limit': {'type': 'integer', 'default': 10, 'maximum': 50, 'minimum': 1}}}
Historial

Cambios recientes en herramientas

Añadido
known_payment_traps
17 de September de 2026 a las 12:38
Añadido
market_size
17 de September de 2026 a las 12:38
Añadido
rank_by_accuracy
17 de September de 2026 a las 12:38
Añadido
rank_sellers
17 de September de 2026 a las 12:38
Añadido
look_up_seller
17 de September de 2026 a las 12:38
Añadido
check_before_paying
17 de September de 2026 a las 12:38
Añadido
find_api
17 de September de 2026 a las 12:38
Descubrir

Servidores MCP similares

Tenjin

blog.tenjin/tenjin

Searches, reads, and publishes paid essays and synthesized answers, with USDC payments handled through x402.

SCRIPTMASTERLABS — SqueezeOS MCP

com.scriptmasterlabs/squeezeos

Discovers and routes machine capabilities, provides web access and search verification, and supports caller-authorized x402 payme…

x402 Market Intelligence + Russian Web Access

com.ruscrape/russia-access

Fetches websites through country-specific or residential IPs, provides Russian web access and proxies, runs sandboxed code, and o…

Anyway Possible Paid Agent Utilities

io.github.anyway-possible/agent-utilities

Provides Base wallet and payment-readiness checks, merchant intelligence, public URL verification, and verifiable web evidence th…

x402-list-mcp

com.x402-list/x402-list-mcp

Searches and evaluates x402 payment APIs using service health, uptime, pricing, compliance, change events, and on-chain settlemen…

Agent Deals

io.github.gmahar82-stack/agent-deals

Checks and compares x402 services, finds lower-cost working APIs, and reads public webpages or PDFs as Markdown.

ghost-x402-market-intel-vet-schema

dev.workers.ghost-agent-os.ghost-identity/ghost-x402-market-intel-vet-schema

Evaluates and vets paid x402/API providers, applies pre-spend decisions, checks schema freshness, and performs failover web searc…

nohumans.directory

directory.nohumans/registry

Discovers and evaluates paid x402 APIs and datasets, including pricing, schemas, payment chains, reputation, and verified deliver…