@neuralnexustech/cortex-mcp
npm
v2.9.0
Published by @neuralnexustech — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
Persistent brain, memory, loop controller, and reminder engine for AI coding agents
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 1.2 = 99. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −1.2 | Package runs install-time scripts MTC-SUP-010 | supply-chain |
2. Client adoption risk — 99 − 7 = 92. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
In the server's implementation (`dashboard/dist/assets/index-DFnwFI-D.js:1`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: 3;function Wl(n){return new Function("d","return {"+n.map(function(t,e){return JSON.stringify(t)+": d["+e+'] || ""'}).jo
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dashboard/dist/assets/index-DFnwFI-D.js
In the server's implementation (`bin/cortex.js:7`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: import { spawn } from 'child_process'; import { getOrCreateConfig, writeConfig, registerPort, registerAgent, unregister
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server bin/cortex.js
"@neuralnexustech/cortex-mcp" executes postinstall script(s) at install time. An install hook runs at install time; most are routine build/setup, but review what it does before trusting it.
Evidence: cd dashboard && npm install && npm run build
Fix: Review the scripts; install with --ignore-scripts where possible and vet what they do.
Location: package @neuralnexustech/cortex-mcp
Each tool and what it can reach — statically extracted from the published source.
cortex_get_token_budgetreads sensitive datacortex_add_decisionno sensitive capabilitycortex_add_featureno sensitive capabilitycortex_add_relationshipno sensitive capabilitycortex_add_researchno sensitive capabilitycortex_add_snippetno sensitive capabilitycortex_add_testno sensitive capabilitycortex_ask_humanno sensitive capabilitycortex_auto_healno sensitive capabilitycortex_check_contradictionsno sensitive capabilitycortex_check_remindersno sensitive capabilitycortex_confirm_destructiveno sensitive capabilitycortex_get_detailno sensitive capabilitycortex_get_next_taskno sensitive capabilitycortex_get_roleno sensitive capabilitycortex_get_skillno sensitive capabilitycortex_get_stateno sensitive capabilitycortex_healthno sensitive capabilitycortex_initno sensitive capabilitycortex_list_agentsno sensitive capabilitycortex_list_skillsno sensitive capabilitycortex_log_issueno sensitive capabilitycortex_log_progressno sensitive capabilitycortex_log_tokensno sensitive capabilitycortex_pipeline_cancelno sensitive capabilitycortex_pipeline_historyno sensitive capabilitycortex_pipeline_pauseno sensitive capabilitycortex_pipeline_planno sensitive capabilitycortex_pipeline_resumeno sensitive capabilitycortex_pipeline_startno sensitive capabilitycortex_pipeline_statusno sensitive capabilitycortex_resolve_contradictionno sensitive capabilitycortex_resolve_issueno sensitive capabilitycortex_rollbackno sensitive capabilitycortex_save_snapshotno sensitive capabilitycortex_searchno sensitive capabilitycortex_set_active_projectno sensitive capabilitycortex_set_roleno sensitive capabilitycortex_tick_fileno sensitive capabilitycortex_update_featureno sensitive capabilitycortex_update_testno sensitive capabilitycortex_write_dictionaryno sensitive capabilityScan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v2.9.0 latest |
A 92/100 | 3 | 1.13.0 | 2026-09-07 |
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan @neuralnexustech/cortex-mcp --online
Independent packages implementing the same tool, scanned with the same engine. Compare all 8 side by side →
Multi-level reasoning MCP server with configurable depth levels
Framework-agnostic MCP server that serves structured knowledge on-demand to any MCP-compatible AI tool
Local-first knowledge graph that watches your project files, extracts entities and relationships via LLMs, and lets you query across projects in natural language.
Persistent memory for AI coding assistants. Injects context from past sessions into every LLM request.
Making AI Accountable Over Time - MCP server for persistent memory, automatic verification, and evidence-based grounding
MCP server with 12 deterministic calendar and temporal tools — calendar discovery, temporal context, datetime resolution, atomic booking, RRULE expansion, and availability merging
FDA device & vehicle recall risk for AI agents: recall history, MAUDE trend, risk score.
Open-source MCP server exposing Agent402.Tools' catalog — 500+ strong: 400+ self-hostable tools + 100 multi-tool skill packs (security-audit, trend-analysis, structured-scrape, decode-blob, forecasting-bake-off) for AI agents — browser, web search & answe
Zero-dependency MCP server that gives AI agents a self-updating project memory in AGENTS.md. Returns merge instructions instead of mutating state, so every change is a reviewable diff.
MCP Apps UI resources and server helpers for n8n
MCP server providing comprehensive access to BookStack knowledge management system
MCP server for tracking achievements with STAR methodology