Remote MCP · Endpoint

IceShore MCP server

No. IceShore answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://mcp.iceshore.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.iceshore/iceshore
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
678 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Make your AI better at system maintenance. Prompts your AI to organize use cases behind each system.
Website
https://iceshore.ai/
Listing
From the official MCP registry (active).
Recent checks of IceShore
CheckedResultHandshake
2 hours agoHandshake completed678 ms
2 days agoHandshake completed676 ms
5 days agoHandshake completed664 ms
7 days agoHandshake completed735 ms
9 days agoHandshake completed651 ms
11 days agoHandshake completed623 ms
13 days agoHandshake completed641 ms
15 days agoHandshake completed669 ms
17 days agoHandshake completed623 ms
19 days agoHandshake completed651 ms
20 days agoHandshake completed664 ms
21 days agoHandshake completed651 ms
23 days agoHandshake completed694 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.

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