infranodus-mcp-server (infranodus/mcp-server-infranodus) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it yet. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Caution
67/100

infranodus-mcp-server

InfraNodus MCP server - A Model Context Protocol server for network thinking and graph analysis

→ infranodus/mcp-server-infranodus· npm: infranodus-mcp-server· listed on official

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

infranodus

Source: Official · also listed on npm

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Officialnot scored herenpmscored separately

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
⚠️
Known vulnerabilities in dependencies: 3 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 3 credentials: INFRANODUS_API_KEY, JWT_SECRET, KEYWORDGRAPH_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies3 high1 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

high@modelcontextprotocol/sdk@1.18.2GHSA-345p-7cg4-v4c7

@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse

high@modelcontextprotocol/sdk@1.18.2GHSA-8r9q-7v3j-jr4g

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

high@modelcontextprotocol/sdk@1.18.2GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

lowuuid@11.1.0GHSA-w5hq-g745-h8pq

uuid: Missing buffer bounds check in v3/v5/v6 when buf is provided

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configBRAND
configCORS_ORIGIN
configFLY_APP_NAME
🔐 secretINFRANODUS_API_KEYNote: you can leave the empty in which case you can make 70 free requests after which you will hit quota and will need to add your API key.
configINFRANODUS_FEEDBACKSet =0 to remove the tool (and the one-line nudge appended to workflow-ending results) from the server
configINFRANODUS_LEARNINGS_Also available as the save-learnings prompt in clients that expose MCP prompts. Set =0 to remove these three tools from the server entirely (see [Project learnings](#project-learnings))._
🔐 secretJWT_SECRET
🔐 secretKEYWORDGRAPH_API_KEY
configMCPCAT_ANONYMOUSThe report contains short paraphrases of what you were working on (capped at 200 characters), the same policy as the prompts InfraNodus already logs; =1 skips the per-user log entirely
configMCP_SOURCE
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// quality suggestions

Secrets not logged

1 secret value sent to log

Redact or omit secret values from log output.

Production dependencies are patched

0 critical, 3 high severity in production deps — @modelcontextprotocol/sdk@1.18.2 (high), @modelcontextprotocol/sdk@1.18.2 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 2 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/infranodus/mcp-server-infranodus?variant=verified)](https://m8ven.ai/mcp/infranodus/mcp-server-infranodus)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: b3be2cc023cd959399b8f77e96833fa53a110bd5
code hash: c897a9be23800e4497e3ff18db2ae733d145fdb73786101514670f57e5f2fdc0
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client