Remote MCP · Endpoint

uniwire MCP server

No. uniwire answered an MCP handshake 19 minutes ago.

UpLast checked 19 minutes ago

Server URL

https://mcp.uniwire.sh/mcp

The last check completed an MCP handshake.

Registry name
io.github.uniwire-dev/uniwire
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
314 ms
Tools exposed
14 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Electrical single-line and multi-line diagrams: build, check (NF C 15-100, IEC 60364), draw, PDF.
Listing
From the official MCP registry (active).
Recent checks of uniwire
CheckedResultHandshake
19 minutes agoHandshake completed314 ms
9 days agoHandshake completed330 ms
9 days agoHandshake completed309 ms
11 days agoHandshake completed296 ms
12 days agoHandshake completed305 ms
13 days agoHandshake completed343 ms
14 days agoHandshake completed327 ms
14 days agoHandshake completed365 ms
16 days agoHandshake completed436 ms
19 days agoHandshake completed414 ms
21 days agoHandshake completed314 ms
24 days agoHandshake completed1.25 s
26 days agoHandshake completed317 ms
28 days agoHandshake completed309 ms

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