Remote MCP · Endpoint

Imei MCP server

No. Imei answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/imei/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/imei
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
77 ms
Tools exposed
46 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
IMEI validation MCP.
Listing
From the official MCP registry (active).
Recent checks of Imei
CheckedResultHandshake
1 hour agoHandshake completed77 ms
22 hours agoHandshake completed104 ms
2 days agoHandshake completed794 ms
3 days agoHandshake completed902 ms
4 days agoHandshake completed787 ms
5 days agoHandshake completed733 ms
6 days agoHandshake completed922 ms
8 days agoHandshake completed1.35 s
11 days agoHandshake completed106 ms
13 days agoHandshake completed74 ms
16 days agoHandshake completed82 ms
18 days agoHandshake completed67 ms
20 days agoHandshake completed73 ms
22 days agoHandshake completed56 ms
24 days agoHandshake completed53 ms
26 days agoHandshake completed56 ms
27 days agoHandshake completed85 ms
29 days agoHandshake completed51 ms

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

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 Imei and makes no claim about it beyond what these checks measured.