Nexo Brain MCP Server

nexo-brain npm v7.38.7

Published by wazionapps — 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.

NEXO runtime core for NEXO Desktop. Provides local memory, Deep Sleep, Evolution support-ticket mode, skills, watchdog, and MCP tooling for the Desktop product.

Trust grade
B
86/100
Last scanned get badge →
Trust
B · 86/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
B Why this grade threat 93 − adoption risk = 86/100

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 − 7.5 = 93. What the published surface and source actually contain:

PointsWhat was foundCategory
−6.3 Untrusted input concatenated into a command sink MTC-SRC-009 injection
−1.2 Package runs install-time scripts MTC-SUP-010 supply-chain

2. Client adoption risk — 93 − 7 = 86. 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:

PointsAdoption-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.

Findings 16

high Reads a sensitive credential path or dumps the environment (src/local_context/privacy.py)MTC-SRC-006

In the server's implementation (`src/local_context/privacy.py:10`): Reading private keys / cloud credentials, or serializing the whole environment, is a sensitive-data source that becomes exfiltration when combined with any egress. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: ".env.production", ".npmrc", ".pypirc", ".netrc", ".boto", ".pgpass", ".my.cnf", ".git-cred

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 src/local_context/privacy.py

high Reads a sensitive credential path or dumps the environment (src/r23g_secrets_in_output.py)MTC-SRC-006

In the server's implementation (`src/r23g_secrets_in_output.py:34`): Reading private keys / cloud credentials, or serializing the whole environment, is a sensitive-data source that becomes exfiltration when combined with any egress. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: ]*" r"(?:[/\w.-]*(?:id_rsa|\.pem|\.p12|\.pfx|\.crt\.key|credentials(?:\.json)?|secrets?\.(?:json|yaml|env))" r"|

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 src/r23g_secrets_in_output.py

high Shell/command execution in server code (bin/nexo-brain.js)MTC-SRC-002

In the server's implementation (`bin/nexo-brain.js:17`): 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: spawnSync } = require("child_process"); const crypto = require("crypto"); const fs = require("fs"); const { createRequi

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/nexo-brain.js

high Shell/command execution in server code (bin/nexo-managed-mcp.js)MTC-SRC-002

In the server's implementation (`bin/nexo-managed-mcp.js:6`): 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: st { spawn } = require("child_process"); function nexoHome() { return process.env.NEXO_HOME || path.join(require("os"

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/nexo-managed-mcp.js

high Shell/command execution in server code (bin/nexo.js)MTC-SRC-002

In the server's implementation (`bin/nexo.js:10`): 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: spawnSync } = require("child_process"); const fs = require("fs"); const os = require("os"); const path = require("path"

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/nexo.js

high Shell/command execution in server code (bin/windows-wsl-bridge.js)MTC-SRC-002

In the server's implementation (`bin/windows-wsl-bridge.js:1`): 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: spawnSync } = require("child_process"); const fs = require("fs"); const os = require("os"); const path = require("path"

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/windows-wsl-bridge.js

high Shell/command execution in server code (src/agent_runner.py)MTC-SRC-002

In the server's implementation (`src/agent_runner.py:856`): 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: try: result = subprocess.run(cmd, env=launch_env, cwd=str(cwd_path)) finally: duration_ms = int((t

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 src/agent_runner.py

high Shell/command execution in server code (src/auto_update.py)MTC-SRC-002

In the server's implementation (`src/auto_update.py:605`): 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: try: result = subprocess.run( ["git", "rev-parse", "--is-inside-work-tree"], cwd=str(R

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 src/auto_update.py

high Shell/command execution in server code (src/backup_retention.py)MTC-SRC-002

In the server's implementation (`src/backup_retention.py:42`): 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: -technical") proc = subprocess.run(command, capture_output=True, text=True, timeout=120) try: payload =

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 src/backup_retention.py

high Shell/command execution in server code (src/causal_graph.py)MTC-SRC-002

In the server's implementation (`src/causal_graph.py:200`): 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: eturn True result = subprocess.run( ["git", "cat-file", "-e", f"{clean}^{{commit}}"], cwd=repo_root,

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 src/causal_graph.py

high Shell/command execution in server code (src/cli.py)MTC-SRC-002

In the server's implementation (`src/cli.py:138`): 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: try: result = subprocess.run( ["npm", "view", LATEST_NPM_PACKAGE, "version"], capture_

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 src/cli.py

medium Untrusted input concatenated into a command sink (bin/nexo-brain.js)MTC-SRC-009

In the server's implementation (`bin/nexo-brain.js:2967`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: t); try { execSync( `launchctl bootout gui/$(id -u) "${plistPath}" 2>/dev/null; launchctl bootst

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/nexo-brain.js

medium Dynamic module load from a non-literal (src/auto_update.py)MTC-SRC-005

In the server's implementation (`src/auto_update.py:1184`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: y: module = __import__(module_name) except Exception: missing.append(state_key)

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 src/auto_update.py

medium Dynamic module load from a non-literal (src/classifier_local.py)MTC-SRC-005

In the server's implementation (`src/classifier_local.py:58`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: try: __import__(module_name) except Exception: return False return True def

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 src/classifier_local.py

low Shell/command execution in packaging/dev tooling (bin/postinstall.js)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`bin/postinstall.js:11`): 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: ecFileSync } = require("child_process"); const NEXO_HOME = process.env.NEXO_HOME || path.join(require("os").homedir(),

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/postinstall.js

low Package runs install-time scripts (postinstall)MTC-SUP-010

"nexo-brain" 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: node bin/postinstall.js

Fix: Review the scripts; install with --ignore-scripts where possible and vet what they do.

Location: package nexo-brain

Tools 170

Each tool and what it can reach — statically extracted from the published source.

  • nexo_answerno sensitive capability
  • nexo_api_callno sensitive capability
  • nexo_askno sensitive capability
  • nexo_automation_reconcileno sensitive capability
  • nexo_automation_supervisorno sensitive capability
  • nexo_capability_explainno sensitive capability
  • nexo_card_matchno sensitive capability
  • nexo_check_answerno sensitive capability
  • nexo_checkpoint_readno sensitive capability
  • nexo_checkpoint_saveno sensitive capability
Show 160 more tools ↓
  • nexo_closure_closeno sensitive capability
  • nexo_closure_item_getno sensitive capability
  • nexo_closure_linkno sensitive capability
  • nexo_closure_nextno sensitive capability
  • nexo_closure_snapshotno sensitive capability
  • nexo_closure_statusno sensitive capability
  • nexo_closure_triageno sensitive capability
  • nexo_closure_verifyno sensitive capability
  • nexo_cognitive_control_observatoryno sensitive capability
  • nexo_confidence_checkno sensitive capability
  • nexo_context_packetno sensitive capability
  • nexo_context_routerno sensitive capability
  • nexo_continuity_auditno sensitive capability
  • nexo_continuity_compaction_eventno sensitive capability
  • nexo_continuity_resume_bundleno sensitive capability
  • nexo_continuity_snapshot_readno sensitive capability
  • nexo_continuity_snapshot_writeno sensitive capability
  • nexo_cortex_checkno sensitive capability
  • nexo_cortex_decideno sensitive capability
  • nexo_create_app_tokenno sensitive capability
  • nexo_credential_createno sensitive capability
  • nexo_credential_deleteno sensitive capability
  • nexo_credential_getno sensitive capability
  • nexo_credential_listno sensitive capability
  • nexo_credential_updateno sensitive capability
  • nexo_drive_actno sensitive capability
  • nexo_drive_dismissno sensitive capability
  • nexo_drive_reinforceno sensitive capability
  • nexo_drive_signalsno sensitive capability
  • nexo_embedding_migration_statusno sensitive capability
  • nexo_entity_dossierno sensitive capability
  • nexo_evidence_recordno sensitive capability
  • nexo_evidence_searchno sensitive capability
  • nexo_filesno sensitive capability
  • nexo_followup_completeno sensitive capability
  • nexo_followup_createno sensitive capability
  • nexo_followup_deleteno sensitive capability
  • nexo_followup_getno sensitive capability
  • nexo_followup_lifecycleno sensitive capability
  • nexo_followup_noteno sensitive capability
  • nexo_followup_restoreno sensitive capability
  • nexo_followup_updateno sensitive capability
  • nexo_goal_getno sensitive capability
  • nexo_goal_listno sensitive capability
  • nexo_goal_openno sensitive capability
  • nexo_goal_updateno sensitive capability
  • nexo_guard_checkno sensitive capability
  • nexo_guardian_rule_overrideno sensitive capability
  • nexo_heartbeatno sensitive capability
  • nexo_hook_runsno sensitive capability
  • nexo_hot_context_listno sensitive capability
  • nexo_index_add_dirno sensitive capability
  • nexo_index_dirsno sensitive capability
  • nexo_index_remove_dirno sensitive capability
  • nexo_intraday_memory_cycleno sensitive capability
  • nexo_learning_addno sensitive capability
  • nexo_learning_apply_retroactivelyno sensitive capability
  • nexo_learning_deleteno sensitive capability
  • nexo_learning_listno sensitive capability
  • nexo_learning_qualityno sensitive capability
  • nexo_learning_resolve_candidateno sensitive capability
  • nexo_learning_searchno sensitive capability
  • nexo_learning_updateno sensitive capability
  • nexo_local_asset_getno sensitive capability
  • nexo_local_asset_neighborsno sensitive capability
  • nexo_local_contextno sensitive capability
  • nexo_local_index_controlno sensitive capability
  • nexo_local_index_diagnostics_tailno sensitive capability
  • nexo_local_index_exclusionsno sensitive capability
  • nexo_local_index_filetypesno sensitive capability
  • nexo_local_index_migrate_roots_v2no sensitive capability
  • nexo_local_index_modelsno sensitive capability
  • nexo_local_index_purgeno sensitive capability
  • nexo_local_index_rootsno sensitive capability
  • nexo_local_index_service_configno sensitive capability
  • nexo_local_index_statusno sensitive capability
  • nexo_managed_mcp_statusno sensitive capability
  • nexo_mcp_write_queue_statusno sensitive capability
  • nexo_memory_answerno sensitive capability
  • nexo_memory_backfillno sensitive capability
  • nexo_memory_event_listno sensitive capability
  • nexo_memory_event_statsno sensitive capability
  • nexo_memory_forgetno sensitive capability
  • nexo_memory_healthno sensitive capability
  • nexo_memory_maintenanceno sensitive capability
  • nexo_memory_observation_listno sensitive capability
  • nexo_memory_observation_processno sensitive capability
  • nexo_memory_observation_statsno sensitive capability
  • nexo_memory_searchno sensitive capability
  • nexo_memory_timelineno sensitive capability
  • nexo_menuno sensitive capability
  • nexo_opportunity_feedbackno sensitive capability
  • nexo_opportunity_getno sensitive capability
  • nexo_opportunity_queueno sensitive capability
  • nexo_opportunity_refreshno sensitive capability
  • nexo_opportunity_suppressno sensitive capability
  • nexo_plugin_listno sensitive capability
  • nexo_plugin_loadno sensitive capability
  • nexo_plugin_removeno sensitive capability
  • nexo_pre_action_contextno sensitive capability
  • nexo_pre_answer_routeno sensitive capability
  • nexo_product_answerno sensitive capability
  • nexo_product_capabilitiesno sensitive capability
  • nexo_product_knowledge_validateno sensitive capability
  • nexo_product_surface_statusno sensitive capability
  • nexo_protocol_debt_resolveno sensitive capability
  • nexo_recent_contextno sensitive capability
  • nexo_recent_context_captureno sensitive capability
  • nexo_recent_context_resolveno sensitive capability
  • nexo_reindexno sensitive capability
  • nexo_reminder_completeno sensitive capability
  • nexo_reminder_createno sensitive capability
  • nexo_reminder_deleteno sensitive capability
  • nexo_reminder_getno sensitive capability
  • nexo_reminder_noteno sensitive capability
  • nexo_reminder_restoreno sensitive capability
  • nexo_reminder_updateno sensitive capability
  • nexo_remindersno sensitive capability
  • nexo_runtime_service_statusno sensitive capability
  • nexo_saved_not_used_auditno sensitive capability
  • nexo_sendno sensitive capability
  • nexo_session_compliance_stateno sensitive capability
  • nexo_session_diary_readno sensitive capability
  • nexo_session_diary_writeno sensitive capability
  • nexo_session_export_bundleno sensitive capability
  • nexo_session_log_closeno sensitive capability
  • nexo_session_log_createno sensitive capability
  • nexo_session_portable_contextno sensitive capability
  • nexo_skill_matchno sensitive capability
  • nexo_smart_startupno sensitive capability
  • nexo_startupno sensitive capability
  • nexo_statusno sensitive capability
  • nexo_stopno sensitive capability
  • nexo_support_ticket_closeno sensitive capability
  • nexo_support_ticket_createno sensitive capability
  • nexo_support_ticket_listno sensitive capability
  • nexo_support_ticket_messageno sensitive capability
  • nexo_support_ticket_readno sensitive capability
  • nexo_support_ticket_reopenno sensitive capability
  • nexo_system_catalogno sensitive capability
  • nexo_task_acknowledge_guardno sensitive capability
  • nexo_task_closeno sensitive capability
  • nexo_task_frequencyno sensitive capability
  • nexo_task_listno sensitive capability
  • nexo_task_logno sensitive capability
  • nexo_task_openno sensitive capability
  • nexo_tool_explainno sensitive capability
  • nexo_trackno sensitive capability
  • nexo_transcript_readno sensitive capability
  • nexo_transcript_recentno sensitive capability
  • nexo_transcript_searchno sensitive capability
  • nexo_untrackno sensitive capability
  • nexo_workflow_compensationno sensitive capability
  • nexo_workflow_getno sensitive capability
  • nexo_workflow_handoffno sensitive capability
  • nexo_workflow_listno sensitive capability
  • nexo_workflow_openno sensitive capability
  • nexo_workflow_replayno sensitive capability
  • nexo_workflow_resumeno sensitive capability
  • nexo_workflow_updateno sensitive capability

What this scan could not see

Versions 1

Scan 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.

VersionScoreFindingsEngineScanned
v7.38.7 latest B 86/100 16 1.13.0 2026-09-07

Embed this score

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.

MCP Trust Score: B · 86/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/nexo-brain/badge.svg)](https://mcptrustchecker.com/registry/nexo-brain)
HTML
<a href="https://mcptrustchecker.com/registry/nexo-brain"><img src="https://mcptrustchecker.com/registry/nexo-brain/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/nexo-brain/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

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 nexo-brain --online

Use the free API → How scoring works

More in AI, Memory & Reasoning