Skills/PyPI/neruva-mcp

neruva-mcp@0.69.2

VERIFIED· not started

Publisher claims: "Verified skills for AI agents. Find, install and run helper code that a program has checked on cases it never saw, and build your own: every skill ships the exact checker that proved it, so you can re-run the evidence yourself instead of taking our word for it. Free to read and install, no key and no account. Works with any model that can call a function, from a frontier API to a 0.6B running on your laptop." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher clouthier-simulation-labs-info · publishing for 185 daysInstalls 388Last detonated 35 h ago
$claude mcp add neruva-mcp -- uvx neruva-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
ANTHROPIC_API_KEYNERUVA_API_KEYConfiguration, not credentials: NERUVA_AUTO_RECORD, NERUVA_HOME, NERUVA_MEMORY, NERUVA_NAMESPACE, NERUVA_PRINCIPLES_NS, NERUVA_URL
Where it talks to
neruva.io (its own)
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. It asks for ANTHROPIC_API_KEY, NERUVA_API_KEY and talks to neruva.io. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.

$vet-skills run --secrets ANTHROPIC_API_KEY=neruva.io,NERUVA_API_KEY=neruva.io -- uvx neruva-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 91/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 detectedsrc/neruva_mcp/forge.py:226 · Python subprocess execution detectedp = subprocess.run([sys.executable, str(script)], capture_output=True, text=True,Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05

No other findings across 5,635 lines in 20 files.

Cost to the agent

Instructions loaded
≈139 tok
1 file · 20 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 neruva-mcp@0.69.2 as of 33 h ago. This is the package itself, not its dependencies.