Remote MCP · Endpoint

FastAF MCP server

No. FastAF answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.fastaf.co/mcp

The last check completed an MCP handshake.

Registry name
co.fastaf/fastaf
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
458 ms
Tools exposed
23 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
22 web-data tools: search, Bing, images, Reddit without authors, jobs, patents, flights and YouTube.
Listing
From the official MCP registry (active).
Recent checks of FastAF
CheckedResultHandshake
1 hour agoHandshake completed458 ms
1 day agoHandshake completed364 ms
2 days agoHandshake completed344 ms
3 days agoHandshake completed544 ms
4 days agoHandshake completed376 ms
5 days agoHandshake completed440 ms
7 days agoHandshake completed779 ms
10 days agoHandshake completed290 ms
12 days agoCredentials required—
14 days agoCredentials required—
17 days agoCredentials required—
19 days agoCredentials required—
21 days agoCredentials required—
23 days agoCredentials required—
25 days agoCredentials required—
26 days agoCredentials required—
28 days agoCredentials required—
29 days agoCredentials required—

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

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