io.github.m9labs-railscope/verantis-mcp
REMOTE · API.VERANTIS.AI · 2 COMPONENTS · SCANNED OCT 6
Verified directory for machine payments (x402 & MPP): check services and wallets before agents pay.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 786 tokens (~196/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.m9labs-railscope/verantis-mcp server?
io.github.m9labs-railscope/verantis-mcp is a hosted endpoint at https://api.verantis.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.verantis.ai
claude mcp add --transport http m9labs-railscope-verantis-mcp 'https://api.verantis.ai/mcp'
{
"mcpServers": {
"m9labs-railscope-verantis-mcp": {
"url": "https://api.verantis.ai/mcp"
}
}
} {
"servers": {
"m9labs-railscope-verantis-mcp": {
"type": "http",
"url": "https://api.verantis.ai/mcp"
}
}
} [mcp_servers.m9labs-railscope-verantis-mcp] url = "https://api.verantis.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"m9labs-railscope-verantis-mcp": {
"type": "remote",
"url": "https://api.verantis.ai/mcp",
"enabled": true
}
}
} openclaw mcp add m9labs-railscope-verantis-mcp --url 'https://api.verantis.ai/mcp' --transport streamable-http
mcp_servers:
m9labs-railscope-verantis-mcp:
url: "https://api.verantis.ai/mcp" {
"McpServers": {
"m9labs-railscope-verantis-mcp": {
"Transport": "http",
"Url": "https://api.verantis.ai/mcp"
}
}
} assistant mcp add m9labs-railscope-verantis-mcp -t streamable-http -u 'https://api.verantis.ai/mcp'
{
"mcpServers": {
"m9labs-railscope-verantis-mcp": {
"type": "http",
"url": "https://api.verantis.ai/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 +7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Sept 26 0
- Tool “find_paid_service” rewrote its description, which is the text the model reads security
- Tool “get_service” rewrote its description, which is the text the model reads security
- Schema quality: 169 → 196 ▼ functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 6 Oct 2026 · Probed https://api.verantis.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.verantis.ai | CN=WE1,O=Google Trust Services,C=US | 12 Aug 2026 | 10 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 598976dae695d3940e07886fe62fe6ac |
| SANs: api.verantis.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.verantis.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| verantis.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.verantis.ai/mcp | Verified | 200 | |
| http (plaintext) | http://api.verantis.ai/mcp | HTTPS enforced | 301 | https://api.verantis.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_wallet ~179
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.
| Name | Type | Req | Description |
|---|---|---|---|
| pay_to | string | yes | recipient wallet address (0x… for Base/EVM, base58 for Solana) |
No output schema declared.
No examples provided.
directory_stats ~20
Index-level statistics: services, verification breakdown, data freshness.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
find_paid_service ~470
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.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | settlement network, e.g. base, solana, polygon, tempo |
| exclude_concentrated | boolean | – | exclude services from operators with many listings under one registrable owner (a neutral concentration signal, not a fraud claim) |
| limit | integer | – | maximum number of results to return (default 10) |
| max_latency_ms | integer | – | reject services slower than this (ms) |
| max_price_usd | number | – | max price per call in USD |
| min_score | integer | – | minimum trust score 0-100 — set high (e.g. 85) for money-moving tasks |
| protocol | string | – | restrict to one payment protocol: x402 or mpp |
| proven_only | boolean | – | 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 con… |
| query | string | yes | what you need, e.g. 'twitter data', 'web search', 'rpc ethereum' |
| require_fresh | boolean | – | live re-probe stale results before returning — use before paying real money; adds ~1s per stale service |
| verified_only | boolean | – | only services that passed the latest live probe |
No output schema declared.
No examples provided.
get_service ~117
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).
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | the service host / domain to look up, e.g. api.nansen.ai |
No output schema declared.
No examples provided.
What is the io.github.m9labs-railscope/verantis-mcp server?
io.github.m9labs-railscope/verantis-mcp is listed in the public MCP registry as io.github.m9labs-railscope/verantis-mcp. Verified directory for machine payments (x402 & MPP): check services and wallets before agents pay. This page covers its hosted endpoint (https://api.verantis.ai/mcp).
Is the io.github.m9labs-railscope/verantis-mcp server safe to use?
io.github.m9labs-railscope/verantis-mcp scores 85 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.m9labs-railscope/verantis-mcp server expose?
io.github.m9labs-railscope/verantis-mcp exposes 4 tools: find_paid_service, get_service, directory_stats, check_wallet. Their descriptions and schemas cost roughly 786 tokens of context every time the server is loaded.
Does the io.github.m9labs-railscope/verantis-mcp server require authentication?
No. We connected to io.github.m9labs-railscope/verantis-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.m9labs-railscope/verantis-mcp server still maintained?
io.github.m9labs-railscope/verantis-mcp is still listed as active in the MCP registry. We last reached this channel on 6 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.