Verantis MCP Server

by m9labs-railscope Your server? Claim it

answering

Verantis MCP is answering right now. Last checked 14 min ago. 130 installs a week from pypi. It exposes 4 tools. Last commit 31 Aug 2026.

Verified directory for machine payments (x402 & MPP): check services and wallets before agents pay.

Installs per day peak 39 · avg 18 · -8% w/w

a month agotoday

Uptime history 61 days of history · worst day 93%

61 days agonow

98.9%

Uptime 24h

90 of 91 checks

Tools

read from the server

324 ms

Response time

average over 24h

130

Installs / week

npm and PyPI

What changed 7

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 18 August 2026. No other catalogue keeps this.

31 Aug 2 tool descriptions were rewritten find_paid_service, get_service

18 Aug 3 tool descriptions were rewritten check_wallet, find_paid_service, get_service

18 Aug 2 tools changed the parameters they ask for find_paid_service, get_service

Verantis MCP does not always answer

Over the last week it answered 99.2% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add verantis-mcp --transport http https://api.verantis.ai/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "verantis-mcp": {
      "url": "https://api.verantis.ai/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.verantis-mcp]
url = "https://api.verantis.ai/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "verantis-mcp": {
      "url": "https://api.verantis.ai/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "verantis-mcp": {
      "url": "https://api.verantis.ai/mcp"
    }
  }
}

This one needs environment variables set before it will start: VERANTIS_API_BASE (Override the Verantis API base URL (defaults to https://api.verantis.ai).). The author declared them in the registry entry; get the values from the project itself.

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

directory

directory_stats

Index-level statistics: services, verification breakdown, data freshness.

paid

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' 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.

service

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 this one alone) vs 'dedicated' (this service's own). Pass the host (domain).

wallet

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 ('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.

Endpoints

URL	Transport	State	Latency	Checked
https://api.verantis.ai/mcp	streamable-http	answering	485 ms	14 min ago

Alternatives to Verantis MCP

same job, measured the same way

Xpay

by xona-labs

Xona Wallet: agent wallet for AI agents. x402 payments, AgenC hires, 20k+ services

160 installs/wk local only

Agentpay

by up2itnow0822

Non-custodial x402 payment MCP server for AI agents. Wallets and payments on 17 chains.

731 installs/wk local only

Clawpay

by up2itnow0822

Non-custodial x402 payment MCP server for AI agents. Wallets, payments, and commerce on 17 chains.

local only

Agent Wormhole

by runningoffcode

Check tokens, pages and x402 payments before your agent trusts them. Offline verdicts.

697 installs/wk local only

Amrood — INR Payments for AI Agents

by saurabh-karn

KYC-verified INR wallets for AI agents in India. Payments, escrow, and settlements.

163 installs/wk local only

AgentIndex

by cognivis

Trust scores and on-chain payment receipts for x402 services.

4 tools answering

HPP x402 MCP Bridge

by hpp-io

MCP bridge for autonomous x402 payments in HPP USDC.e — discover and pay for services per call.

170 installs/wk local only

Azeth Protocol

by azeth-protocol

Smart accounts, x402 payments, on-chain reputation, and service discovery for AI agents

68 installs/wk local only

Verantis MCP — questions

Answers built from our own checks of this server.

What can Verantis MCP do?

It exposes 4 tools, read directly from the server on our last check. Among them: check_wallet, directory_stats, find_paid_service, get_service. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Verantis MCP working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 90 of 91 checks got a reply (98.9%), average response time 324 ms. The bar chart above shows every period we have measured.

How do I connect Verantis MCP?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Verantis MCP need an API key?

No. Verantis MCP completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Verantis MCP?

It answers our handshake in 324 ms on average, which is faster than 41% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

How many people use Verantis MCP?

The pypi package verantis-mcp was installed 130 times in the last week. Week over week that is -8%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.

Is Verantis MCP open source?

Yes — it is published under the MIT licence, written in Python, 4 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.