Remote MCP · Endpoint

step2gcode MCP server

No. step2gcode answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://www.step2gcode.com/api/mcp/test

The last check completed an MCP handshake.

Registry name
com.step2gcode/step2gcode
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
360 ms
Tools exposed
12 tools
Uptime, last 30 days
3 checks from 3 checks
Described by its publisher as
Turn STEP, DXF and SVG files into CNC milling and laser G-code for GRBL, LinuxCNC, Mach3 and more.
Listing
From the official MCP registry (active).
Recent checks of step2gcode
CheckedResultHandshake
7 hours agoHandshake completed360 ms
4 days agoHandshake completed287 ms
7 days agoHandshake completed299 ms

The last 3 checks. Full history is kept for 30 days; the all-time counter stands at 3 responding of 3.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with step2gcode and makes no claim about it beyond what these checks measured.