deadends.dev vs Execute deadlock-resolver-mcp
deadends.dev is an MCP server published by deadends.dev. Marketplaces we read that list it: 1 (Official MCP Registry). Execute deadlock-resolver-mcp is an MCP server published by Evozim. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  deadends.dev | |
|---|---|---|
| Official MCP Registry | Listed Version: 0.9.0 Downloads/month (PyPI): 199 Downloads/week (PyPI): 45 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 2.0.0 No figure published Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | deadends.dev | Execute deadlock-resolver-mcp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server or your machine | Remote server (api.m2mcent.com/deadlock-resolver-mcp/sse) |
| Transport (differs) | Streamable HTTP, stdio | SSE |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/dbwls99706/deadends.dev | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | not checked yet | Answered with HTTP 402 (2 days ago) |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
deadends.dev
Structured failure knowledge for AI agents — dead ends, workarounds, error chains
Execute deadlock-resolver-mcp
Premium agentic endpoint for deadlock-resolver-mcp.
How to run each
deadends.dev As a remote MCP server
claude mcp add --transport http deadends-dev https://deadends.dev/mcpExecute deadlock-resolver-mcp As a remote MCP server
claude mcp add --transport sse deadlock-resolver-mcp https://api.m2mcent.com/deadlock-resolver-mcp/sse --header "Payment-Signature: <YOUR_PAYMENT_SIGNATURE>"Requires: Payment-Signature header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Execute deadlock-resolver-mcp has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: deadends.dev · What it can do: Execute deadlock-resolver-mcp · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.