Other · Remote MCP server
Slipstream
Shared distillation cache for AI agents - every fetch ~73-89% fewer tokens via a shared cache.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.tathagat22/slipstream- Version
- 1.0.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-06-01
- Updated
- 2026-06-01
- Publisher
- tathagat22 (GitHub) · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/tathagat22) · how
- Website
- slipstream-pi.vercel.app
- Repository
- github.com/tathagat22/slipstream
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://slipstream-pi.vercel.app/api/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- mcp-typescript server on vercel 0.1.0 · protocol 2025-06-18
- Tools discovered
- 8:
cached_fetch,cached_outline,slipstream_note,slipstream_recall,slipstream_vote,slipstream_flag,whats_new,slipstream_stats - Checked on
- 2026-10-05
How to connect Slipstream
Slipstream is a remote MCP server: there is nothing to install. Its endpoint is https://slipstream-pi.vercel.app/api/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from tathagat22 (GitHub)
| Server | Runs |
|---|---|
| Plumb MCPTwo-way Figma MCP: extract + verify design-to-code, or generate on-brand Figma pages from a prompt. | Local · stdio |
More other servers
| Server | Runs |
|---|---|
| Slides.comCreate, edit, preview, and share Slides.com presentations. Requires a paid Slides.com account. | Remote · HTTPLive check: sign-in required |
| SlidesflyPublish and manage existing HTML presentations from an MCP-capable Agent. | Remote · HTTPLive check: sign-in required |
| Slidev MCPGenerate, render, and host Slidev presentations from markdown. | Remote · HTTPLive check: ✗ no handshake |
| SlimsnapYour recent screen captures as structured JSON your AI agent can read. Local only, no network. | Local · stdio |
| Slop StoreAgents publish AI-made apps in one call with no key; anyone plays them in the browser. | Remote · HTTPLive check: ✓ handshake |
| slop-chopFind and remove the writing patterns a profile lists. Deterministic, local, no model and no network. | Local · stdio |
| Slug Generator APIURL-friendly slugs from text - transliteration, custom separators. x402 micropayment. | Remote · SSELive check: ✗ no handshake |
| Small SiteValidate and publish built static websites to a public Small Site URL. | Local · stdio |