Remote MCP · Endpoint

Usgs National Map MCP server

No. Usgs National Map answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://gateway.pipeworx.io/usgs-national-map/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/usgs-national-map
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
111 ms
Tools exposed
44 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
USGS The National Map (TNM) Access API MCP
Listing
From the official MCP registry (active).
Recent checks of Usgs National Map
CheckedResultHandshake
1 day agoHandshake completed111 ms
3 days agoHandshake completed70 ms
5 days agoHandshake completed64 ms
7 days agoHandshake completed221 ms
8 days agoHandshake completed81 ms
10 days agoHandshake completed407 ms
11 days agoHandshake completed44 ms
13 days agoHandshake completed173 ms
15 days agoHandshake completed49 ms
17 days agoHandshake completed48 ms
18 days agoHandshake completed92 ms
19 days agoHandshake completed53 ms
20 days agoHandshake completed41 ms
22 days agoHandshake completed40 ms
22 days agoHandshake completed50 ms

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

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