Cortex RMCP
NPM · CORTEX-RMCP · SCANNED AUG 10
Rust MCP server for homelab logs, syslog, Docker logs, FTS search, and AI transcript correlation.
Available components
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security50
- No malware found by supply-chain analysis.Pass
- Known CVEs could not be checked: the version this server declares is not published in its registry.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: the version this server declares is not published in its registry.Unverified
Provenance & Transparency3
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Provenance check failed: the declared version isn't published, so its provenance can't be verified. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Maintenance history not yet determined.Unverified
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
- Schema quality not yet verified: this package could not be installed in a clean environment, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: this package could not be installed in a clean environment, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: this package could not be installed in a clean environment, so we have no tool definitions to assess.Unverified
Tool Safety–
Not scored yet: our latest scan of this package recorded no findings here. That is usually because the category is newer than the scan, or because we have not captured the MCP schema this package serves yet. It fills in the next time we score it.
Capabilities0
- Protocol version not yet verified: this package could not be installed in a clean environment, so we never saw its MCP handshake.Unverified
Unverified: 4 categories
Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →
How do I install the Cortex RMCP MCP server?
Cortex RMCP runs locally as an npm package, launched with npx -y cortex-rmcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · cortex-rmcp
claude mcp add ai-dinglebear-cortex-rmcp -- npx -y cortex-rmcp
{
"mcpServers": {
"ai-dinglebear-cortex-rmcp": {
"command": "npx",
"args": [
"-y",
"cortex-rmcp"
]
}
}
} {
"servers": {
"ai-dinglebear-cortex-rmcp": {
"command": "npx",
"args": [
"-y",
"cortex-rmcp"
]
}
}
} codex mcp add ai-dinglebear-cortex-rmcp -- npx -y cortex-rmcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-dinglebear-cortex-rmcp": {
"type": "local",
"command": [
"npx",
"-y",
"cortex-rmcp"
],
"enabled": true
}
}
} openclaw mcp add ai-dinglebear-cortex-rmcp --command npx --arg -y --arg cortex-rmcp
mcp_servers:
ai-dinglebear-cortex-rmcp:
command: "npx"
args: ["-y", "cortex-rmcp"] {
"McpServers": {
"ai-dinglebear-cortex-rmcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"cortex-rmcp"
]
}
}
} assistant mcp add ai-dinglebear-cortex-rmcp -t stdio -c npx -a -y cortex-rmcp
{
"mcpServers": {
"ai-dinglebear-cortex-rmcp": {
"command": "npx",
"args": [
"-y",
"cortex-rmcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 10 Aug 26 −6
The score moved with no change recorded against any check. We would rather say so than guess.
- 9 Aug 26 −7
The score moved with no change recorded against any check. We would rather say so than guess.
- 8 Aug 26 −6
The score moved with no change recorded against any check. We would rather say so than guess.
- 7 Aug 26 −7
- Security disclosure: fail → pass ▲ functional
- 6 Aug 26 −6
The score moved with no change recorded against any check. We would rather say so than guess.
- 5 Aug 26 0
- Known CVEs: pass → unverified ▼ security
- Install scripts: partial → unverified ▼ security
- Provenance: Provenance check failed: the declared version isn't published, so its provenance can't be verified. security
- The scripts that run when this package is installed changed: postinstall security
- Maintenance: pass → unverified ▼ functional
- Dependency health: pass → unverified ▼ functional
- License: pass → fail ▼ functional
- Licence: MIT functional
- 31 Jul 26 −6
- Malware scan: pass → unverified ▼ security
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 38
First indexed and scored.
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 10 Aug 2026 · Analysed npm/cortex-rmcp@3.9.1
Provenance Version not published
The package exists but this version is not published, so there is no artifact to attest.
| Result | Version not published |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.
What is the Cortex RMCP MCP server?
Cortex RMCP is an MCP server listed in the public MCP registry as ai.dinglebear/cortex-rmcp. Rust MCP server for homelab logs, syslog, Docker logs, FTS search, and AI transcript correlation. This page covers its npm package (cortex-rmcp).
Is the Cortex RMCP MCP server safe to use?
Cortex RMCP scores 0 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
Is the Cortex RMCP MCP server still maintained?
Cortex RMCP has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 3 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.