Remote MCP · Endpoint

com.footfally/site MCP server

Yes, as of 1 hour ago: the check failed for an unclassified reason.

DownLast checked 1 hour ago

Server URL

https://footfally.com/mcp

The last check failed: the check failed for an unclassified reason.

Registry name
com.footfally/site
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
7 tools
Uptime, last 30 days
68.4% from 19 checks
Described by its publisher as
Footfally: the site's own MCP server — dataset; every answer cites the site.
Listing
From the official MCP registry (active).
Recent checks of com.footfally/site
CheckedResultHandshake
1 hour agoFailed - the check failed for an unclassified reason—
18 hours agoFailed - the check failed for an unclassified reason—
2 days agoHandshake completed553 ms
3 days agoHandshake completed656 ms
4 days agoFailed - the check failed for an unclassified reason—
5 days agoHandshake completed605 ms
6 days agoFailed - the check failed for an unclassified reason—
7 days agoHandshake completed762 ms
10 days agoFailed - the check failed for an unclassified reason—
13 days agoHandshake completed840 ms
15 days agoHandshake completed685 ms
17 days agoHandshake completed562 ms
19 days agoHandshake completed848 ms
21 days agoHandshake completed688 ms
23 days agoHandshake completed830 ms
25 days agoFailed - the check failed for an unclassified reason—
27 days agoHandshake completed410 ms
28 days agoHandshake completed439 ms
29 days agoHandshake completed1.19 s

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

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