Remote MCP · Endpoint

Fas MCP server

No. Fas answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/fas
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
457 ms
Tools exposed
42 tools
Uptime, last 30 days
88.2% from 17 checks
Described by its publisher as
FAS MCP — USDA Foreign Agricultural Service (trade & global production data)
Listing
From the official MCP registry (active).
Recent checks of Fas
CheckedResultHandshake
1 hour agoHandshake completed457 ms
2 days agoHandshake completed58 ms
4 days agoHandshake completed56 ms
5 days agoFailed - the request timed out—
7 days agoHandshake completed72 ms
8 days agoHandshake completed48 ms
9 days agoFailed - the request timed out—
12 days agoHandshake completed42 ms
14 days agoHandshake completed38 ms
15 days agoHandshake completed463 ms
17 days agoHandshake completed36 ms
18 days agoHandshake completed1.17 s
19 days agoHandshake completed41 ms
20 days agoHandshake completed43 ms
21 days agoHandshake completed41 ms
21 days agoHandshake completed41 ms
23 days agoHandshake completed47 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 15 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 Fas and makes no claim about it beyond what these checks measured.