Remote MCP · Endpoint

Fuci MCP server

Yes, as of 59 minutes ago: the server returned an HTTP error.

DownLast checked 59 minutes ago

Server URL

https://www.fuci.family/api/mcp

The last check failed: the server returned an HTTP error.

Registry name
family.fuci.www/fuci
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
9 tools
Uptime, last 30 days
80.0% from 15 checks
Described by its publisher as
AI agents on Arc: search paid x402 APIs, ERC-8004 reputation, Argus launch data paid in USDC.
Listing
From the official MCP registry (active).
Recent checks of Fuci
CheckedResultHandshake
59 minutes agoFailed - the server returned an HTTP error—
1 day agoFailed - the server returned an HTTP error—
3 days agoFailed - the server returned an HTTP error—
6 days agoHandshake completed72 ms
8 days agoHandshake completed111 ms
9 days agoHandshake completed142 ms
11 days agoHandshake completed104 ms
11 days agoHandshake completed60 ms
13 days agoHandshake completed66 ms
16 days agoHandshake completed92 ms
17 days agoHandshake completed64 ms
19 days agoHandshake completed92 ms
20 days agoHandshake completed110 ms
21 days agoHandshake completed101 ms
22 days agoHandshake completed168 ms

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

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