Remote MCP · Endpoint

glim.sh MCP server

No. glim.sh answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://glim.sh/mcp

The last check completed an MCP handshake.

Registry name
sh.glim/glim
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
323 ms
Tools exposed
14 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Give your agent live data from Twitter, Reddit, the web and GitHub. No API keys, no scraping stack.
Website
https://glim.sh/
Repository
https://github.com/glim-sh/glim-mcp
Listing
From the official MCP registry (active).
Recent checks of glim.sh
CheckedResultHandshake
1 hour agoHandshake completed323 ms
2 days agoHandshake completed428 ms
4 days agoHandshake completed367 ms
5 days agoHandshake completed331 ms
7 days agoHandshake completed363 ms
8 days agoHandshake completed332 ms
9 days agoHandshake completed327 ms
12 days agoHandshake completed311 ms
13 days agoHandshake completed324 ms
15 days agoHandshake completed305 ms
16 days agoHandshake completed317 ms
18 days agoHandshake completed312 ms
19 days agoHandshake completed321 ms
20 days agoHandshake completed313 ms
21 days agoHandshake completed325 ms
21 days agoHandshake completed327 ms
23 days agoHandshake completed319 ms

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

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