Remote MCP · Endpoint

OpenFab MCP server

No. OpenFab answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://openfab-22100483453.us-central1.run.app/mcp/

The last check completed an MCP handshake.

Registry name
io.github.yyphilo/openfab
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
159 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Instant parametric cost estimates for custom manufacturing: CNC, molding, sheet metal, 3DP, PCB.
Listing
From the official MCP registry (active).
Recent checks of OpenFab
CheckedResultHandshake
1 hour agoHandshake completed159 ms
9 days agoHandshake completed173 ms
10 days agoHandshake completed119 ms
11 days agoHandshake completed111 ms
12 days agoHandshake completed152 ms
14 days agoHandshake completed112 ms
14 days agoHandshake completed117 ms
15 days agoHandshake completed291 ms
17 days agoHandshake completed108 ms
19 days agoHandshake completed168 ms
21 days agoHandshake completed148 ms
24 days agoHandshake completed138 ms
26 days agoHandshake completed265 ms
28 days agoHandshake completed160 ms

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

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