Verantis MCP
The verified directory for machine payments — as an MCP tool.
[Install in VS Code]
[PyPI]
[MCP Registry]
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
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:
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:
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
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.