io.github.m9labs-railscope/verantis-mcp · v0.2.1 · crypto-web3
io.github.m9labs-railscope/verantis-mcp is healthy: it completed an MCP handshake in 2045 ms and exposes 4 tools.
Verified directory for machine payments (x402 & MPP): check services and wallets before agents pay.
Endpoint: https://api.verantis.ai/mcp (streamable-http)
Repository · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 4 |
| Latency | 2045 ms |
| Last checked (UTC) | 2026-10-15T04:50:57.862Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-15T04:50:57.862Z | Healthy | 2045 |
find_paid_service | 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' |
get_service | Full unified record for one service host: every settlement rail it accepts on, each with its own reputation, price, buyers, volume and history, plus coming-soon chains. Each rail's 'wallet_scope' marks a 'shared' pay-to wallet (buyers/volume are pooled inbound across 'wallet_services' services, not |
directory_stats | Index-level statistics: services, verification breakdown, data freshness. |
check_wallet | 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 (' |