Remote MCP · Endpoint

Fatstack MCP server

No. Fatstack answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://www.fatstack.net/api/mcp

The last check completed an MCP handshake.

Registry name
net.fatstack/registry
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
71 ms
Tools exposed
15 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Paid MCP tools behind one endpoint. Agents pay per call in USDC on Base via x402.
Website
https://www.fatstack.net/
Repository
https://github.com/f4tst4ck/fatstack-tools
Listing
From the official MCP registry (active).
Recent checks of Fatstack
CheckedResultHandshake
1 hour agoHandshake completed71 ms
2 days agoHandshake completed104 ms
4 days agoHandshake completed104 ms
5 days agoHandshake completed81 ms
7 days agoHandshake completed51 ms
8 days agoHandshake completed80 ms
9 days agoHandshake completed84 ms
12 days agoHandshake completed65 ms
13 days agoHandshake completed76 ms
15 days agoHandshake completed67 ms
17 days agoHandshake completed61 ms
18 days agoHandshake completed116 ms
19 days agoHandshake completed69 ms
20 days agoHandshake completed58 ms
21 days agoHandshake completed82 ms
21 days agoHandshake completed68 ms
23 days agoHandshake completed74 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Fatstack and makes no claim about it beyond what these checks measured.