supcon-international/node-red-mcp-server (supcon-international/node-red-mcp-server) is an MCP server listed on the M8ven Trust Index. It scores 6 out of 100, grade F. It declares 27 tools. No publisher has claimed this listing.

F
Warning
6/100

supcon-international/node-red-mcp-server

Model Context Protocol (MCP) server for interacting with Node-RED

supcon-international/node-red-mcp-server· npm: @supcon-international/node-red-mcp-server· listed on glama

Warning. Serious findings were identified. Review the full report before connecting. 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

supcon-international

Source: Glama · 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 →

Install from

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
🚨
Secret credentials may flow to a network call
1 flow detected: NODE_RED_TOKEN. We can’t prove the destination matches the brand the credential belongs to.
⚠️
Tool descriptions don’t match what handlers do
4 tools describe read intent but their handlers mutate — list-backups (line 235: fs.mkdir(backupDir, { recursive: true })); get-backup-flows (line 235: fs.mkdir(backupDir, { recursive: true })); backup-health (line 235: fs.mkdir(backupDir, { recursive: true }))
⚠️
Known vulnerabilities in dependencies: 15 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
// tools this server exposes27 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

backup-flows

Create a named backup of current Node-RED flows with optional reason

list-backups

List all available flow backups with details

get-backup-flows

Get the specific flows content from a backup by name

backup-health

Check backup system health and provide recommendations

get-flows

Retrieves the complete list of flows from the Node-RED instance.

update-flows

Updates the entire flow configuration of the Node-RED instance. Args: flowsJson (e.g.'[{type: 'tab', id: '396c2376c693d', label: 'Sheet 1'}]')

get-flow

Retrieves the configuration of a specific flow by its ID. Args: id (e.g.'396c237c693dc')

update-flow

Updates the configuration of a specific flow by its id. Args: id (e.g.'396c237c693dc') flowJson (e.g.'{id: '91ad456e52b8', label: 'Sheet 1', nodes: [], configs: []}')

list-tabs

Lists all flow tabs (workspaces) in the Node-RED instance.

create-flow

Creates a new flow in the Node-RED instance. Args: flowJson (e.g.'{id: '91ad456e52b8', label: 'Sheet 1', nodes: [], configs: []}')

delete-flow

Deletes a specific flow from the Node-RED instance by its ID. Args: id (e.g.'396c237c693dc')

get-flows-state

Retrieves the current deployment state of all flows in the Node-RED instance. This tool returns the runtime state of the flows, including their active status.

set-flows-state

Updates the deployment state of all flows in the Node-RED instance.

get-flows-formatted

Retrieves a human-readable, formatted list of all flows in the Node-RED instance.

visualize-flows

Generates a graph-like visualization of the flows in the Node-RED instance.

inject

Triggers an inject node in the Node-RED instance by its ID. This tool simulates an input event for the specified inject node.

get-available-nodes

Retrieves a list of all installed nodes their information (name,help,module) in the Node-RED instance.

get-node-detailed-info

Retrieves source code about a specific node module by its name. Args: module (e.g.'node-red/inject')

get-node-set-detailed-info

Retrieves source code about a specific node module by its name. Args: module (e.g.'@supcon-international/node-red-function-gpt-with-memory') set (e.g.'function-gpt')

install-node-module

Install a specific node module in the Node-RED instance. Args: module (e.g.'node-red-dashboard')

toggle-node-module

Enables or disables a specific node module in the Node-RED instance. Args: module (e.g.'node-red/inject') enabled (e.g.'true')

toggle-node-module-set

Enables or disables a specific node module set in the Node-RED instance. Args: module (e.g.'@supcon-international/node-red-function-gpt-with-memory') set (e.g.'function-gpt') enabled (e.g.'true')

find-nodes-by-type

Searches for nodes in the Node-RED instance by their type. Args: nodeType (e.g.'inject')

search-nodes

Searches for nodes in the Node-RED instance by a query string, optionally filtering by a specific property. Args: query (e.g.'inject') property (e.g.'type') (optional)

get-settings

Retrieves the runtime settings of the Node-RED instance. This tool returns the current configuration settings of the Node-RED server.

get-diagnostics

Retrieves diagnostic information from the Node-RED instance. This tool returns detailed runtime diagnostics, including system status and performance metrics.

api-help

Displays a help table of all available Node-RED Admin API methods, including their implementation status in the MCP server. This tool provides a quick reference for available API endpoints.

// known CVEs in dependencies15 high5 medium10 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.11.0GHSA-345p-7cg4-v4c7

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

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

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

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

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

highaxios@1.9.0GHSA-35jp-ww65-95wh

axios Vulnerable to Full Man-in-the-Middle via Prototype Pollution Gadget in `config.proxy`

highaxios@1.9.0GHSA-3g43-6gmg-66jw

axios Vulnerable to Credential Theft and Response Hijacking via Prototype Pollution Gadget in Config Merge

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.
configMCP_BACKUP_PATHCustom backup directory path
configMCP_MAX_BACKUPSMaximum number of backups to keep
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

27/27 tools missing one or more hints — backup-flows (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list-backups (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get-backup-flows (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +24 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Destructive tools are labelled

1 tool perform destructive updates without destructiveHint — backup-flows deletes at line 349 (fs.unlink(path.join(backupDir, backup.filename)))

Add destructiveHint:true to any tool whose handler calls .delete(), .upsert(), .update(), unlink, rm, DELETE, DROP, REPLACE INTO, or any operation that overwrites existing data.

Descriptions match behaviour

4 tools describe read intent but their handlers mutate — list-backups (line 235: fs.mkdir(backupDir, { recursive: true })); get-backup-flows (line 235: fs.mkdir(backupDir, { recursive: true })); backup-health (line 235: fs.mkdir(backupDir, { recursive: true }))

Rename the tool, rewrite the description, or move the side-effect into a separate clearly-named tool.

Tool inputs are validated

24/27 tool handlers declare input schemas (89%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tests exist

No test files found

Add tests that exercise each declared tool.

Production dependencies are patched

0 critical, 15 high severity in production deps — @modelcontextprotocol/sdk@1.11.0 (high), @modelcontextprotocol/sdk@1.11.0 (high)

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

Tool description accuracy

4 tools have description/behavior mismatches: list-backups: description implies read-only but handler writes/deletes/executes; get-backup-flows: description implies read-only but handler writes/deletes/executes; backup-health: description implies read-only but handler writes/deletes/executes

Update tool descriptions to accurately reflect all capabilities — especially write, delete, or execute operations.

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 8 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/supcon-international/node-red-mcp-server?variant=verified)](https://m8ven.ai/mcp/supcon-international/node-red-mcp-server)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: b95822768fd6e0c7d06198da56464620c8dc0677
code hash: 995054bd795f3f4cfe107c9eec089fc405084effef0c464bd3eb028f2a6edce8
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