A
license-
quality-
maintenanceEnables agents to search a verified directory of machine-payable services, inspect service and wallet reputation, and get pre-payment checks before spending.
MIT
verantis-mcp
Server Details
Verified directory for machine payments (x402 & MPP): check services and wallets before agents pay.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- m9labs-railscope/verantis-mcp
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
4 toolscheck_walletInspect
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, human-readable reasons, on-chain buyer retention (distinct buyers, repeat rate, distribution), and which services it fronts. An unknown or low-reputation recipient is a reason to pause.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| pay_to | Yes | recipient wallet address (0x… for Base/EVM, base58 for Solana) |
directory_statsInspect
Index-level statistics: services, verification breakdown, data freshness.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
find_paid_serviceInspect
Search Verantis's verified directory of machine-payable services (x402, MPP). Every result includes verification status from a live unpaid probe: whether the endpoint currently returns a valid 402 payment challenge, the live price from that challenge, and when it was last probed. Prefer verified=true results before paying anyone.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| chain | No | settlement network, e.g. base, solana, polygon, tempo | |
| limit | No | ||
| query | Yes | what you need, e.g. 'twitter data', 'web search', 'rpc ethereum' | |
| protocol | No | ||
| min_score | No | minimum trust score 0-100 — set high (e.g. 85) for money-moving tasks | |
| proven_only | No | only services that have EARNED reputation over time (excludes 'new' services and 'watch' services whose on-chain payments are concentrated / not yet broadly distributed). Reputation is earned via consistent history + on-chain buyer retention; a brand-new well-behaved service is verified but new, not top-trust. | |
| max_price_usd | No | max price per call in USD | |
| require_fresh | No | live re-probe stale results before returning — use before paying real money; adds ~1s per stale service | |
| verified_only | No | only services that passed the latest live probe | |
| max_latency_ms | No | reject services slower than this (ms) | |
| exclude_concentrated | No | exclude services from operators with many listings under one registrable owner (a neutral concentration signal, not a fraud claim) |
get_serviceInspect
Full Verantis record for one service domain, including verification provenance (probe time, classification, live vs listed price, pay-to).
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- Flicense-qualityAmaintenanceEnables agents to discover and verify paid agent services through x402 payment validation and release gate checks.
- AlicenseAqualityAmaintenanceBefore an AI agent pays an x402 endpoint, checks whether it's safe to pay: liveness, scam/anomaly scan (payTo hijack, bait-and-switch, honeypot), and on-chain receiver verification. ~70% of x402 endpoints are dead or scams.3MIT
- Alicense-qualityBmaintenanceMCP server for verifying agent payment integrity on x402, providing tools to check payTo mismatches, market stats, and lookup endpoints.1MIT