Remote MCP · Endpoint
TuringCorp MCP server
No. TuringCorp answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://mcp.turingcorp.net/mcp
The last check completed an MCP handshake.
- Registry name
- net.turingcorp.mcp/decider
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 159 ms
- Tools exposed
- 2 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- A decision model for the calls that don't have a right answer. The better option, with a reason.
- Website
- https://mcp.turingcorp.net/
- Repository
- https://github.com/TuringCorp-net/MCP
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 159 ms |
| 1 day ago | Handshake completed | 174 ms |
| 2 days ago | Handshake completed | 210 ms |
| 3 days ago | Handshake completed | 187 ms |
| 4 days ago | Handshake completed | 191 ms |
| 5 days ago | Handshake completed | 261 ms |
| 7 days ago | Handshake completed | 323 ms |
| 9 days ago | Handshake completed | 179 ms |
| 12 days ago | Handshake completed | 490 ms |
| 14 days ago | Handshake completed | 566 ms |
| 16 days ago | Handshake completed | 168 ms |
| 18 days ago | Handshake completed | 263 ms |
| 20 days ago | Handshake completed | 145 ms |
| 22 days ago | Handshake completed | 167 ms |
| 25 days ago | Handshake completed | 173 ms |
| 26 days ago | Handshake completed | 211 ms |
| 27 days ago | Handshake completed | 151 ms |
| 29 days ago | Handshake completed | 362 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 TuringCorp and makes no claim about it beyond what these checks measured.