Query this database from inside your agent

claude mcp add --transport http stupidllm https://www.stupidllm.com/api/mcp/

Or point any MCP client at https://www.stupidllm.com/api/mcp/. Read-only, no key, no signup. The trailing slash matters.

Tools

• search_incidents — Filter by agent, failure mode, minimum severity, or date.
• get_incident — One full record: what was instructed, what happened, and the primary source.
• get_agent_reliability — Incident count, average and maximum severity, failure-mode breakdown.
• list_agents — Every agent tracked, with counts. Call this first to learn the vocabulary.
• compare_agents — Two or more agents side by side.

What you get back

Every row carries its source_url and a canonical link, so an answer built on this can be checked by whoever reads it. That is the entire point of the database and it does not change because the caller is a machine.

get_agent_reliability returns a caveat alongside the numbers, and it is worth repeating here: incident counts measure what has been documented, not how often an agent fails. An agent with more incidents may simply be more used, or more written about. Do not build a league table out of them.

Attribution

Free to call, including commercially. If an answer you produce rests on a row from here, cite the incident page — https://www.stupidllm.com/incident/<stupid_id>/ — so the reader can reach the primary source.

Read-only, and staying that way

There are no write tools and there will not be. An MCP server that accepts incident submissions is an unauthenticated write path into the content this site’s credibility rests on. Submissions go through the form, where a human checks the source.

This is an experiment

It is new, and whether it stays depends on whether anything actually calls it. Calls are logged server-side — tool name, parameters, and whether the corpus could answer. No IP addresses, no payloads, no identity: the only name recorded is the one your client volunteers in its handshake.

There is a rate limit, and it is the one place an address is touched at all. It is hashed the moment the request arrives, held in memory to count that minute’s requests, and discarded. It is never written to the log, to a database, or to disk.

The queries that return nothing are the ones worth having. A search this database cannot answer is a direct request for data it should have, and it is better evidence than anything inferred from search rankings. If you ask it something and get an empty result, that is useful — it means the gap gets written up.

Machine-readable

/.well-known/mcp.json describes the server. A GET to the endpoint itself returns the tool list.