modelrisk-mcp@0.4.5
VERIFIED· not startedPublisher claims: "Open MCP server bridging Anthropic Claude (and any MCP-compatible client) with the ModelRisk Excel add-in." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
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
MODELRISK_MCP_TOKENConfiguration, not credentials: MODELRISK_AUTO_LAUNCH, MODELRISK_MCP_READ_ONLY, MRENGINE_NATIVE_DLL, MRSERVICE_ACTIVATION_KEY, MRSERVICE_ACTIVATION_KEY1, MRSERVICE_ACTIVATION_KEY2, MRSERVICE_DISABLE_BUNDLED_KEY, MRSERVICE_VARID_TIMEOUT_S- Where it talks to
- no vendor host named in the code
- 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 MODELRISK_MCP_TOKEN and talks to its vendor. 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.
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-11 and scored it 85/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 deviationsStatic findings
subprocess.run([npx, "-y", _MCPB_PKG, "validate", str(stage / "manifest.json")], check=True)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.subprocess.run([npx, "-y", _MCPB_PKG, "pack", str(stage), str(out)], check=True)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.`npx` — which validates the manifest during packing. If node/npx isn'tFix: Pin versions and sources; vendor anything fetched at install time.forcibly kill it (it's blocked in C), so on timeout it leaks untilFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.npx = shutil.which("npx")Fix: Pin versions and sources; vendor anything fetched at install time.# Before any event loop exists. Windows can kill the loop's self-pipe onFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.proc = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.if not (npx and _pack_with_cli(npx, stage, out)):Fix: Pin versions and sources; vendor anything fetched at install time.proc = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.done = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.Cost to the agent
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 modelrisk-mcp@0.4.5 as of 3d ago. This is the package itself, not its dependencies.