Remote MCP · Endpoint

Usaspending MCP server

No. Usaspending answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/usaspending/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/usaspending
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
289 ms
Tools exposed
48 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
USAspending MCP — Federal spending data from USAspending.gov API
Listing
From the official MCP registry (active).
Recent checks of Usaspending
CheckedResultHandshake
1 hour agoHandshake completed289 ms
2 days agoHandshake completed58 ms
4 days agoHandshake completed54 ms
5 days agoHandshake completed83 ms
7 days agoHandshake completed51 ms
8 days agoHandshake completed2.73 s
9 days agoHandshake completed54 ms
12 days agoHandshake completed50 ms
14 days agoHandshake completed343 ms
15 days agoHandshake completed66 ms
17 days agoHandshake completed70 ms
18 days agoHandshake completed40 ms
19 days agoHandshake completed41 ms
20 days agoHandshake completed40 ms
20 days agoHandshake completed51 ms
22 days agoHandshake completed280 ms
23 days agoHandshake completed39 ms

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

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