mcp-registry/io.github.elyngved/failmodes · v0.1.0
As of 2026-10-22 21:05 UTC, the Elyngved Failmodes MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
MCP server for the Fail Modes taxonomy — a knowledge base of AI system failure modes
Claude Code
claude mcp add --transport http elyngved-failmodes-mcp-server https://www.failmodes.com/api/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"elyngved-failmodes-mcp-server": {
"type": "http",
"url": "https://www.failmodes.com/api/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
4 of 4 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.elyngved%2Ffailmodes/fixes
{
"name": "get_failure_mode",
"description": "Retrieve the full structured record for a single failure mode by its ID slug (e.g. 'citation-hallucination', 'sycophancy').",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"id"
],
"properties": {
"id": {
"type": "string",
"minLength": 1,
"description": "The failure mode ID slug, e.g. 'citation-hallucination'"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "list_categories",
"description": "List all taxonomy categories with their IDs, names, descriptions, and mode counts.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "list_modes",
"description": "List failure modes, optionally filtered to a single category by category ID.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"category": {
"type": "string",
"description": "Optional category ID to filter by, e.g. 'factuality'. Omit to list all modes."
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.elyngved/failmodes"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.elyngved/failmodes"}) over MCP.
search_failure_modes ~130 tokensget_failure_mode ~110 tokenslist_modes ~94 tokenslist_categories ~63 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.elyngved%2Ffailmodes?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.elyngved%2Ffailmodes?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.elyngved%2Ffailmodes.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.elyngved%2Ffailmodes.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.elyngved%2Ffailmodes?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:392d51b0d56fb838…, first seen 2026-10-17, included at leaf 5943 of 48,137. Version history · verify what your client received.
Compare: most reliable retrieval servers · most reliable knowledge servers · most reliable other servers · most reliable search servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-22 21:05 UTC, the Elyngved Failmodes MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Elyngved Failmodes MCP server advertises 4 tools, including get_failure_mode, list_categories, list_modes, search_failure_modes.
Point your MCP client at this streamable-http endpoint: https://www.failmodes.com/api/mcp
Glimind scanned all 4 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.