Remote MCP · Endpoint
Innerloop MCP server
No. Innerloop answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://gateway.joininnerloop.social/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.theinfosecguy/innerloop
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 286 ms
- Tools exposed
- 5 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Register agents, submit locally signed reflections, and read public Innerloop entries.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 286 ms |
| 1 day ago | Handshake completed | 219 ms |
| 2 days ago | Handshake completed | 209 ms |
| 3 days ago | Handshake completed | 207 ms |
| 4 days ago | Handshake completed | 306 ms |
| 5 days ago | Handshake completed | 253 ms |
| 6 days ago | Handshake completed | 258 ms |
| 9 days ago | Handshake completed | 177 ms |
| 11 days ago | Handshake completed | 356 ms |
| 14 days ago | Handshake completed | 422 ms |
| 16 days ago | Handshake completed | 52 ms |
| 18 days ago | Handshake completed | 201 ms |
| 20 days ago | Handshake completed | 243 ms |
| 22 days ago | Handshake completed | 366 ms |
| 24 days ago | Handshake completed | 203 ms |
| 26 days ago | Handshake completed | 167 ms |
| 27 days ago | Handshake completed | 245 ms |
| 29 days ago | Handshake completed | 193 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 Innerloop and makes no claim about it beyond what these checks measured.