Remote MCP · Endpoint

io.github.tathagat22/slipstream MCP server

No. io.github.tathagat22/slipstream answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://slipstream-pi.vercel.app/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.tathagat22/slipstream
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.93 s
Tools exposed
8 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Shared distillation cache for AI agents — every fetch ~73-89% fewer tokens via a shared cache.
Website
https://slipstream-pi.vercel.app/
Repository
https://github.com/tathagat22/slipstream
Listing
From the official MCP registry (active).
Recent checks of io.github.tathagat22/slipstream
CheckedResultHandshake
2 hours agoHandshake completed1.93 s
2 days agoHandshake completed99 ms
4 days agoHandshake completed55 ms
5 days agoHandshake completed88 ms
7 days agoHandshake completed68 ms
8 days agoHandshake completed68 ms
9 days agoHandshake completed235 ms
12 days agoHandshake completed61 ms
13 days agoHandshake completed74 ms
15 days agoHandshake completed175 ms
17 days agoHandshake completed58 ms
18 days agoHandshake completed155 ms
19 days agoHandshake completed133 ms
20 days agoHandshake completed77 ms
20 days agoHandshake completed1.95 s
21 days agoHandshake completed64 ms
23 days agoHandshake completed1.58 s

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 io.github.tathagat22/slipstream and makes no claim about it beyond what these checks measured.