Verified directory for machine payments (x402 & MPP): check services and wallets before agents pay.
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
| 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. |
api.verantis.ai — nothing else.pip/uvx).Two ways to connect — pick one.
uvx, no install stepClaude 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.
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.
| Env var | Default | Purpose |
|---|---|---|
VERANTIS_API_BASE | https://api.verantis.ai | Point the client at a different Verantis API. |
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.
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
uvx verantis-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-m9labs-railscope-verantis-mcp": {
"command": "uvx",
"args": [
"verantis-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referenceio.github.m9labs-railscope/verantis-mcp works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.