_ registry / mcp http-sse · checked 11h ago

veriphone

https://mcp.veriphone.io

Registry code: 031e5384fc19e0fa

api record

Veriphone validates phone numbers and returns carrier and line-type data for 243 countries. verify_phone costs 1 credit per call in static mode and 10 in current mode, charged only when the API answers "success". Prefer international format (+14169670000); otherwise pass default_country. A valid number is one a carrier can assign — it does not mean the handset is switched on or reachable. Pricing and docs: https://veriphone.io/llms.txt

endpoint
https://mcp.veriphone.io
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is veriphone live?
Yes — it answered the hub's last check (checked 11h ago). It answered 100% of checks over the last 30 days.
Is veriphone free to use?
Not measured yet.
What tools does veriphone have?
5 tools: verify_phones, verify_phone, example_number, get_credits, current_coverage.
Is veriphone safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
78ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 2 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 5 tools
5 never probed 0 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • verify_phones unknown never probed

    Validate up to 50 phone numbers in one call (same fields as verify_phone, one result per input, in order). Costs 1 credit per number (10 in current mode). For thousands of numbers use the CSV upload at https://veriphone.io/clean-phone-list instead.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "phones"
      ],
      "properties": {
        "mode": {
          "enum": [
            "static",
            "current"
          ],
          "type": "string",
          "description": "\"static\" (default, 1 credit): validity, line type, carrier of the number's original range, country, formatting. \"current\" (10 credits, 1 if unresolved): everything in static plus the carrier currently serving the number, even after porting, with a ported flag."
        },
        "phones": {
          "type": "array",
          "items": {
            "type": "string",
            "minLength": 3
          },
          "maxItems": 50,
          "minItems": 1,
          "description": "Up to 50 numbers."
        },
        "default_country": {
          "type": "string",
          "maxLength": 2,
          "minLength": 2,
          "description": "Two-letter ISO country code, e.g. \"US\" or \"GB\". Used when a number has no international prefix."
        }
      }
    }
    arguments 33 lines
  • verify_phone unknown never probed

    Validate one phone number and return its line type (mobile, fixed_line, voip, toll_free…), carrier, country, region, and formats (E.164, international, local). Costs 1 credit (static) or 10 credits (mode "current" — also resolves the carrier currently serving the number, incl. ported numbers). Invalid numbers are a charged, definitive answer with a reason. Not a check of whether the phone is switched on.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "phone"
      ],
      "properties": {
        "mode": {
          "enum": [
            "static",
            "current"
          ],
          "type": "string",
          "description": "\"static\" (default, 1 credit): validity, line type, carrier of the number's original range, country, formatting. \"current\" (10 credits, 1 if unresolved): everything in static plus the carrier currently serving the number, even after porting, with a ported flag."
        },
        "phone": {
          "type": "string",
          "minLength": 3,
          "description": "The number to check, ideally in international format, e.g. \"+14169670000\"."
        },
        "default_country": {
          "type": "string",
          "maxLength": 2,
          "minLength": 2,
          "description": "Two-letter ISO country code, e.g. \"US\" or \"GB\". Used when a number has no international prefix."
        }
      }
    }
    arguments 28 lines
  • example_number unknown never probed

    A syntactically valid example phone number for a country and line type (MOBILE, FIXED_LINE, TOLL_FREE, VOIP…), useful for testing formats. Free to call.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "type": {
          "type": "string",
          "description": "MOBILE (default), FIXED_LINE, TOLL_FREE, VOIP, PREMIUM_RATE…"
        },
        "country": {
          "type": "string",
          "maxLength": 2,
          "minLength": 2,
          "description": "Two-letter ISO country code, e.g. \"US\" or \"GB\". Used when a number has no international prefix."
        }
      }
    }
    arguments 16 lines
  • get_credits unknown never probed

    The account's plan, monthly limit, credits used this period, pay-as-you-go balance, and usage split by static/current mode. Free to call.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • current_coverage unknown never probed

    Which countries support mode "current" (the carrier currently serving a number, after porting). Pass a country to get yes/no, or nothing for the full list. Free to call, no key needed.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "country": {
          "type": "string",
          "maxLength": 2,
          "minLength": 2,
          "description": "Two-letter ISO country code, e.g. \"US\" or \"GB\". Used when a number has no international prefix."
        }
      }
    }
    arguments 12 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 031e5384fc19e0fa.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/031e5384fc19e0fa/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/031e5384fc19e0fa/badge.svg)](https://brick.blue/agent/031e5384fc19e0fa?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.