Is the Buyukesim MCP server down?

mcp-registry/com.buyukesim/mcp · v1.0.0

healthy
Last checked 2026-10-23 21:18 UTC · handshake 311ms

As of 2026-10-23 21:18 UTC, the Buyukesim MCP server is up with a Glimind reliability score of 88/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 12 outages in 90 days, with a median recovery of 2 minutes.

uptime (30d checks)
99.9%
checks observed
4,455
outages (90d)
12
tools
21

No-logs VPN, real UK +44 number eSIMs and travel-data eSIMs, bought with crypto. No KYC, no account.

Install Buyukesim MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http buyukesim-mcp-server https://buyukesim.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "buyukesim-mcp-server": {
      "type": "http",
      "url": "https://buyukesim.com/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: B (82/100)

B (82/100): 0 error(s), 2 warning(s) across 21 tool(s); ~3,605 tokens of tool definitions.
Scores higher than 37% of 15,594 MCP servers Glimind has audited.
Its tool list costs an agent ~3,605 tokens per session — more than 55% of servers.
80 → 82 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints12
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability92

What to fix (4)

21 of 21 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: check_balance, check_order_status, check_uk_coverage, create_deposit, create_wallet and 16 more

2 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: create_deposit, create_wallet

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

In the last 30 days: 0 tool(s) removed and 2 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

Auto-fix: 17 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.buyukesim%2Fmcp/fixes

check_balance 1 change
{
  "name": "check_balance",
  "description": "Check the balance of the agent wallet (pass the ak_live_ api key from create_wallet). Returns available USD balance.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "api_key": {
        "type": "string",
        "description": "The ak_live_ key returned by create_wallet. Pass it here, or as an Authorization: Bearer header."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
check_order_status 1 change
{
  "name": "check_order_status",
  "description": "Look up the status of a BuyUKeSIM order using its short lookup/magic code (the code the customer received). Returns only the order status - no personal data, no QR.",
  "inputSchema": {
    "type": "object",
    "required": [
      "code"
    ],
    "properties": {
      "code": {
        "type": "string",
        "description": "The order lookup / magic code: 8 letters and digits, often written with a dash after the fourth."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
check_uk_coverage 1 change
{
  "name": "check_uk_coverage",
  "description": "Check whether the UK +44 number has been reported working in a country, from buyers who told us after using it there. Pass a 2-letter ISO country code. Returns how many reports exist and how many said it worked, and says plainly when there are none - an absent country means no evidence either way, not a failure. This is evidence, not a promise: roaming depends on the local network. Read-only.",
  "inputSchema": {
    "type": "object",
    "required": [
      "country"
    ],
    "properties": {
      "country": {
        "type": "string",
        "description": "2-letter ISO country code, e.g. NG, DE, RU."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.buyukesim/mcp"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.buyukesim/mcp"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.buyukesim%2Fmcp.svg)](https://glimind.com/server/mcp-registry%2Fcom.buyukesim%2Fmcp?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.buyukesim%2Fmcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.buyukesim%2Fmcp.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.buyukesim%2Fmcp.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.buyukesim%2Fmcp?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:ede7bcad78005803…, first seen 2026-10-17, included at leaf 6801 of 54,641. Version history · verify what your client received.

Tools (21)

Compare: most reliable finance servers · most reliable other servers · most reliable retrieval servers · most reliable payments servers · most reliable knowledge servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Buyukesim MCP server down right now?

As of 2026-10-23 21:18 UTC, the Buyukesim MCP server is up with a Glimind reliability score of 88/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 12 outages in 90 days, with a median recovery of 2 minutes.

How many tools does Buyukesim MCP server provide?

Buyukesim MCP server advertises 21 tools, including check_balance, check_order_status, check_uk_coverage, create_deposit, create_wallet.

How do I install Buyukesim MCP server?

Point your MCP client at this streamable-http endpoint: https://buyukesim.com/mcp

Is the Buyukesim MCP server safe to connect to an AI agent?

Glimind scanned all 21 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Buyukesim MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve