io.github.m9labs-railscope/verantis-mcp
PYPI · VERANTIS-MCP · 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 from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to m9labs-railscope/verantis-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 49 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
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 Management93
- Stability observed for 28 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
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 runs locally as a PyPI package, launched with uvx verantis-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · verantis-mcp
claude mcp add m9labs-railscope-verantis-mcp -- uvx verantis-mcp
{
"mcpServers": {
"m9labs-railscope-verantis-mcp": {
"command": "uvx",
"args": [
"verantis-mcp"
]
}
}
} {
"servers": {
"m9labs-railscope-verantis-mcp": {
"command": "uvx",
"args": [
"verantis-mcp"
]
}
}
} codex mcp add m9labs-railscope-verantis-mcp -- uvx verantis-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"m9labs-railscope-verantis-mcp": {
"type": "local",
"command": [
"uvx",
"verantis-mcp"
],
"enabled": true
}
}
} openclaw mcp add m9labs-railscope-verantis-mcp --command uvx --arg verantis-mcp
mcp_servers:
m9labs-railscope-verantis-mcp:
command: "uvx"
args: ["verantis-mcp"] {
"McpServers": {
"m9labs-railscope-verantis-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"verantis-mcp"
]
}
}
} assistant mcp add m9labs-railscope-verantis-mcp -t stdio -c uvx -a verantis-mcp
{
"mcpServers": {
"m9labs-railscope-verantis-mcp": {
"command": "uvx",
"args": [
"verantis-mcp"
]
}
}
} 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.
- 4 Oct 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.
- 2 Oct 26 −2
- Stability: pass → 0.80 functional
- 1 Oct 26 0
- Stability: 0.97 → pass security
- 30 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 +26
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- 25 Sept 26 +15
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 0
- Stability: 0.97 → pass security
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 · Analysed pypi/verantis-mcp@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | m9labs-railscope/verantis-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/m9labs-railscope/verantis-mcp/.github/workflows/publish.yml@refs/tags/v0.2.1 |
| Rekor log index | 2500385866 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:fe13694314bf9da33589cf1ff7826379c3932ba0a001ababef807b5627525535 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 ~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.
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 PyPI package (verantis-mcp).
Is the io.github.m9labs-railscope/verantis-mcp server safe to use?
io.github.m9labs-railscope/verantis-mcp scores 93 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 6 October 2026. Its build provenance is signed and verified. 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 678 tokens of context every time the server is loaded.
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.
What licence is the io.github.m9labs-railscope/verantis-mcp server under?
io.github.m9labs-railscope/verantis-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.