Remote MCP · Endpoint

BlockWerk MCP server

No. BlockWerk answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://blockwerk-mcp-worker.blockwerk.workers.dev/

The last check completed an MCP handshake.

Registry name
tech.blockwerk/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
336 ms
Tools exposed
44 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Build, run and analyse block-diagram simulations: PID, Bode, FFT, optimisation and code export.
Listing
From the official MCP registry (active).
Recent checks of BlockWerk
CheckedResultHandshake
1 hour agoHandshake completed336 ms
4 days agoHandshake completed284 ms
14 days agoHandshake completed290 ms
15 days agoHandshake completed328 ms
15 days agoHandshake completed290 ms
17 days agoHandshake completed201 ms
18 days agoHandshake completed354 ms
19 days agoHandshake completed345 ms
20 days agoHandshake completed199 ms
21 days agoHandshake completed409 ms
23 days agoHandshake completed262 ms
25 days agoHandshake completed303 ms
28 days agoHandshake completed64 ms

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

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