InternationalCall.co dialing
REMOTE · INTERNATIONALCALL.CO · SCANNED SEP 27
Exact international dialing instructions for any country or number, plus per-minute call prices.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 504 tokens (~252/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the InternationalCall.co dialing MCP server?
InternationalCall.co dialing is a hosted endpoint at https://internationalcall.co/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · internationalcall.co
claude mcp add --transport http co-internationalcall-dialing 'https://internationalcall.co/api/mcp'
{
"mcpServers": {
"co-internationalcall-dialing": {
"url": "https://internationalcall.co/api/mcp"
}
}
} {
"servers": {
"co-internationalcall-dialing": {
"type": "http",
"url": "https://internationalcall.co/api/mcp"
}
}
} [mcp_servers.co-internationalcall-dialing] url = "https://internationalcall.co/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"co-internationalcall-dialing": {
"type": "remote",
"url": "https://internationalcall.co/api/mcp",
"enabled": true
}
}
} openclaw mcp add co-internationalcall-dialing --url 'https://internationalcall.co/api/mcp' --transport streamable-http
mcp_servers:
co-internationalcall-dialing:
url: "https://internationalcall.co/api/mcp" {
"McpServers": {
"co-internationalcall-dialing": {
"Transport": "http",
"Url": "https://internationalcall.co/api/mcp"
}
}
} assistant mcp add co-internationalcall-dialing -t streamable-http -u 'https://internationalcall.co/api/mcp'
{
"mcpServers": {
"co-internationalcall-dialing": {
"type": "http",
"url": "https://internationalcall.co/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 27 Sept 26 73
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 27 Sept 2026 · Probed https://internationalcall.co/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=internationalcall.co | CN=YR2,O=Let's Encrypt,C=US | 7 Sept 2026 | 6 Dec 2026 | RSA 2048 | SHA256-RSA | 5f67720203f7b98df84fc12307896f23f29 |
| SANs: internationalcall.co | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of internationalcall.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| co. | present | 7786 | 8 | Verified |
| internationalcall.co. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' 'wasm-unsafe-eval' https://js.stripe.com https://platform.twitter.com https://www.googletagmanager.com; worker-src 'self' blob:; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; img-src 'self' data: blob: https:; font-src 'self' https://fonts.gstatic.com; connect-src 'self' https://*.supabase.co wss://*.supabase.co https://api.stripe.com https://*.twilio.com wss://*.twilio.com https://*.google-analytics.com https://*.analytics.google.com https://*.googletagmanager.com; frame-src 'self' https://js.stripe.com https://hooks.stripe.com https://www.youtube-nocookie.com https://www.youtube.com https://player.vimeo.com https://www.loom.com https://www.dailymotion.com https://platform.twitter.com; frame-ancestors 'self' http://localhost:* https://o-mega.ai https://*.o-mega.ai https://founden.ai https://*.founden.ai https://*.founden.co https://*.e2b.app https://*.vercel.app; object-src 'none'; base-uri 'self' |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(self), microphone=(self), display-capture=(self), geolocation=(), browsing-topics=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://internationalcall.co/api/mcp | Verified | 200 | |
| http (plaintext) | http://internationalcall.co/api/mcp | HTTPS enforced | 308 | https://internationalcall.co/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_call_price Price of a call from the browser ~168
Per-minute price of calling a country, or a specific number, from a web browser with InternationalCall.co: live rates, whether the free welcome credit covers a first call, how billing works, and a link that opens the dialer set to that country. A number in a dearer prefix range (premium, satellite-adjacent, special services) is quoted at its own higher rate.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | – | Country being called: an ISO 3166-1 alpha-2 code such as "MX", or an English name such as "Mexico". |
| number | string | – | A specific phone number, as the caller has it: local format ("55 1234 5678", needs destination) or international ("+52 55 1234 5678"). |
| Name | Type | Req | Description |
|---|---|---|---|
| billing | string | yes | – |
| callUrl | string|null | yes | – |
| callable | boolean | yes | – |
| destination | object | yes | – |
| firstCallCovered | boolean | yes | – |
| note | string|null | yes | – |
| number | string|null | yes | – |
| numberPricePerMinute | string|null | yes | – |
| pricePerMinute | string|null | yes | – |
| pricingUrl | string | yes | – |
| welcomeCredit | string | yes | – |
No examples provided.
get_dialing_instructions How to dial an international number ~210
Exact dialing instructions from one country to another: the digits to press (exit code, country code, and the national number with any trunk prefix correctly dropped or kept), the + form for mobiles, and step-by-step guidance. Pass a specific number to get its exact dial sequence, or just the destination for the rule and a real example. Derived from Google's libphonenumber metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | – | Country being called: an ISO 3166-1 alpha-2 code such as "MX", or an English name such as "Mexico". |
| number | string | – | A specific phone number, as the caller has it: local format ("55 1234 5678", needs destination) or international ("+52 55 1234 5678"). |
| origin | string | – | 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". |
| Name | Type | Req | Description |
|---|---|---|---|
| callUrl | string|null | yes | – |
| destination | object | yes | – |
| dialSequence | string | yes | – |
| fromAnyMobile | string | yes | – |
| guideUrl | string|null | yes | – |
| isExample | boolean | yes | – |
| kind | string | yes | – |
| note | string|null | yes | – |
| number | – | yes | – |
| origin | object | yes | – |
| steps | array | yes | – |
| trunkRule | string | yes | – |
No examples provided.
What is the InternationalCall.co dialing MCP server?
InternationalCall.co dialing is an MCP server listed in the public MCP registry as co.internationalcall/dialing. Exact international dialing instructions for any country or number, plus per-minute call prices. This page covers its hosted endpoint (https://internationalcall.co/api/mcp).
Is the InternationalCall.co dialing MCP server safe to use?
InternationalCall.co dialing scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the InternationalCall.co dialing MCP server expose?
InternationalCall.co dialing exposes 2 tools: get_dialing_instructions, get_call_price. Their descriptions and schemas cost roughly 378 tokens of context every time the server is loaded.
Does the InternationalCall.co dialing MCP server require authentication?
No. We connected to InternationalCall.co dialing without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the InternationalCall.co dialing MCP server still maintained?
InternationalCall.co dialing is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.