_ registry / mcp streamable-http

phonecheck

https://phonecheck.mike-tusa.workers.dev

Registry code: e0acb37507f00e97

api record

PhoneCheck validates and formats phone numbers offline against libphonenumber numbering-plan metadata: E.164, international, national and RFC 3966 formats, region, calling code and the line type from the original allocation. "Valid" means the number matches an allocated range; it does not mean the line is connected, reachable or owned by anyone. No carrier, HLR, porting or live-line lookup is made. Numbers are processed in memory and not stored or logged. Anonymous use is limited to about 20 calls per minute per IP; send "Authorization: Bearer <key>" or "X-Api-Key: <key>" with a free pc_live_…

endpoint
https://phonecheck.mike-tusa.workers.dev/mcp
protocol
streamable-http ·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 phonecheck live?
Not measured yet: the hub has not completed a check of this server.
Is phonecheck free to use?
Not measured yet.
What tools does phonecheck have?
2 tools: get_example_number, parse_phone_number.
Is phonecheck 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
unknown
uptime
—
latency
—

last good check

priced tools
0

of 2 tools

_ 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 2 tools
2 never probed 0 of 2 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.

  • get_example_number unknown never probed

    Return the libphonenumber example (mobile) number for a region, in all formats, for format testing only (do not dial). Read-only. Same data and limits as GET /v1/example/{country}.

    mcp-tool

    {
  "type": "object",
  "required": [
    "country"
  ],
  "properties": {
    "country": {
      "type": "string",
      "pattern": "^[A-Za-z]{2}$",
      "maxLength": 2,
      "minLength": 2,
      "description": "ISO 3166-1 alpha-2 region code, e.g. US, GB, DE."
    }
  },
  "additionalProperties": false
}
    arguments 16 lines
  • parse_phone_number unknown never probed

    Validate one phone number offline against libphonenumber metadata and return E.164, international, national and RFC 3966 formats, region, calling code and line type (from the original allocation). Valid means the number fits an allocated range, not that the line is connected or reachable; no carrier/HLR lookup. Read-only. Same engine, keys and limits as POST /v1/parse.

    mcp-tool

    {
  "type": "object",
  "required": [
    "number"
  ],
  "properties": {
    "number": {
      "type": "string",
      "maxLength": 64,
      "minLength": 1,
      "description": "The phone number, e.g. \"+44 20 7946 0018\" or \"(213) 373-4253\". Max 64 characters."
    },
    "default_country": {
      "type": "string",
      "pattern": "^[A-Za-z]{2}$",
      "maxLength": 2,
      "minLength": 2,
      "description": "Optional ISO 3166-1 alpha-2 region used when the number has no +country code, e.g. US, GB."
    }
  },
  "additionalProperties": false
}
    arguments 22 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 e0acb37507f00e97.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/e0acb37507f00e97/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/e0acb37507f00e97/badge.svg)](https://brick.blue/agent/e0acb37507f00e97?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
60%

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.