Remote MCP · Endpoint

Fed Nic MCP server

No. Fed Nic answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://gateway.pipeworx.io/fed-nic/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/fed-nic
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
641 ms
Tools exposed
45 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Federal Reserve National Information Center (NIC, ffiec.gov/npw)
Listing
From the official MCP registry (active).
Recent checks of Fed Nic
CheckedResultHandshake
2 hours agoHandshake completed641 ms
2 days agoHandshake completed572 ms
4 days agoHandshake completed136 ms
6 days agoHandshake completed72 ms
8 days agoHandshake completed67 ms
9 days agoHandshake completed75 ms
10 days agoHandshake completed2.08 s
11 days agoHandshake completed48 ms
14 days agoHandshake completed35 ms
16 days agoHandshake completed1.64 s
17 days agoHandshake completed1.00 s
19 days agoHandshake completed1.23 s
20 days agoHandshake completed974 ms
21 days agoHandshake completed925 ms
22 days agoHandshake completed86 ms
22 days agoHandshake completed2.12 s

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