Home / MCP registry index / io.github.shawndei/glimind
io.github.shawndei/glimind
io.github.shawndei/glimind in the official MCP registry.
Endpoint https://glimind.com/mcp. Source: github.com/shawndei/mcpinfrastructure.
The registry describes it as: Live reliability for AI agent tools: is it working right now, and how do I call it correctly?
We read its 19 tools on 2026-10-26. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
how_to_use_glimind route_task route_tasks check_tool_reliability get_working_recipe prepare_tool_call discover_tools find_alternatives audit_server select_tools scan_tools verify_tools preflight_tools find_related_tools watch_tool get_notifications unwatch list_breakages report_outcome
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-shawndei-glimind)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.