Remote MCP · Endpoint

Slashtel MCP server

No. Slashtel answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://slashtel.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.slashtel/slashtel
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
94 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Travel data eSIMs in about 200 destinations and mobile top-ups in 100+ countries, live prices.
Listing
From the official MCP registry (active).
Recent checks of Slashtel
CheckedResultHandshake
5 hours agoHandshake completed94 ms
9 days agoHandshake completed151 ms
10 days agoHandshake completed104 ms
11 days agoHandshake completed216 ms
12 days agoHandshake completed117 ms
14 days agoHandshake completed273 ms
14 days agoHandshake completed123 ms
15 days agoHandshake completed168 ms
17 days agoHandshake completed135 ms
19 days agoHandshake completed208 ms
21 days agoHandshake completed340 ms
24 days agoHandshake completed165 ms
26 days agoHandshake completed127 ms
28 days agoHandshake completed107 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 26 responding of 26.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Slashtel and makes no claim about it beyond what these checks measured.