Remote MCP · Endpoint

New Hampshire Code MCP server

No. New Hampshire Code answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://gateway.pipeworx.io/new-hampshire-code/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/new-hampshire-code
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
172 ms
Tools exposed
46 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
New Hampshire RSA (Revised Statutes Annotated) — state statutes by citation and by topic. Fleet…
Listing
From the official MCP registry (active).
Recent checks of New Hampshire Code
CheckedResultHandshake
3 hours agoHandshake completed172 ms
1 day agoHandshake completed385 ms
4 days agoHandshake completed3.20 s
7 days agoHandshake completed1.04 s
9 days agoHandshake completed1.89 s
11 days agoHandshake completed984 ms
13 days agoHandshake completed72 ms
15 days agoHandshake completed104 ms
18 days agoHandshake completed87 ms
20 days agoHandshake completed63 ms
21 days agoHandshake completed56 ms
23 days agoHandshake completed64 ms

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

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