Remote MCP · Endpoint

Nato MCP server

No. Nato answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/nato/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/nato
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
55 ms
Tools exposed
44 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Phonetic & Morse code MCP.
Listing
From the official MCP registry (active).
Recent checks of Nato
CheckedResultHandshake
1 hour agoHandshake completed55 ms
2 days agoHandshake completed67 ms
4 days agoHandshake completed54 ms
5 days agoHandshake completed63 ms
7 days agoHandshake completed52 ms
8 days agoHandshake completed287 ms
9 days agoHandshake completed50 ms
12 days agoHandshake completed45 ms
14 days agoHandshake completed51 ms
15 days agoHandshake completed167 ms
17 days agoHandshake completed55 ms
18 days agoHandshake completed38 ms
19 days agoHandshake completed43 ms
20 days agoHandshake completed38 ms
20 days agoHandshake completed51 ms
22 days agoHandshake completed56 ms
23 days agoHandshake completed48 ms

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

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