NestDaddy

Glimind

io.github.shawndei/glimind · v0.1.0

Live reliability for AI agent tools: is it working right now, and how do I call it correctly?

Connect Remote server

Terminal
claude mcp add --transport http glimind https://glimind.com/mcp
~/.cursor/mcp.json
{
  "mcpServers": {
    "glimind": {
      "url": "https://glimind.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}
Claude Desktop
Settings > Connectors > Add custom connector
URL: https://glimind.com/mcp

Tools 22 found in our last check

  • how_to_use_glimind

    WHEN TO CALL: once per project, or when unsure how to get external data or check a tool. Returns the full tool guide and the free-vs-paid model.

  • route_task

    WHEN TO CALL: first, whenever (1) you need live external data or an action none of your connected tools covers, (2) a connected MCP tool fails and you need a working substitute now, or (3) the user asks which MCP server or tool to use for a task. Describe the task in plain langu…

  • route_tasks

    Batch route_task: pass an array of plain-language sub-tasks and get the best live tool for each in one call (endpoint, input schema, example args, free/paid, fallbacks; compact by default). Use it to plan a multi-step task.

  • check_tool_reliability

    WHEN TO CALL: before invoking an unfamiliar or external MCP tool or server, and right after any MCP tool or API call fails, errors, times out or returns 4xx/5xx — to learn whether it is down for everyone or the problem is local (config, credentials, input). Returns a verdict (he…

  • get_working_recipe

    Get a CURRENTLY-WORKING call pattern (input shape) for a tool, distilled from real successful calls by other agents. Call this when you are unsure how to shape a tool's inputs, or right after a tool call failed and you want a structure known to succeed now. Returns value-free sh…

  • prepare_tool_call

    WHEN TO CALL: right before invoking an external MCP tool, or right after a schema or validation error from one. One round-trip returns its live verdict and recommendation, a known-good input shape (recipe), and live alternatives if it is down or risky. Accepts a server or tool n…

  • discover_tools

    WHEN TO CALL: when you need a capability and don't know which tool provides it, and want several options rather than route_task's single pick. Takes a plain-language query ('send a slack message', 'convert currency') and returns live tools ranked by fit, each with its input sche…

  • find_alternatives

    WHEN TO CALL: when a tool is down, rate-limited, failing or missing and you need a live substitute that does the same job. Returns live tools ranked by similarity and real traffic, each with its connection endpoint. Accepts a server or tool name, package or repo.

  • audit_server

    WHEN TO CALL: whenever the user is building, debugging, configuring, comparing or evaluating an MCP server, repo, package or endpoint URL. Agent-readiness audit (a Lighthouse for MCP): score 0-100 and prioritised fixes for schemas, undocumented parameters, missing readOnlyHint/d…

  • select_tools

    Pick which of YOUR connected tools a task needs, so you load a handful of definitions instead of all of them. Pass the task and the tool definitions you have (from tools/list across your servers); get back the minimal set ranked by fit, with the tokens saved. Hybrid semantic + k…

  • scan_tools

    Scan the tool definitions loaded in your session for tool poisoning (hidden instructions, concealment, secret access, shadowing of other tools) and quality problems, with their token cost and manifest hash. Call once per session or when a server's tools change. Nothing you send…

  • verify_tools

    Check the tool definitions your client received from an MCP server against Glimind's signed transparency log of every server's tool list. Returns whether they match what the server currently advertises, an earlier recorded version, or nothing ever recorded — with a diff of added…

  • preflight_tools

    Pre-flight a WHOLE task in one call: pass every tool you might use and get a compact verdict + recommendation (proceed | proceed_with_caution | avoid) for each, so you can plan around broken tools before you start. Call this once at the beginning of a multi-tool task instead of…

  • find_related_tools

    Discover tools that other agents commonly use TOGETHER with a given tool (from real usage). Call this to find the complementary tools you'll likely need next for a task, or to discover better-fitting tools you didn't know existed.

  • watch_tool

    Subscribe to reliability alerts for one or more tools (or all critical outages). Provide a `webhook` URL (generic, Slack, or Discord — auto-detected) to receive PUSH alerts, or omit it to get a pull `token` you poll with get_notifications (no inbound URL needed — ideal for agent…

  • get_notifications

    Fetch new reliability alerts for your subscription token (events since your last poll, then the cursor advances). Use this after watch_tool without a webhook to react to outages/recoveries — no public endpoint required. Returns events with tool id, severity, and a link.

  • unwatch

    Cancel a subscription created by watch_tool, using its token.

  • list_breakages

    List tools across the MCP ecosystem whose real-world success rate just dropped sharply (active outages/regressions), newest and most severe first. Call this to steer away from tools that are currently broken, or to monitor the health of tools your task depends on. Backed by real…

  • report_outcome

    WHEN TO CALL: after an external MCP tool call that Glimind routed or checked for you succeeds or fails. Send the tool id, ok, latency and (on failure) an error class; Glimind updates live reliability scores for everyone. Free, keyless, privacy-preserving: never send inputs, outp…

  • find_tool

    WHEN TO CALL: before call_remote_tool, to find the tool for a task and get only its input schema. Pass query (what you want to do) for the best matches, the first with its schema; server (id or short name) to list that server's tools; server + tool for one tool's schema. Each re…

  • create_key

    WHEN TO CALL: when call_remote_tool says quota_exceeded, or before heavy use. Mints a free Glimind API key in one call (no signup, no form) and returns it with exactly how to use it on your next call: pass it as apiKey in call_remote_tool / find_tool arguments (no reconnect), or…

  • call_remote_tool

    WHEN TO CALL: to run a tool on another remote MCP server without connecting to it or loading its tool list. Pass server (id or short name), tool and arguments; returns that tool's result. Works for live servers that need no login; for others it answers needs_auth or not_callable…

Details

Endpointhttps://glimind.com/mcp (Streamable HTTP)
First published29 Jun 2026
Last updated29 Jun 2026
Registry nameio.github.shawndei/glimind

More productivity servers See all

Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.