About verantis-mcp
verantis-mcp lets MCP-capable agents inspect machine-payment services and recipient wallets before payment. It reads Verantis's public directory of x402 and MPP services, including verification provenance and reputation information.
Key features
- 01Search the x402 and MPP directory
- 02Filter services by price, chain, and reputation
- 03Retrieve service records and verification provenance
- 04Check wallet reputation and buyer retention
Use cases
- 01Find verified machine-payment services
- 02Review a service before an agent pays
- 03Check a payment recipient wallet
MCP support
Exposes read-only directory search, service lookup, wallet checks, and directory statistics as MCP tools. It can be used locally over stdio or through the hosted Streamable HTTP endpoint.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://api.verantis.ai/mcpclaude mcp add --transport http m9labs-railscope-verantis https://api.verantis.ai/mcp{"mcpServers":{"m9labs-railscope-verantis":{"type":"http","url":"https://api.verantis.ai/mcp"}}}Open in Cursor{"servers":{"m9labs-railscope-verantis":{"type":"http","url":"https://api.verantis.ai/mcp"}}}Open in VS Code{"mcpServers":{"m9labs-railscope-verantis":{"type":"http","url":"https://api.verantis.ai/mcp"}}}{"mcpServers":{"m9labs-railscope-verantis":{"serverUrl":"https://api.verantis.ai/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
4| Parameter | Type | Required | Description |
|---|---|---|---|
| chain | string | No | settlement network, e.g. base, solana, polygon, tempo |
| limit | integer | No | maximum number of results to return (default 10) |
| query | string | Yes | what you need, e.g. 'twitter data', 'web search', 'rpc ethereum' |
| protocol | enum | No | restrict to one payment protocol: x402 or mppx402 | mpp |
| min_score | integer | No | minimum trust score 0-100 — set high (e.g. 85) for money-moving tasks |
| proven_only | boolean | No | only services that have EARNED reputation over time (excludes 'new' services and 'watch' services whose on-chain payments are concentrated / not yet broadly distributed). Reputation is earned via consistent history + on-chain buyer retention; a brand-new well-behaved service is verified but new, not top-trust. |
| max_price_usd | number | No | max price per call in USD |
| require_fresh | boolean | No | live re-probe stale results before returning — use before paying real money; adds ~1s per stale service |
| verified_only | boolean | No | only services that passed the latest live probe |
| max_latency_ms | integer | No | reject services slower than this (ms) |
| exclude_concentrated | boolean | No | exclude services from operators with many listings under one registrable owner (a neutral concentration signal, not a fraud claim) |
Details
From the project READMEVerantis MCP
The verified directory for machine payments — as an MCP tool.
Give any MCP-capable agent (Claude, Cursor, agent frameworks) the ability to check what it's about to pay before it pays. Verantis continuously probes machine-payable services across x402 and MPP, measures on-chain reputation, and publishes a recomputable record. This server is a thin client of the public Verantis API — standard library only, no dataset needed.
Learn more: verantis.ai · methodology: verantis.ai/methodology
Tools
| Tool | What it does |
|---|---|
find_paid_service | Search the verified directory (x402 / MPP). Filter by verified-only, price, chain, protocol, category, reputation. |
get_service | Full record + verification provenance for one domain. |
check_wallet | Pre-payment guard — pass the recipient wallet a service asked you to pay; get its earned reputation tier, on-chain buyer retention, and which services it fronts. |
directory_stats | Index-level stats: services, verification breakdown, freshness. |
What it can and can't do
- Can: read the public directory; check a service or wallet before your agent pays.
- Can't: move money, see your keys, or read your files.
- Only ever calls
api.verantis.ai— nothing else. - Writes nothing (hosted endpoint) / only a random anonymous install id (local
pip/uvx). - No account, no API key. MIT-licensed. Read-only.
- How we measure: verantis.ai/methodology
Install & connect
Two ways to connect — pick one.
Local (stdio) — via uvx, no install step
Claude Desktop (claude_desktop_config.json) or any MCP client:
{
"mcpServers": {
"verantis": {
"command": "uvx",
"args": ["verantis-mcp"]
}
}
}
Prefer pip? pip install verantis-mcp, then use "command": "verantis-mcp" with no args.
Cursor (~/.cursor/mcp.json): same block under mcpServers.
Hosted (no install) — connect by URL
VS Code / Copilot: one-click add ▸ — or add it manually below.
For any client that supports remote / streamable-HTTP MCP servers, point it straight at the hosted endpoint — nothing to install, no Python:
{
"mcpServers": {
"verantis": { "url": "https://api.verantis.ai/mcp" }
}
}
Clients that only speak local stdio can bridge with npx mcp-remote https://api.verantis.ai/mcp.
Restart your client, and the four tools appear.
Configuration
| Env var | Default | Purpose |
|---|---|---|
VERANTIS_API_BASE | https://api.verantis.ai | Point the client at a different Verantis API. |
Notes
Informational only; not financial, investment, or legal advice. Classifications describe what live probes and on-chain reads observed at a point in time and can change. Reputation is earned from real on-chain settlement, not assumed. Verantis has no rail of its own, no token, and no stake in any listed service.
MIT licensed.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.