Remote MCP · Endpoint
Local Model Suitability MCP MCP server
No. Local Model Suitability MCP answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://local-model-suitability-mcp-production.up.railway.app/
The last check completed an MCP handshake.
- Registry name
- io.github.OjasKord/local-model-suitability-mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2024-11-05
- Handshake latency
- 132 ms
- Tools exposed
- 1 tool
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Check if a task runs locally vs cloud. Save money on calls that don't need cloud inference.
- Website
- https://kordagencies.com/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 132 ms |
| 1 day ago | Handshake completed | 96 ms |
| 2 days ago | Handshake completed | 113 ms |
| 3 days ago | Handshake completed | 106 ms |
| 4 days ago | Handshake completed | 94 ms |
| 5 days ago | Handshake completed | 218 ms |
| 6 days ago | Handshake completed | 104 ms |
| 9 days ago | Handshake completed | 130 ms |
| 11 days ago | Handshake completed | 106 ms |
| 14 days ago | Handshake completed | 98 ms |
| 16 days ago | Handshake completed | 96 ms |
| 18 days ago | Handshake completed | 94 ms |
| 20 days ago | Handshake completed | 122 ms |
| 22 days ago | Handshake completed | 92 ms |
| 24 days ago | Handshake completed | 88 ms |
| 26 days ago | Handshake completed | 274 ms |
| 28 days ago | Handshake completed | 121 ms |
| 29 days ago | Handshake completed | 90 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 Local Model Suitability MCP and makes no claim about it beyond what these checks measured.