Remote MCP · Endpoint

Fema Nfhl MCP server

No. Fema Nfhl answered an MCP handshake 1 hour ago.

UpLast checked 1 hour 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
264 ms
Tools exposed
44 tools
Uptime, last 30 days
100% from 16 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
1 hour agoHandshake completed264 ms
2 days agoHandshake completed1.62 s
4 days agoHandshake completed72 ms
6 days agoHandshake completed1.21 s
7 days agoHandshake completed1.02 s
9 days agoHandshake completed999 ms
10 days agoHandshake completed1.07 s
11 days agoHandshake completed1.95 s
14 days agoHandshake completed41 ms
15 days agoHandshake completed270 ms
17 days agoHandshake completed42 ms
19 days agoHandshake completed223 ms
20 days agoHandshake completed40 ms
21 days agoHandshake completed46 ms
22 days agoHandshake completed45 ms
22 days agoHandshake completed48 ms

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