_ registry / mcp streamable-http · checked 19m ago

internationalcall-dialing

https://internationalcall.co

Registry code: 0d0a4ac2d9ecf11a

api record

InternationalCall.co tools for calling phones across borders. Use get_dialing_instructions whenever someone asks how to call a country or a specific number from somewhere: it applies each country's exit code, the destination's trunk-prefix rule (the UK drops its leading 0, Mexico and Italy drop nothing) and shared calling-code zones (the US, Canada and most of the Caribbean dial each other as 1 + ten digits). Use get_call_price for what a call costs per minute from a web browser with InternationalCall.co. Results include a guide link and a browser-dialer link to share with the user.

endpoint
https://internationalcall.co/api/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 internationalcall-dialing live?
Yes — it answered the hub's last check (checked 19m ago). It answered 99% of checks over the last 30 days.
Is internationalcall-dialing free to use?
Not measured yet.
What tools does internationalcall-dialing have?
2 tools: get_call_price, get_dialing_instructions.
Is internationalcall-dialing 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
98.9%

90 days 99.3%· all time 99.3%

latency
313ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 401 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • get dialing instructions for another country
  • get per-minute price of an international call
takes → gives
text → data
tools
2 reads
_ 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_call_price reads unknown 7h ago

    Per-minute price of calling a country, or a specific number, from a web browser with InternationalCall.co: the live rate, whether the free welcome credit covers a first call, how billing works, and a link that opens the dialer set to that country. Use it when someone asks what a call abroad costs or how to call a phone abroad from a computer. For which digits to dial, use get_dialing_instructions instead. Pass `destination` for the country's standard rate, or `number` to price that exact number: premium, satellite-adjacent and special-service ranges cost more than the standard rate (a local-format number also needs `destination`). The rate depends only on the number called, not on where the caller is.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "number": {
          "type": "string",
          "maxLength": 40,
          "description": "A specific phone number, as the caller has it: local format (\"55 1234 5678\", needs destination) or international (\"+52 55 1234 5678\")."
        },
        "destination": {
          "type": "string",
          "maxLength": 80,
          "description": "Country being called: an ISO 3166-1 alpha-2 code such as \"MX\", or an English name such as \"Mexico\"."
        }
      },
      "additionalProperties": false
    }
    arguments 17 lines
  • get_dialing_instructions reads unknown 7h ago

    Exact digits to dial a phone in another country from the caller's country: exit code, country code, and the national number with its trunk prefix correctly dropped or kept, plus the + form for mobiles and numbered steps. Use it for any "how do I call this country or number" question, including shared-code zones (the US, Canada and most of the Caribbean dial 1 + ten digits, with no exit code). For what the call costs, use get_call_price instead. Pass `number` for that number's exact sequence (a + international number needs nothing else; a local-format number also needs `destination`), or only `destination` for the country's rule and a real example. `origin` defaults to the US. Derived from Google's libphonenumber metadata.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "number": {
          "type": "string",
          "maxLength": 40,
          "description": "A specific phone number, as the caller has it: local format (\"55 1234 5678\", needs destination) or international (\"+52 55 1234 5678\")."
        },
        "origin": {
          "type": "string",
          "maxLength": 80,
          "description": "Country the caller is dialing from (default \"US\"): an ISO 3166-1 alpha-2 code such as \"MX\", or an English name such as \"Mexico\"."
        },
        "destination": {
          "type": "string",
          "maxLength": 80,
          "description": "Country being called: an ISO 3166-1 alpha-2 code such as \"MX\", or an English name such as \"Mexico\"."
        }
      },
      "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 0d0a4ac2d9ecf11a.

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