List your agent

glimind

MCP server● Hosted · onlinev0.1.0

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

Reviews

No review yet. Used glimind? Be the first to help others choose.

What it does

glimind is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.

No capability identified yet from its description.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES
Local installNO
Version0.1.0
PriceNot in the registry
First seen26 Sept 2026
Last checked1d ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 1d ago (live check)

Hosted endpoint

  • https://glimind.com/mcp streamable-http

In Claude Code: claude mcp add --transport http glimind https://glimind.com/mcp

MCP settings (Claude Desktop, Cursor and other MCP clients)

{
  "mcpServers": {
    "glimind": {
      "url": "https://glimind.com/mcp"
    }
  }
}

Live check

Electra Index connected to the hosted endpoint 1d ago

ONLINE glimind answered an MCP connection on 16 Nov 2026 and introduced itself as glimind-oracle 0.1.0 (MCP protocol 2025-06-18).

22 tools offered to AI assistants

  • 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
  • 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, cre
  • 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; serve
  • 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 other
  • 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, undocume
  • 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_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.
  • 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 know
  • 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 do
  • 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
  • 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
  • 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, wit
Show 10 more
  • 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 s
  • 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 nothi
  • 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 beg
  • 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 (
  • 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
  • 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 too
  • 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, priv
  • 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 /

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Facts & evidence

Each fact shows where it was seen and when.
FactValueEvidenceSourceLast confirmed
Hosted endpointhttps://glimind.com/mcpDECLAREDSRC-001 Official MCP Registry1d ago
Local install (package)noDECLAREDSRC-001 Official MCP Registry1d ago
Remote access (hosted)yesDECLAREDSRC-001 Official MCP Registry1d ago
Websitehttps://glimind.comDECLAREDSRC-001 Official MCP Registry1d ago
Repositoryhttps://github.com/shawndei/mcpinfrastructureDECLAREDSRC-001 Official MCP Registry1d ago
Registry statusactiveDECLAREDSRC-001 Official MCP Registry1d ago
Version0.1.0DECLAREDSRC-001 Official MCP Registry1d ago
MCP serveryesDECLAREDSRC-001 Official MCP Registry1d ago

Change history

Baseline
No change detected yet. History builds up as the robots revisit this server.

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Do you run glimind? Know when it stops answering

For publishers · optional

Its hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.

Monitor glimindLaunch offer $39.99 once, for life instead of $9.99/month · All plans

Monitoring never changes a score or a rank.

Are you the publisher of glimind?

Free · show your listing

An independent listing builds trust with your buyers. Announce it, and add the badge to your website or README.

Announce it on LinkedIn
Listed on Electra IndexListed on Electra Index
<a href="https://electraindex.com/mcp/glimind?utm_source=badge&utm_medium=share&utm_campaign=listing"><img src="https://electraindex.com/api/badge/glimind/card" width="260" height="72" alt="Listed on Electra Index"></a>

Questions about glimind

How do I connect glimind?

Use the hosted endpoint https://glimind.com/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

What tools does glimind offer?

When Electra Index connected on 16 Nov 2026, it listed 22 tools: route_task, check_tool_reliability, find_tool, call_remote_tool, audit_server, how_to_use_glimind, route_tasks, get_working_recipe and more. The full list is in "Live check" above.

Is glimind online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 1d ago.