Servidor MCP de Glimind

• Direcciónhttps://glimind.com/mcpno está en el registro oficial: respondió al preguntarle

Ninguna entrada del registro oficial de MCP nombra este servidor. Respondió en glimind.com cuando el Atlas preguntó en la dirección donde suelen montarse los servidores, así que es del propio proveedor. Los clientes y catálogos que listan servidores a partir del registro no lo muestran.

• Estadorespondecomprobado el 2026-10-28
• Herramientas19
• El servidor se llamaglimind-oracle
• Versión del servidor0.1.0
• Versión del protocolo2025-06-18

El 2026-10-28 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 205 ms.

• Aún no se ha juzgado si sus herramientas hacen el trabajo del producto.
• Comprobado 5 de los 7 días necesarios para juzgar su fiabilidad.

Lo dicen reglas a partir de las mediciones de arriba. La primera llamada probable la elige un modelo de la lista de herramientas; lee su descripción antes de fiarte.

• Nota INITE MCPtras una semanala nota necesita 7 comprobaciones diarias: 5 hasta ahora
• Respondiómidiendo5 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
• Mediana de la primera respuesta86 ms
• Espacio en el contexto del agente≈ 4036 tokenslas definiciones de todas sus herramientas (21), que el agente lleva en cada turno
• Definiciones de herramientasA · 100 de 100
• Resultados tipados0 de 21 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez

• Todas las herramientas pasan las seis comprobaciones.

Un programa comprueba el servidor una vez al día: initialize y tools/list, sin modelo. Los tokens son la longitud de las definiciones, a unos cuatro caracteres por token. La nota promedia seis comprobaciones del nombre, la descripción, el esquema y las anotaciones de cada herramienta; dice lo bien descritas que están, no si funcionan. La nota pondera solo lo medido: si responde (25%), si hace el trabajo del producto (25%), definiciones (20%), contexto (10%), uso (10%) y lo fácil que es conectarse (10%). Lo que no se midió queda fuera, y una instrucción oculta limita la nota a 40. El estado de los servidores MCP de los proveedores: método y números →

• 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, the free-vs-paid model and a short memoryBlock to save in CLAUDE.md / AGENTS.md / .cursorrules so the next session knows…

• 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…

• 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…

• 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…

• 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…

• 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…

• 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…

• 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…

• 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…

• 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…

• 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…

• 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…

• 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…

• 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…

• 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…