cnc-fluidnc-mcp (WhitneyDesignLabs/cnc-fluidnc-mcp) is an MCP server listed on the M8ven Trust Index. It scores 53 out of 100, grade D. It declares 27 tools. No publisher has claimed this listing.

D
Caution
53/100

cnc-fluidnc-mcp

An MCP server that enables Claude to control CNC routers running FluidNC firmware using natural language. It provides 27 tools for monitoring status, jogging axes, executing G-code, and managing SD card files and machine configurations.

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

WhitneyDesignLabs

Source: Glama

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
⚠️
Tool descriptions don’t match what handlers do
3 tools describe read intent but their handlers mutate — list_backups (line 12: mkdir(dir, { recursive: true })); list_macros (line 11: mkdir(dir, { recursive: true })); get_macro (line 11: mkdir(dir, { recursive: true }))
⚠️
Known vulnerabilities in dependencies: 1 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.
// 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_config

Save the current FluidNC settings and work offsets to a timestamped backup file.

list_backups

List all saved configuration backups.

restore_config

Restore machine settings from a backup. Defaults to dry-run mode showing what would change. Requires confirm=true to actually apply.

send_gcode

Send a single G-code or Grbl command to the CNC machine. Safety level is auto-classified. DANGEROUS/CRITICAL commands require confirm=true.

run_gcode_program

Send a multi-line G-code program to the machine, one line at a time. Requires confirm=true.

spindle_control

Control the spindle: turn on (CW/CCW with speed) or off. Turning on requires confirm=true.

feed_hold

Pause machine motion immediately (feed hold). Sends '!' realtime command.

cycle_resume

Resume machine motion after a feed hold. Sends '~' realtime command.

soft_reset

Emergency stop — soft reset the controller (0x18). Stops all motion and spindle immediately. Requires confirm=true.

list_macros

List all saved CNC macros.

get_macro

View the contents of a saved macro.

save_macro

Create or update a macro. Parameters can be substituted in G-code using {param_name} syntax.

run_macro

Execute a saved macro. Shows preview first; set confirm=true to run. Parameters can override defaults.

delete_macro

Delete a saved macro. Requires confirm=true.

jog

Jog the CNC machine along an axis by a specified distance at a given feed rate. Uses incremental mode ($J=G91).

home_axes

Run homing cycle. Homes all axes by default, or specify individual axes.

unlock_machine

Clear alarm state and unlock the machine ($X). Use after an alarm condition.

set_zero

Set the work coordinate zero for specified axes at the current position (G10 L20 P1). If no axes specified, sets all axes to zero.

go_to_zero

Move to work coordinate zero. Raises Z to safe height first, then moves XY, then lowers Z.

list_sd_files

List files and directories on the CNC controller's SD card.

upload_to_sd

Upload a file to the CNC controller's SD card.

delete_sd_file

Delete a file from the CNC controller's SD card. Requires confirm=true.

run_sd_file

Run a G-code file from the CNC controller's SD card. Requires confirm=true.

get_machine_status

Get real-time CNC machine status: position, state, feed rate, spindle speed, and overrides

get_system_info

Get FluidNC system information: firmware version, CPU, memory, WiFi, SD card status

get_machine_settings

Get all FluidNC/Grbl machine settings. Optionally filter by keyword (e.g. 'accel', 'steps', 'max_rate').

get_gcode_state

Get active G-code modal state: motion mode, coordinate system, units, distance mode, spindle, coolant

// known CVEs in dependencies1 high1 low

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

highws@8.20.0GHSA-96hv-2xvq-fx4p

ws: Memory exhaustion DoS from tiny fragments and data chunks

ws: Uninitialized memory disclosure

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.
configFLUIDNC_HOST"": "http://your-controller.local"
// 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_config (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_backups (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); restore_config (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 — delete_macro deletes at line 208 (unlink(path))

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

3 tools describe read intent but their handlers mutate — list_backups (line 12: mkdir(dir, { recursive: true })); list_macros (line 11: mkdir(dir, { recursive: true })); get_macro (line 11: mkdir(dir, { recursive: true }))

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

Tool inputs are validated

19/27 tool handlers declare input schemas (70%)

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

Tool handlers catch errors

Only 8/27 tool handlers wrap calls in try/catch (30%)

Wrap each tool handler body in try/catch and return a structured error response.

Tests exist

No test files found

Add tests that exercise each declared tool.

Production dependencies are patched

0 critical, 1 high severity in production deps — ws@8.20.0 (high), ws@8.20.0 (low)

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

Tool description accuracy

3 tools have description/behavior mismatches: list_backups: description implies read-only but handler writes/deletes/executes; list_macros: description implies read-only but handler writes/deletes/executes; get_macro: 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 9 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/whitneydesignlabs/cnc-fluidnc-mcp?variant=verified)](https://m8ven.ai/mcp/whitneydesignlabs/cnc-fluidnc-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: a26c810a4f8a89301084c38236754290e555fb6e
code hash: c25d037b6cf5a2fc6a9653ffa41dfc79c9440a6b4847c0e61b0b60cb8ef84445
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