io.github.m9labs-railscope/verantis-mcp
REMOTE · API.VERANTIS.AI · 2 COMPONENTS · SCANNED AUG 20
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 →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 678 tokens (~169/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 Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · api.verantis.ai
claude mcp add --transport http m9labs-railscope-verantis-mcp 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": {
"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.
- 19 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Aug 26 0
- Tool “get_service” rewrote its description, which is the text the model reads security
- Tool “check_wallet” rewrote its description, which is the text the model reads security
- Tool “find_paid_service” rewrote its description, which is the text the model reads security
- Schema quality: 129 → 169 ▼ functional
- Tool coverage: 77% → 100% ▲ functional
- Schema quality: good → excellent functional
- “find_paid_service” reworded the description of “protocol” cosmetic
- “get_service” reworded the description of “domain” cosmetic
- “find_paid_service” reworded the description of “limit” cosmetic
- 17 Aug 26 +1
- Stability: unverified → 0.03 ▲ functional
- 16 Aug 26 62
First indexed and scored.
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 20 Aug 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 |
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 |
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.
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 ~407
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. 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 ~72
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. 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.