Cortex RMCP vs MCP Debug Recorder
Cortex RMCP is an MCP server published by dinglebear.ai. Marketplaces we read that list it: 1 (Official MCP Registry). MCP Debug Recorder is an MCP server published by oaslananka. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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 |   Cortex RMCP | |
|---|---|---|
| Official MCP Registry | Listed Version: 3.13.2 Downloads/month (npm): 785 Downloads/week (npm): 77 Forks (GitHub): 4 Stars (GitHub): 4 Not marked · First seen |
Listed Version: 1.0.1 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 | Cortex RMCP | MCP Debug Recorder |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 4 | No figure on GitHub |
| Forks (GitHub) (differs) | 4 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@dinglebear/cortex) | On your machine (mcp-debug-recorder) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 7, secrets among them: 2 | 3, secrets among them: 0 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/dinglebear-ai/cortex | github.com/oaslananka/mcp-debug-recorder |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
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
Cortex RMCP
Self-hosted homelab log intelligence over MCP, CLI, and REST with SQLite/FTS.
MCP Debug Recorder
Record debug sessions, commands, failed attempts, and successful fixes in local SQLite storage.
How to run each
Cortex RMCP As a local MCP server: npm package
claude mcp add --env "CORTEX_API_TOKEN=<YOUR_CORTEX_API_TOKEN>" --env "CORTEX_TOKEN=<YOUR_CORTEX_TOKEN>" --transport stdio cortex -- npx -y @dinglebear/cortex mcpRequires: CORTEX_API_TOKEN (secret), CORTEX_TOKEN (secret)
MCP Debug Recorder As a local MCP server: npm package
claude mcp add --transport stdio mcp-debug-recorder -- npx -y mcp-debug-recorderCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only Cortex RMCP asks for
CORTEX_API_TOKEN (secret)CORTEX_HOMECORTEX_RMCP_RELEASE_BASE_URLCORTEX_RMCP_REPOCORTEX_RMCP_VERSIONCORTEX_TOKEN (secret)RUST_LOG
Only MCP Debug Recorder asks for
DEBUG_RECORDER_DBFUZZY_THRESHOLDLOG_LEVEL
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Cortex RMCP · What it can do: MCP Debug Recorder · 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.