Remote MCP · Endpoint
Synap MCP server
No. Synap answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://pool.linkrra.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.linkrra/synap
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 288 ms
- Tools exposed
- 4 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Open AI models through one OpenAI-compatible API: chat, live model list, prices and cost estimates.
- Website
- https://synap.linkrra.com/
- Repository
- https://github.com/jimmyplup/synap-mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 288 ms |
| 18 hours ago | Handshake completed | 287 ms |
| 2 days ago | Handshake completed | 282 ms |
| 3 days ago | Handshake completed | 286 ms |
| 4 days ago | Handshake completed | 325 ms |
| 5 days ago | Handshake completed | 622 ms |
| 6 days ago | Handshake completed | 367 ms |
| 7 days ago | Handshake completed | 251 ms |
| 10 days ago | Handshake completed | 250 ms |
| 13 days ago | Handshake completed | 249 ms |
| 15 days ago | Handshake completed | 252 ms |
| 17 days ago | Handshake completed | 265 ms |
| 19 days ago | Handshake completed | 246 ms |
| 21 days ago | Handshake completed | 244 ms |
| 23 days ago | Handshake completed | 260 ms |
| 25 days ago | Handshake completed | 242 ms |
| 27 days ago | Handshake completed | 252 ms |
| 28 days ago | Handshake completed | 245 ms |
| 29 days ago | Handshake completed | 243 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 30 responding of 30.
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 Synap and makes no claim about it beyond what these checks measured.