Remote MCP · Endpoint
io.sota/mcp MCP server
No. io.sota/mcp answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://mcp.sota.io/mcp
The last check completed an MCP handshake.
- Registry name
- io.sota/mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 321 ms
- Tools exposed
- 14 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- EU-native PaaS for AI agents — deploy web apps with one sentence, managed Postgres, GDPR by default.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 321 ms |
| 2 days ago | Handshake completed | 318 ms |
| 4 days ago | Handshake completed | 312 ms |
| 6 days ago | Handshake completed | 323 ms |
| 7 days ago | Handshake completed | 319 ms |
| 9 days ago | Handshake completed | 357 ms |
| 10 days ago | Handshake completed | 317 ms |
| 11 days ago | Handshake completed | 327 ms |
| 14 days ago | Handshake completed | 324 ms |
| 15 days ago | Handshake completed | 328 ms |
| 17 days ago | Handshake completed | 311 ms |
| 19 days ago | Handshake completed | 314 ms |
| 20 days ago | Handshake completed | 305 ms |
| 21 days ago | Handshake completed | 321 ms |
| 22 days ago | Handshake completed | 324 ms |
| 22 days ago | Handshake completed | 336 ms |
| 23 days ago | Handshake completed | 321 ms |
| 25 days ago | Handshake completed | 388 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 18 responding of 18.
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 io.sota/mcp and makes no claim about it beyond what these checks measured.