step2gcode
REMOTE · WWW.STEP2GCODE.COM · 2 COMPONENTS
Turn STEP, DXF and SVG files into CNC milling and laser G-code for GRBL, LinuxCNC, Mach3 and more.
Available components
Last scanned (18 hours ago)
Scores higher than 59% of remote servers
Reachable. Last reached 21 Nov 2026.
Category IoT and Hardware
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3321 tokens (~276/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 88% of tool parameters carry a description.Partial
- Structured output schemas are declared (17% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Nov 26 0
- Tool “get_step_download_link” rewrote its description, which is the text the model reads security
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- First check of Tool coverage: 17 functional
- New tool “fetch” functional
- New tool “search” functional
- 14 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 13 Nov 26 69
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://www.step2gcode.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=step2gcode.com | CN=YE1,O=Let's Encrypt,C=US | 15 Nov 2026 | 13 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 638964a2e85d7af29e8d9f59c370035af1c |
| SANs: step2gcode.com, www.step2gcode.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.step2gcode.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| step2gcode.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; img-src 'self' data: https:; font-src 'self' data: https://fonts.gstatic.com; connect-src 'self' blob:; frame-ancestors 'self'; |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.step2gcode.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://www.step2gcode.com/api/mcp | HTTPS enforced | 301 | https://www.step2gcode.com/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_upload ~186
Check whether the user finished the browser upload. Returns the file_id once ready. Free. NEXT STEP - do not generate yet. Ask the user: 1. Which material? Offer the presets (wood, hardwood, plywood, acrylic, aluminum, steel, brass). If theirs is not among them, pick the closest preset AND set spindle_speed, feed_rate, plunge_rate and step_down yourself from known cutting data for that material and cutter. 2. Which cutter diameters do they actually own? Recommend one from that list: it must fit the smallest inner radius of the part, and a smaller cutter means longer machining time. If you cannot judge the geometry yet, say so and suggest generating once to see the dimensions. 3. Is the part cut all the way through? Then recommend holding_tabs so it does not come loose on the last pass.
| Name | Type | Req | Description |
|---|---|---|---|
| upload_id | string | yes | – |
No output schema declared.
No examples provided.
convert_mesh_to_step ~253
Turn an uploaded STL or 3MF mesh back into a STEP solid with exact surfaces - planes, cylinders, cones and fillets instead of triangles, intersected into real edges. Free; only the download of the finished file is charged. Use this when the user has a mesh and needs CAD geometry: a hole becomes a cylinder with a diameter again, a chamfer a cone with an angle, so the part can be dimensioned, modified and machined. Typical case: the CAD source is gone and the mesh is all that is left. The answer states the largest measured deviation between the built solid and the mesh, in millimetres - always pass that number on to the user, it is what tells them whether the result is accurate enough for their part. Parts made of freeform surfaces and raw 3D scans are rejected with a reason instead of being badly reconstructed. Upload the mesh the same way as any other file (curl to /api/upload, upload_file_content or create_upload_link), then pass the file_id here. The resulting STEP file can go straight into generate_gcode afterwards.
| Name | Type | Req | Description |
|---|---|---|---|
| file_id | string | yes | file_id of an uploaded .stl or .3mf mesh |
No output schema declared.
No examples provided.
create_upload_link ~146
Create a short-lived link the user opens in their browser to upload a CAD file (STEP, DXF or SVG). Returns the link and an upload_id. Poll check_upload with the upload_id until it reports a file_id, then call generate_gcode. Free. Before using this, check whether you can run shell commands. If you can, do not send the user to the browser: compress the file locally and pass it to upload_file_content (the compression is detected by itself). That works inside sandboxes without network access, which is the common case - a direct curl upload fails there with a proxy error. The response of this tool spells out all three routes in order.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
fetch ~37
Read the full text of one page found with search, by its id. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The id from a search result |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| text | string | yes | – |
| title | string | yes | – |
| url | string | yes | – |
No examples provided.
generate_gcode ~874
Start G-code generation for an uploaded file and wait for the result. Most jobs finish within the wait, so the answer usually already carries the part dimensions and hole diameters - no polling needed. Only if it says the job is still running, call get_job_status once after a few seconds. Free - only the download is charged. BEFORE CALLING THIS, ask the user about the settings you cannot infer from the file. Two of them change the result substantially and are wrong by default more often than not: - material: drives spindle speed, feed rates and depth per pass. Aluminium cut with wood settings breaks cutters. - holding_tabs: without them a cut-out part comes loose on the last pass and can be thrown off the machine. Recommend them for any part cut all the way through. Also worth asking when the geometry suggests it: pockets and holes (STEP files carry that depth information), and whether the job is milling or laser work. IMAGES (PNG, JPG, WebP ...) are always laser raster engraving. Ask for the engraving width in mm, photo or logo (image_mode), the controller (GRBL or Marlin) and its S maximum (laser_max_s), and tell the user to test power and speed on a scrap piece first.
| Name | Type | Req | Description |
|---|---|---|---|
| bit_diameter | number | – | Cutter diameter in mm, e.g. 6. Leave it out and step2gcode picks the largest whole millimetre that still fits through the smallest hole in the part. |
| controller | string | – | Laser G-code dialect. GRBL (default) or Marlin (3D printers with a laser module, MPCNC/LowRider and other Marlin machines). |
| depth | number | – | Cutting depth in mm; omit to take it from the model geometry (STEP) |
| feed_rate | number | – | Horizontal feed in mm/min. Same rule: only for materials outside the presets. |
| file_id | string | yes | file_id from check_upload or upload_file_content |
| holding_tabs | boolean | – | Leave small bridges so a part cut all the way through stays in the stock. Strongly recommended for through cuts. |
| holes | boolean | – | Drill or mill the holes found in the geometry |
| image_mode | string | – | Images only. Line by line (raster): dither for photos (default), threshold for logos and text, grayscale for power per dot. Along lines (vector, much faster): outline traces the edges of dark areas,… |
| image_width_mm | number | – | Images only: engraving width in mm; the height follows from the aspect ratio. Default 100. |
| inner_contours | boolean | – | Cut inner contours and cut-outs |
| laser | boolean | – | Laser job instead of milling |
| laser_max_s | number | – | Highest S value of the machine: $30 on GRBL (usually 1000), 255 on most Marlin machines. Ask the user - a wrong value burns at the wrong power. |
| laser_power | number | – | Laser power in % (laser jobs). For images the default is 30 %. |
| laser_speed | number | – | Laser speed in mm/min (laser jobs). For images the default is 2000. |
| material | string | – | Workpiece material. Sets spindle speed, feed rates and depth per pass. Ask the user - the default assumes softwood. |
| origin_xy | string | – | Workpiece origin in XY. Default TL. |
| origin_z | string | – | Z zero on the stock surface (top) or on the spoilboard. Default top. |
| plunge_rate | number | – | Plunge feed in mm/min, for materials outside the presets. |
| pockets | boolean | – | Mill pockets found in the geometry (STEP) |
| ramp_entry | boolean | – | Enter the material on a ramp instead of plunging straight down |
| spindle_speed | number | – | Spindle speed in rpm. Only set this when the material is not covered by the presets - otherwise the preset value is used. |
| step_down | number | – | Depth per pass in mm. Rule of thumb: up to 1x cutter diameter in softwood, far less in metal. |
No output schema declared.
No examples provided.
get_credit_balance ~27
Show credits left on the access token and how many models are already paid for. Free.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_download_link ~130
Return the download link for the finished G-code. THIS is the billed step: one credit per model not paid for yet. Re-downloading the same job or a model already paid for is free. Called without confirm, this tool charges nothing and only reports what the download would cost. Show that to the user, wait for their answer, and only then call again with confirm=true. Never set confirm=true on your own initiative - it spends the user's money.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | Set to true only after the user has explicitly agreed to spend the credit. |
| job_id | string | yes | – |
No output schema declared.
No examples provided.
get_job_status ~100
Check a generation job. While it runs you get the percentage done, how long it has been running and how much time is left before the generator gives up on its own (180 s). When it fails you get the generator's own reason - pass that on to the user instead of retrying blindly. This is the ONLY correct way to wait for a job; calling generate_gcode again never helps. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
No output schema declared.
No examples provided.
get_step_download_link ~170
Return the download link for a STEP file built by convert_mesh_to_step. While stl2step is in beta this is free and the answer says so; otherwise it is the billed step: one credit per model not paid for yet. The DXF contour that comes with a 2.5D part belongs to the same part and costs nothing extra. Called without confirm, this tool charges nothing and only reports what the download would cost. Show that to the user, wait for their answer, and only then call again with confirm=true. Never set confirm=true on your own initiative - it spends the user's money.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | Set to true only after the user has explicitly agreed to spend the credit. |
| step_id | string | yes | step_id from convert_mesh_to_step |
No output schema declared.
No examples provided.
preview_toolpath ~55
Show the finished tool path as an image (top view and isometric view, cutting moves and rapids in different colours) so the user can sanity-check the job before paying. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
No output schema declared.
No examples provided.
search ~97
Search step2gcode's help and knowledge base: supported files (STEP, DXF, SVG, STL, images, Gerber), machines and post-processors, settings, laser, 3D milling, pricing and credits. Returns pages with id, title and url; read one with fetch. Free, no file needed.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | What to look for, e.g. 'DXF holes smaller than the cutter' |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | – |
No examples provided.
upload_file_content ~498
Upload a CAD file by writing its content out yourself. Use this only when a direct curl upload to /api/upload is not possible - that route costs you no output at all. If you must use this tool, ALWAYS compress first and pass the output as content: (xz -9e -c model.step 2>/dev/null || gzip -9c model.step) | base64 | tr -d '\n' xz writes about a quarter less than gzip; the command falls back to gzip where xz is missing (macOS). xz, bzip2 and gzip are recognised by themselves - no extra argument. Do not paste the raw file. You have to write out every character you pass here, and a typical STEP solid takes you three minutes raw against twenty seconds compressed - the user watches that happen. Compression shrinks it about fivefold, which brings files up to roughly 80 KB within reach. NO SHELL AVAILABLE? Then do not use this tool for anything above about 10 KB - you would have to type the whole file out and the user waits minutes for it. Call create_upload_link instead: the user drops the file in a browser and it is done in five seconds. Same if the file is still too large after compressing. Free. NEXT STEP - do not generate yet. Ask the user: 1. Which material? Offer the presets (wood, hardwood, plywood, acrylic, aluminum, steel, brass). If theirs is not among them, pick the closest preset AND set spindle_speed, feed_rate, plunge_rate and step_down yourself from known cutting data for that material and cutter. 2. Which cutter diameters do they actually own? Recommend one from that list: it must fit the smallest inner radius of the part, and a smaller cutter means longer machining time. If you cannot judge the geometry yet, say so and suggest generating once to see the dimensions. 3. Is the part cut all the way through? Then recommend holding_tabs so it does not come loose on the last pass.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | Output of: (xz -9e -c model.step 2>/dev/null || gzip -9c model.step) | base64 | tr -d '\n' - the compressed file, base64 encoded (xz, bzip2 or gzip, detected by itself). |
| filename | string | yes | File name including extension, e.g. bracket.step |
No output schema declared.
No examples provided.
How do I install the step2gcode MCP server?
step2gcode is a hosted endpoint at https://www.step2gcode.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · www.step2gcode.com
claude mcp add --transport http com-step2gcode-step2gcode 'https://www.step2gcode.com/api/mcp'
What is the step2gcode MCP server?
step2gcode is an MCP server listed in the public MCP registry as com.step2gcode/step2gcode. Turn STEP, DXF and SVG files into CNC milling and laser G-code for GRBL, LinuxCNC, Mach3 and more. This page covers its hosted endpoint (https://www.step2gcode.com/api/mcp).
Is the step2gcode MCP server safe to use?
step2gcode scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the step2gcode MCP server expose?
step2gcode exposes 12 tools: create_upload_link, check_upload, upload_file_content, generate_gcode, get_job_status, and 7 more. Their descriptions and schemas cost roughly 2,573 tokens of context every time the server is loaded.
Does the step2gcode MCP server require authentication?
No. We connected to step2gcode without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the step2gcode MCP server still maintained?
step2gcode is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the step2gcode MCP server?
VerifyMCP ran 13 checks on step2gcode, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.