Remote MCP · Endpoint

io.github.MassimoSun/smsverbot-mcp MCP server

No. io.github.MassimoSun/smsverbot-mcp answered an MCP handshake 57 minutes ago.

UpLast checked 57 minutes ago

Server URL

https://kremledroid.duckdns.org/mcp

The last check completed an MCP handshake.

Registry name
io.github.MassimoSun/smsverbot-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
373 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
SMS verification for AI agents: buy a number, get the code, cancel with refund. Free sandbox.
Listing
From the official MCP registry (active).
Recent checks of io.github.MassimoSun/smsverbot-mcp
CheckedResultHandshake
57 minutes agoHandshake completed373 ms
3 days agoHandshake completed284 ms
12 days agoHandshake completed283 ms
13 days agoHandshake completed285 ms
15 days agoHandshake completed290 ms
15 days agoHandshake completed288 ms
17 days agoHandshake completed287 ms
18 days agoHandshake completed290 ms
18 days agoHandshake completed301 ms
20 days agoHandshake completed281 ms
22 days agoHandshake completed334 ms
25 days agoHandshake completed553 ms
27 days agoHandshake completed288 ms

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

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.

Listing data comes from the official MCP registry. Glide is not affiliated with io.github.MassimoSun/smsverbot-mcp and makes no claim about it beyond what these checks measured.