Remote MCP · Endpoint

Fema Nfhl MCP server

No. Fema Nfhl answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://gateway.pipeworx.io/fema-nfhl/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/fema-nfhl
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
928 ms
Tools exposed
47 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
FEMA National Flood Hazard Layer (NFHL) MCP
Listing
From the official MCP registry (active).
Recent checks of Fema Nfhl
CheckedResultHandshake
3 hours agoHandshake completed928 ms
9 days agoHandshake completed898 ms
10 days agoHandshake completed822 ms
11 days agoHandshake completed118 ms
12 days agoHandshake completed950 ms
14 days agoHandshake completed894 ms
14 days agoHandshake completed1.11 s
15 days agoHandshake completed132 ms
17 days agoHandshake completed615 ms
19 days agoHandshake completed78 ms
22 days agoHandshake completed2.19 s
24 days agoHandshake completed433 ms
26 days agoHandshake completed98 ms
28 days agoHandshake completed264 ms

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

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