Connection check
verified live · 27h ago
verantis-mcp
Verified directory for machine payments (x402 & MPP): check services and wallets before agents pay.
Tools
4
GitHub stars
4
Installs / wk
—
Licence
MIT
Transport
streamable-http, stdio
Last checked
27h ago
Tools & capabilities
4 toolsRead from the running server on 27h ago.
check_wallet
read-only
pay_to*
Check a recipient wallet BEFORE your agent pays it — a pre-payment guard. Pass the pay-to address a service asked you to pay; returns whether Verantis knows the wallet, its EARNED… Check a recipient wallet BEFORE your agent pays it — a pre-payment guard. Pass the pay-to address a service asked you to pay; returns whether Verantis knows the wallet, its EARNED reputation tier, and human-readable reasons. A wallet IS a settlement rail, so the reply names the rail it settles on ('rail': chain + protocols), its host, on-chain buyer retention (distinct buyers, repeat rate, distribution), and the host's OTHER rails ('also_settles_on'). If 'shared_wallet' is true the address fronts many services (a relay/treasury) so the reputation reflects the pool, not one service — treat with care. An unknown or low-reputation recipient is a reason to pause.
directory_stats
read-only
Index-level statistics: services, verification breakdown, data freshness. Index-level statistics: services, verification breakdown, data freshness.
find_paid_service
read-only
chainlimitquery*protocolmin_scoreproven_only
+5
Search Verantis's verified directory of machine-payable services (x402, MPP). Results are UNIFIED per service (host): each carries its settlement rails ('rails': base / solana / te… Search Verantis's verified directory of machine-payable services (x402, MPP). Results are UNIFIED per service (host): each carries its settlement rails ('rails': base / solana / tempo), and every rail has its OWN reputation, price, and buyer retention — never blended. Pass 'chain' and 'matched_rail' marks that chain's rail so you see the reputation for the rail you'll actually pay on. 'coming_soon' lists advertised chains not yet measured. Each rail's 'wallet_scope' says if its pay-to wallet is 'dedicated' (the buyers/payments/volume are this service's own) or 'shared' (a relay/treasury fronting 'wallet_services' services, so those figures are the pool's inbound, not this service alone). Prefer verified=true before paying anyone.
get_service
read-only
domain*