Verantis Mcp

io.github.m9labs-railscopePublished by GitHub account m9labs-railscopev0.2.1Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableFinanceSecurity & Monitoring

Overview

AI-generated overview

A read-only directory of machine-payable services (x402 and MPP) that lets an assistant check a service or recipient wallet before an agent pays it.

What you can do
Search the verified directory of machine-payable services, filtered by protocol, chain, price, category or reputation, with results split per settlement rail (base, solana, tempo). Retrieve the full record for one service host, including each rail's reputation, price, buyers, volume and history. Check a recipient wallet before payment to see whether it is known, its earned reputation tier and which services it fronts. Read index-level statistics on services, verification breakdown and data freshness.
When to use it
Use it when an agent is about to pay a machine-payable service over x402 or MPP and you want a pre-payment check of the service or the pay-to wallet. It is informational only and does not move money.
Requirements
Either the hosted streamable-HTTP endpoint or a local process run with uvx or pip (Python). No account or API key. The optional VERANTIS_API_BASE environment variable overrides the API base URL.
Before you install
Reputation and classifications reflect live probes and on-chain reads at a point in time and can change; the data is informational and not financial advice. The local package writes a random anonymous install id. It cannot move money or see keys, but payment decisions remain the agent's responsibility.

Installation

In SourceWeft

  1. Open Verantis Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.m9labs-railscope%2Fverantis-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "verantis": {
      "type": "http",
      "url": "https://api.verantis.ai/mcp"
    }
  }
}

README

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

ToolWhat it does
find_paid_serviceSearch the verified directory (x402 / MPP). Filter by verified-only, price, chain, protocol, category, reputation.
get_serviceFull record + verification provenance for one domain.
check_walletPre-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_statsIndex-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:

json
{  "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:

json
{  "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 varDefaultPurpose
VERANTIS_API_BASEhttps://api.verantis.aiPoint 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.

Source: README.md at commit ddc10d9

Tools

4

find_paid_service

Find a 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.

Parameterschainlimitqueryrequiredprotocolmin_scoreproven_onlymax_price_usdrequire_freshverified_onlymax_latency_msexclude_concentrated

get_service

Get a service record

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

Parametersdomainrequired

directory_stats

Directory statistics

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

Takes no parameters.

check_wallet

Check a recipient 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.

Parameterspay_torequired

Version history

1
  1. v0.2.1LatestSep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts