Finance · Remote MCP server

Verantis MCP

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

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
io.github.m9labs-railscope/verantis-mcp
Version
0.2.1
Status
Active
Category
finance
Transport
Streamable HTTP, stdio (local process)
Package
PyPI
Published
2026-08-18
Updated
2026-08-18
Publisher
m9labs-railscope (GitHub)
Repository
github.com/m9labs-railscope/verantis-mcp
Source
Registry API entry

Remote endpoints

TransportURLHeaders declared
Streamable HTTPhttps://api.verantis.ai/mcpNone

Packages

RegistryPackageVersionTransportEnvironment variables
PyPIruntime: uvxverantis-mcp0.2.1stdioVERANTIS_API_BASE

How to connect Verantis MCP

Verantis MCP is a remote MCP server: there is nothing to install. Its endpoint is https://api.verantis.ai/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.

No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.

It can also run locally from a Python package published to PyPI: verantis-mcp version 0.2.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install — the usual command is uvx verantis-mcp. It reads the environment variable VERANTIS_API_BASE; set it in the client's configuration for this server.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "verantis-mcp": {
      "command": "uvx",
      "args": [
        "verantis-mcp"
      ],
      "env": {
        "VERANTIS_API_BASE": "<value>"
      }
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More finance servers

All 3,583 →
ServerRunsEndpoint or package
VedettaX402 pay-per-call crypto sentiment, divergence & analyst reads. USDC on Base. NFA.Local · stdionpm: vedetta-mcp
Veeam AIopsGoverned Veeam Backup & Replication ops — 27 MCP tools with audit, budget, undo guards.Local · stdioPyPI: veeam-aiops
Vend Api MerchantPay-per-call web intel: extract, search, link check, domain, geo, Nano. Settled via Nano x402.Remote · HTTPextract.paypercall.dev
VeraDataVerified LATAM data for AI agents: sanctions, entity, rates, KYB. Pay via x402.Remote · HTTPapi.veradata.dev
Verdict: the due-diligence house for DeFiVerdict, the due-diligence house for DeFi: keyless ratings, methodology and a hack incident feed.Local · stdionpm: verdict-finance-mcp
VerdictSwarm MCPRead-only pre-trade token risk verdicts and size-aware Solana exit screening for agents.Local · stdioPyPI: verdictswarm-mcp
Verdix address riskCheck an EVM address on Base before sending funds: safe/caution/danger. Pays per call via x402.Local · stdionpm: verdix-mcp
VerdocDeterministic AGENTS.md and repo analysis for coding agents, paid per call in USDC over x402.Local · stdioMCP Bundle (.mcpb): verdochello/verdoc-mcp/releases/download/v0.1.0/