Remote MCP · Endpoint

US state NH MCP server

No. US state NH answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/st-nh/mcp

The last check completed an MCP handshake.

Registry name
io.github.sadri-dridi/st-nh
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
45 ms
Tools exposed
31 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
USPS state code NH.
Listing
From the official MCP registry (active).
Recent checks of US state NH
CheckedResultHandshake
1 hour agoHandshake completed45 ms
2 days agoHandshake completed32 ms
4 days agoHandshake completed10 ms
5 days agoHandshake completed52 ms
7 days agoHandshake completed15 ms
8 days agoHandshake completed100 ms
9 days agoHandshake completed35 ms
12 days agoHandshake completed18 ms
14 days agoHandshake completed32 ms
15 days agoHandshake completed31 ms
17 days agoHandshake completed18 ms
18 days agoHandshake completed10 ms
19 days agoHandshake completed18 ms
20 days agoHandshake completed17 ms
20 days agoHandshake completed15 ms
22 days agoHandshake completed20 ms
23 days agoHandshake completed12 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 US state NH and makes no claim about it beyond what these checks measured.