Remote MCP · Endpoint

Treasury Tic MCP server

No. Treasury Tic answered an MCP handshake 16 minutes ago.

UpLast checked 16 minutes ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/treasury-tic
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
148 ms
Tools exposed
46 tools
Uptime, last 30 days
92.3% from 13 checks
Described by its publisher as
U.S. Treasury International Capital (TIC) System — foreign holdings of U.S. securities, by…
Listing
From the official MCP registry (active).
Recent checks of Treasury Tic
CheckedResultHandshake
16 minutes agoHandshake completed148 ms
8 days agoHandshake completed219 ms
9 days agoHandshake completed80 ms
11 days agoHandshake completed147 ms
12 days agoHandshake completed107 ms
13 days agoHandshake completed100 ms
14 days agoHandshake completed105 ms
15 days agoHandshake completed114 ms
16 days agoHandshake completed252 ms
19 days agoHandshake completed258 ms
21 days agoFailed - the request timed out—
24 days agoHandshake completed461 ms
26 days agoHandshake completed764 ms

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

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