Remote MCP · Endpoint

Usda Soil MCP server

No. Usda Soil answered an MCP handshake 15 hours ago.

UpLast checked 15 hours ago

Server URL

https://gateway.pipeworx.io/usda-soil/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/usda-soil
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
73 ms
Tools exposed
44 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
USDA-NRCS Soil Data Access over SSURGO, the field-surveyed US soil map — the soil at any US…
Listing
From the official MCP registry (active).
Recent checks of Usda Soil
CheckedResultHandshake
15 hours agoHandshake completed73 ms
2 days agoHandshake completed1.24 s
4 days agoHandshake completed63 ms
6 days agoHandshake completed282 ms
8 days agoHandshake completed119 ms
9 days agoHandshake completed183 ms
10 days agoHandshake completed121 ms
13 days agoHandshake completed1.62 s
14 days agoHandshake completed45 ms
16 days agoHandshake completed52 ms
17 days agoHandshake completed181 ms
19 days agoHandshake completed45 ms
20 days agoHandshake completed39 ms
21 days agoHandshake completed40 ms
21 days agoHandshake completed45 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 Usda Soil and makes no claim about it beyond what these checks measured.