Remote MCP · Endpoint

Treasury Fiscal MCP server

No. Treasury Fiscal answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://gateway.pipeworx.io/treasury-fiscal/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/treasury-fiscal
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
59 ms
Tools exposed
42 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Treasury Fiscal MCP — US Treasury Fiscal Data API
Listing
From the official MCP registry (active).
Recent checks of Treasury Fiscal
CheckedResultHandshake
1 day agoHandshake completed59 ms
4 days agoHandshake completed60 ms
5 days agoHandshake completed59 ms
7 days agoHandshake completed67 ms
8 days agoHandshake completed66 ms
9 days agoHandshake completed68 ms
12 days agoHandshake completed77 ms
13 days agoHandshake completed51 ms
15 days agoHandshake completed61 ms
17 days agoHandshake completed52 ms
18 days agoHandshake completed62 ms
19 days agoHandshake completed45 ms
20 days agoHandshake completed52 ms
20 days agoHandshake completed71 ms
21 days agoHandshake completed49 ms
23 days agoHandshake completed51 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 Treasury Fiscal and makes no claim about it beyond what these checks measured.