infranodus-mcp-server@1.11.0
VERIFIED· not startedPublisher claims: "InfraNodus MCP server - A Model Context Protocol server for network thinking and graph analysis" 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
INFRANODUS_API_KEYJWT_SECRETKEYWORDGRAPH_API_KEYMCP_SIGNIN_LOG_SECRETConfiguration, not credentials: BRAND, CORS_ORIGIN, FLY_APP_NAME, INFRANODUS_DELETE, INFRANODUS_FEEDBACK, INFRANODUS_LEARNINGS, MCP_SOURCE, MCPCAT_ANONYMOUS, OPENAI_APPS_CHALLENGE, OPENAI_PATH- Where it talks to
- infranodus.com (its own)Also keywordgraph.com — not the publisher's domain; check what for before connecting.
- What we saw when it ran
- 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 keywordgraph.com as well as its own vendor. The guard injects INFRANODUS_API_KEY, JWT_SECRET, KEYWORDGRAPH_API_KEY, MCP_SIGNIN_LOG_SECRET only into requests to infranodus.com (and its subdomains) and refuses the rest.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
What changed since 1.9.8
vet-skills diff infranodus-mcp-server 1.9.8 1.11.0In the sandbox, this version reached for nothing 1.9.8 did not. Compared from the two recorded runs, not from source.
1.9.8 was not run in the sandbox (install failed); the comparison covers what static analysis recorded only.
The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.
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-19 and scored it 80/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 · 2 s · 2 scenarios · 0 deviationsStatic findings
// STDIO/npx mode: resolve identity from the API keyFix: Pin versions and sources; vendor anything fetched at install time.<input type="password" id="api_key" name="api_key" required placeholder="Enter your API key">Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.- Compatible with ChatGPT Deep Research mode via Developer Mode > ConnectorsFix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.// Bakes in BRAND so `npx infranodus-mcp-server` runs as InfraNodus withoutFix: Pin versions and sources; vendor anything fetched at install time.console.log(`[MCP] Handling POST / as MCP request`);Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why."build": "npx @smithery/cli build",Fix: Pin versions and sources; vendor anything fetched at install time.console.log(`[MCP:auto-init] Sending synthetic "${method}" request`);Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.console.log(`[SSE] POST /message for session ${sessionId}`);Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.console.log(` - OAuth token: POST http://localhost:${PORT}/oauth/token`);Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why."dev": "npx @smithery/cli dev",Fix: Pin versions and sources; vendor anything fetched at install time.- Compatible with ChatGPT Deep Research mode via Developer Mode > ConnectorsFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.- Can be used in ChatGPT Deep Research mode via Developer Mode > ConnectorsFix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.- Can be used in ChatGPT Deep Research mode via Developer Mode > ConnectorsFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.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 infranodus-mcp-server@1.11.0 as of 8 h ago. This is the package itself, not its dependencies.