Server definition

Hash: sha256:7d761a866485694df5f0ff168b3b230dad8a9f4e4f66213b7c11f082ae056d4a
What it is: What a remote MCP server returned when asked what it offers: 4 tools

The blob, as servednamed by its sha256

{
  "instructions": null,
  "tools": [
    {
      "description": "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.",
      "inputSchema": {
        "properties": {
          "pay_to": {
            "description": "recipient wallet address (0x… for Base/EVM, base58 for Solana)",
            "type": "string"
          }
        },
        "required": [
          "pay_to"
        ],
        "type": "object"
      },
      "name": "check_wallet",
      "outputSchema": null
    },
    {
      "description": "Index-level statistics: services, verification breakdown, data freshness.",
      "inputSchema": {
        "properties": {},
        "type": "object"
      },
      "name": "directory_stats",
      "outputSchema": null
    },
    {
      "description": "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.",
      "inputSchema": {
        "properties": {
          "chain": {
            "description": "settlement network, e.g. base, solana, polygon, tempo",
            "type": "string"
          },
          "exclude_concentrated": {
            "default": false,
            "description": "exclude services from operators with many listings under one registrable owner (a neutral concentration signal, not a fraud claim)",
            "type": "boolean"
          },
          "limit": {
            "default": 10,
            "description": "maximum number of results to return (default 10)",
            "type": "integer"
          },
          "max_latency_ms": {
            "description": "reject services slower than this (ms)",
            "type": "integer"
          },
          "max_price_usd": {
            "description": "max price per call in USD",
            "type": "number"
          },
          "min_score": {
            "description": "minimum trust score 0-100 — set high (e.g. 85) for money-moving tasks",
            "type": "integer"
          },
          "protocol": {
            "description": "restrict to one payment protocol: x402 or mpp",
            "enum": [
              "x402",
              "mpp"
            ],
            "type": "string"
          },
          "proven_only": {
            "default": false,
            "description": "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.",
            "type": "boolean"
          },
          "query": {
            "description": "what you need, e.g. 'twitter data', 'web search', 'rpc ethereum'",
            "type": "string"
          },
          "require_fresh": {
            "default": false,
            "description": "live re-probe stale results before returning — use before paying real money; adds ~1s per stale service",
            "type": "boolean"
          },
          "verified_only": {
            "default": true,
            "description": "only services that passed the latest live probe",
            "type": "boolean"
          }
        },
        "required": [
          "query"
        ],
        "type": "object"
      },
      "name": "find_paid_service",
      "outputSchema": null
    },
    {
      "description": "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).",
      "inputSchema": {
        "properties": {
          "domain": {
            "description": "the service host / domain to look up, e.g. api.nansen.ai",
            "type": "string"
          }
        },
        "required": [
          "domain"
        ],
        "type": "object"
      },
      "name": "get_service",
      "outputSchema": null
    }
  ]
}

Verify it yourself

curl -s https://api.teppi.xyz/v1/evidence/sha256:7d761a866485694df5f0ff168b3b230dad8a9f4e4f66213b7c11f082ae056d4a | sha256sum