MCP server list / glimind
Live reliability for AI agent tools: is it working right now, and how do I call it correctly?
Answered:
4 of 4 checks
- Status
- responds
- Typical response time
- 224.5 ms
- Last checked
- Latest check:
- This server answered at its latest check.Last checked · MCP initialize · 8s limit · HTTP 200 · answered in 214 ms.
- Address
- https://glimind.com/
mcp - Listed in:
- official MCP registry
mcp_registry - Registry name
- io.github.shawndei/
glimind - Transport
- streamable HTTP
streamable-http - Host
glimind.com
An outside server from a public listing, not run by Licium; being listed here is not an endorsement.
What the server says about itself
We have not checked it.- Server name:
- glimind-oracle
- Version:
- 0.1.0
- MCP features it lists:
- tools, extensions
- Tool names:
how_to_use_glimindroute_taskroute_taskscheck_tool_reliabilityget_working_recipeprepare_tool_calldiscover_toolsfind_alternativespreflight_toolsfind_related_toolswatch_toolget_notificationsand 3 more
unwatchlist_breakagesreport_outcome- Instructions excerpt:
- QUICK START (free, no signup): your next call can be route_task({"task": "<what you are trying to do>"}) — it returns the single best LIVE tool for the job, ready to call (inputSchema + call hints + expected output), plus ranked fallbacks. If you already know a tool id, prepare_tool_call({"toolId": "<id>"}) tells you in one round-trip whether it works righ…
Reported Aug 17, 2026, 05:02 AM UTC.
Check history
oldest to newest; each row is one recorded check| Checked | Status | Took | Check |
|---|---|---|---|
| responds | 297 ms | MCP initialize · 8s limit · HTTP 200 | |
| responds | 235 ms | MCP initialize · 8s limit · HTTP 200 | |
| responds | 125 ms | MCP initialize · 8s limit · HTTP 200 | |
| responds | 214 ms | MCP initialize · 8s limit · HTTP 200 |
Need a different server, page or part?
Say what you need. We log your request. It can then go on the bounty board, where anyone can add money toward it. Or put a price on it and start today. Your words go with it.
Agents do the same with request_source or POST /v1/requests; this record is GET /v1/directory/{slug} with the slug from this page's address. Run this server? Register it as a part.
Latest recorded check ; every row above is one recorded call.