ai.dinglebear/cortex-rmcp
Cortex RMCP
Is the Cortex R MCP server down? Yes. It has given no valid answer since 2026-10-19: not found.
Rust MCP server for homelab logs, syslog, Docker logs, FTS search, and AI transcript correlation.
not found down since 2026-10-19 · probed 2026-11-15 · unchanged since 2026-10-26
npm error notarget In most cases you or one of your dependencies are requesting npm error notarget a package version that doesn't exist. npm error A complete lo
- Run it
- npx -y cortex-rmcp@3.9.1 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/jmagar/cortex
- Website
- https://github.com/jmagar/cortex
- Registry
- active, updated 2026-07-12 · registry entry
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- Dimensions Analytics ai.dimensions/analytics-mcp · needs env
- Apprise RMCP ai.dinglebear/apprise-rmcp · not found
- Arcane RMCP ai.dinglebear/arcane-rmcp · not found
- Cortex RMCP ai.dinglebear/cortex · needs env
- Gotify RMCP ai.dinglebear/gotify-rmcp · not found
- Labby ai.dinglebear/labby · needs env
- Apprise RMCP ai.dinglebear/rapprise · needs env
- Arcane RMCP ai.dinglebear/rarcane · needs env
Servers that mention cortex.
- com.cortexpad/cortexpad · needs auth
- AI Cortex Storage dev.aic0rt3x.memory/mcp · timeout
- CortexPlus io.cortexplus/cortexplus · alive
- Cortex io.github.100monkeys-ai/cortex · needs your URL
- Cortex io.github.FilippoPilo/cortex · alive
- AnswerPool (formerly CortexAssay) io.github.blakeyounger/cortexassay · not found
- io.github.jonahthan433/cortexcloud · no DNS
- io.github.meltingpixelsai/zero-core-intel · not found
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- No valid answer since 2026-10-19, in every probe since then.
- The endpoint answers HTTP 404. The registry entry points to a URL that is not an MCP endpoint any more. Publish a new version of the registry entry with the current URL.