Remote MCP · Endpoint

Steel Brain MCP server

No. Steel Brain answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://api.steelbrain.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.dryow1/steel-brain
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
709 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Trade-verified steel grade properties, substitution verdicts, and mill-cert guidance for AI agents.
Listing
From the official MCP registry (active).
Recent checks of Steel Brain
CheckedResultHandshake
2 hours agoHandshake completed709 ms
2 days agoHandshake completed699 ms
4 days agoHandshake completed709 ms
6 days agoHandshake completed720 ms
7 days agoHandshake completed697 ms
9 days agoHandshake completed705 ms
10 days agoHandshake completed691 ms
11 days agoHandshake completed693 ms
14 days agoHandshake completed725 ms
15 days agoHandshake completed696 ms
17 days agoHandshake completed770 ms
19 days agoHandshake completed681 ms
20 days agoHandshake completed691 ms
21 days agoHandshake completed721 ms
22 days agoHandshake completed692 ms
22 days agoHandshake completed710 ms

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

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