Remote MCP · Endpoint

Steady Steel MCP server

No. Steady Steel answered an MCP handshake 10 hours ago.

UpLast checked 10 hours ago

Server URL

https://www.steadysteel.org/mcp

The last check completed an MCP handshake.

Registry name
org.steadysteel/steady-steel
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
31 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Quotes laser-cut steel, stainless and aluminum plate and catalog products. Newmarket, Ontario.
Listing
From the official MCP registry (active).
Recent checks of Steady Steel
CheckedResultHandshake
10 hours agoHandshake completed31 ms
2 days agoHandshake completed36 ms
4 days agoHandshake completed30 ms
6 days agoHandshake completed26 ms
8 days agoHandshake completed28 ms
10 days agoHandshake completed41 ms
12 days agoHandshake completed26 ms
13 days agoHandshake completed34 ms
15 days agoHandshake completed29 ms
16 days agoHandshake completed27 ms
18 days agoHandshake completed26 ms
20 days agoHandshake completed28 ms
22 days agoHandshake completed28 ms
23 days agoHandshake completed38 ms

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

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 Steady Steel and makes no claim about it beyond what these checks measured.