io.github.m9labs-railscope/verantis-mcp

Est-ce que io.github.m9labs-railscope/verantis-mcp est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.m9labs-railscope/verantis-mcp » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 4 outils

• check_wallet≈ 249 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • pay_to · string · requis
    recipient wallet address (0x… for Base/EVM, base58 for Solana)

  Exemple d'appel

  {"name": "check_wallet", "arguments": {"pay_to": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• directory_stats≈ 67 tokens

  Index-level statistics: services, verification breakdown, data freshness.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "directory_stats", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• find_paid_service≈ 648 tokens

  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.

  Paramètres, retour & exemple (11)

  Paramètres

  • chain · string · optionnel
    settlement network, e.g. base, solana, polygon, tempo
  • limit · integer · optionnel
    maximum number of results to return (default 10)
  • query · string · requis
    what you need, e.g. 'twitter data', 'web search', 'rpc ethereum'
  • protocol · string · optionnel · x402 | mpp
    restrict to one payment protocol: x402 or mpp
  • min_score · integer · optionnel
    minimum trust score 0-100 — set high (e.g. 85) for money-moving tasks
  • proven_only · boolean · optionnel
    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 · number · optionnel
    max price per call in USD
  • require_fresh · boolean · optionnel
    live re-probe stale results before returning — use before paying real money; adds ~1s per stale service
  • verified_only · boolean · optionnel
    only services that passed the latest live probe
  • max_latency_ms · integer · optionnel
    reject services slower than this (ms)
  • exclude_concentrated · boolean · optionnel
    exclude services from operators with many listings under one registrable owner (a neutral concentration signal, not a fraud claim)

  Exemple d'appel

  {"name": "find_paid_service", "arguments": {"query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_service≈ 173 tokens

  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).

  Paramètres, retour & exemple (1)

  Paramètres

  • domain · string · requis
    the service host / domain to look up, e.g. api.nansen.ai

  Exemple d'appel

  {"name": "get_service", "arguments": {"domain": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://api.verantis.ai/mcp