Cortex RMCP
NPM · @DINGLEBEAR/CORTEX · SCANNED SEP 20
Self-hosted homelab log intelligence over MCP, CLI, and REST with SQLite/FTS.
Available components
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 Security94
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs a script at install time (postinstall) that we could not recognise. It may be perfectly ordinary, but we do not read the published tarball, so we cannot say what it does. View diagnostics → Partial
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to dinglebear-ai/cortex). View diagnostics → Pass
- Clear OSI-approved license (AGPL-3.0-only).Pass
- Actively maintained (last published 8 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
- Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we never saw its MCP handshake.Unverified
Unverified: 5 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 @dinglebear/cortex. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @dinglebear/cortex
claude mcp add ai-dinglebear-cortex -- npx -y @dinglebear/cortex
{
"mcpServers": {
"ai-dinglebear-cortex": {
"command": "npx",
"args": [
"-y",
"@dinglebear/cortex"
]
}
}
} {
"servers": {
"ai-dinglebear-cortex": {
"command": "npx",
"args": [
"-y",
"@dinglebear/cortex"
]
}
}
} codex mcp add ai-dinglebear-cortex -- npx -y @dinglebear/cortex
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-dinglebear-cortex": {
"type": "local",
"command": [
"npx",
"-y",
"@dinglebear/cortex"
],
"enabled": true
}
}
} openclaw mcp add ai-dinglebear-cortex --command npx --arg -y --arg @dinglebear/cortex
mcp_servers:
ai-dinglebear-cortex:
command: "npx"
args: ["-y", "@dinglebear/cortex"] {
"McpServers": {
"ai-dinglebear-cortex": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@dinglebear/cortex"
]
}
}
} assistant mcp add ai-dinglebear-cortex -t stdio -c npx -a -y @dinglebear/cortex
{
"mcpServers": {
"ai-dinglebear-cortex": {
"command": "npx",
"args": [
"-y",
"@dinglebear/cortex"
]
}
}
} 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.
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 13 Aug 26 0
- Security disclosure: unverified → pass ▲ functional
- 12 Aug 26 0
- Security disclosure: pass → unverified ▼ functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 10 Aug 26 0
- Package version: 3.12.0 → 3.13.2 functional
- 9 Aug 26 0
- Licence: MIT → AGPL-3.0-only functional
- Package version: 3.11.3 → 3.12.0 functional
- 7 Aug 26 0
- Security disclosure: fail → pass ▲ functional
- 6 Aug 26 0
- Stability: Stability not yet verified: our sandbox run of this package did not complete, so we have no schema to compare. security
- Schema quality: Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess. functional
- Capabilities: Protocol version not yet verified: our sandbox run of this package did not complete, so we never saw its MCP handshake. functional
- Tool coverage: Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess. 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 20 Sept 2026 · Analysed npm/@dinglebear/cortex@3.13.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | dinglebear-ai/cortex |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/dinglebear-ai/cortex/.github/workflows/release.yml@refs/tags/v3.13.2 |
| Rekor log index | 2402739684 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:668c2bbaa624a8b430cdac17d210e5aee4f49e626caa727c57f9e1a88e2eefb460993c9f406bac6d2087e113bf7929a7c486993e49d7c5d61aae12db9 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| postinstall | unreviewed | node scripts/install.js |
Background: Why install scripts are a supply-chain risk →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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. Self-hosted homelab log intelligence over MCP, CLI, and REST with SQLite/FTS. This page covers its npm package (@dinglebear/cortex).
Is the Cortex RMCP MCP server safe to use?
Cortex RMCP scores 48 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. Its build provenance is signed and verified. 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 is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Cortex RMCP MCP server under?
Cortex RMCP declares the AGPL-3.0-only licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.