midas-nx-mcp@0.3.4
VERIFIED· not startedPublisher claims: "Local MCP server for MIDAS Gen NX / Civil NX, built on midas-nx - not an official MIDAS IT product" 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
Code inventory arrives with this version's next honeypot run.- It will ask for
- unknown until the next run
- Where it talks to
- unknown until the next run
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Not enough was observed to say yet. Not started: dependency install failed; the server itself was not observed. This version's code has not been inventoried for credentials and hosts either; both arrive with its next honeypot run (popular servers first). `vet-skills try midas-nx-mcp` runs it now and prints the full answer.
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-07 and scored it 83/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
return PROJECT_ROOT / ".env"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.environment variables. Run from a checkout, the project's .env is read too,Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."""The checkout's .env; None when installed, where PROJECT_ROOT is site-packages' parent."""Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."""Settings from environment variables, or from a source checkout's .env.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.SETTINGS = set(re.findall(r"\b(MIDAS_[A-Z_]+)\b", (ROOT / ".env.example").read_text("utf-8")))Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.(tmp_path / ".env").write_text("MIDAS_MAPI_KEY_GEN=from-file\n", encoding="utf-8")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."""An environment variable wins over .env.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.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 midas-nx-mcp@0.3.4 as of 7d ago. This is the package itself, not its dependencies.