Skip to main content

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

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

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.

Release files for verantis-mcp 0.1.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for verantis-mcp 0.1.2
File Size Uploaded
verantis_mcp-0.1.2.tar.gz 8.3 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for verantis-mcp 0.1.2
File Interpreter ABI Platform
verantis_mcp-0.1.2-py3-none-any.whl Python 3 none any Details

Total release size: 15.6 kB

Release files / verantis_mcp-0.1.2.tar.gz

Download URL verantis_mcp-0.1.2.tar.gz
Size 8.3 kB
Tags Source
SHA-256 checksum
How to use checksums
f9e943e8f3bd57fa5eacf63078d010f3584c27ed3fab5fb7131a9f3294cb82a4
BLAKE2b-256 checksum
How to use checksums
7724c9a669551ffc8b3b7f8aa1e582a7a36bac13e40c981cd90792b56cf865a1
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 16, 2026.

Transparency log

Release files / verantis_mcp-0.1.2-py3-none-any.whl

Download URL verantis_mcp-0.1.2-py3-none-any.whl
Size 7.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
3109abed281cd85cafafeb93de633fa1a90222511a2eced33eda6315134bcfe7
BLAKE2b-256 checksum
How to use checksums
bdecceb3b4beb8e04869be6646b18fd4473128f61b114a58ef9a004988901453
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 16, 2026.

Transparency log

Release history Release notifications | RSS feed

0.2.1

2 release files

0.2.0

2 release files

0.1.3

2 release files

This release

0.1.2 This release

2 release files

0.1.1

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page