Skills/PyPI/neo-cortex-mcp

neo-cortex-mcp@5.23.11

VERIFIED· not started

Publisher claims: "Neo Memory Cortex — Standalone Memory Server" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher pypi · publishing for 723 daysInstalls 368Last detonated 36 h ago
$claude mcp add neo-cortex-mcp -- uvx neo-cortex-mcp
WatchReport an issue

Coverage

Not started: dependency install failed; the server itself was not observed.
Tested
the dependency install step · every file read, file written and host contacted by what ran
Not tested
server startup · the tool list · tool behavior

What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
GEMINI_API_KEYJINA_API_KEYOPENAI_API_KEYConfiguration, not credentials: ANTHROPIC_MODEL, CLASSIFIER_PROVIDER, CONSOLIDATION_MAX_GROUP_SIZE, CONSOLIDATION_SIMILARITY_THRESHOLD, CONVERSATION_DB_PATH, CORTEX_COLLECTION, CORTEX_DATA_DIR, CORTEX_DB_PATH, DIGESTOR_BUDGET, DIGESTOR_BUDGET_MAX, DIGESTOR_BUDGET_THRESHOLD, DISTILLER_PROVIDER, GEMINI_MODEL, GROQ_MODEL, JINA_DIMENSIONS, JINA_MODEL, LLM_BASE_URL, LLM_MODEL, LLM_PROVIDER, MEMORY_HUB_URL, MEMORY_INDEX_DB_PATH, OPENAI_MODEL, PROJECT_NAMES, SSLKEYLOGFILE, XAI_MODEL, ZAI_MODEL
Where it talks to
no vendor host named in the codeAlso jina.ai, groq.com, jsdelivr.net, z.ai, x.ai — not the publisher's domain; check what for before connecting.
What the honeypot saw
no credential files read · no network
What we could not test
server startup · the tool list · tool behavior

Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names jina.ai, groq.com, jsdelivr.net, z.ai, x.ai as well as its own vendor. The guard injects GEMINI_API_KEY, JINA_API_KEY, OPENAI_API_KEY only into requests to the host you bind (and its subdomains) and refuses the rest.

$vet-skills run --net declared -- uvx neo-cortex-mcp

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-13 and scored it 93/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 0 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.1sprocessdependency install exit 1 ·
0.1sclaimednot started: dependency install failed (exit 1); the server itself was not observed
0.1sprocessscript backend runs setup only
0.1sprocessno install scripts to re-run

Static findings

MEDIUM
Python subprocess execution detectedtests/test_dashboard.py:321 · Python subprocess execution detectedresult = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05

No other findings across 14,371 lines in 81 files.

Cost to the agent

Instructions loaded
≈49 tok
1 file · 81 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

No advisories in OSV for neo-cortex-mcp@5.23.11 as of 33 h ago. This is the package itself, not its dependencies.