Remote MCP · Endpoint
com.footfally/site MCP server
No. com.footfally/site answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://footfally.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.footfally/site
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 688 ms
- Tools exposed
- 7 tools
- Uptime, last 30 days
- 58.8% from 17 checks
- Described by its publisher as
- Footfally: the site's own MCP server — dataset; every answer cites the site.
- Website
- https://footfally.com/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 688 ms |
| 2 days ago | Handshake completed | 830 ms |
| 4 days ago | Failed - the check failed for an unclassified reason | — |
| 5 days ago | Handshake completed | 410 ms |
| 7 days ago | Handshake completed | 439 ms |
| 8 days ago | Handshake completed | 1.19 s |
| 9 days ago | Handshake completed | 684 ms |
| 12 days ago | Failed - the check failed for an unclassified reason | — |
| 13 days ago | Failed - the check failed for an unclassified reason | — |
| 15 days ago | Failed - the check failed for an unclassified reason | — |
| 16 days ago | Handshake completed | 822 ms |
| 17 days ago | Handshake completed | 474 ms |
| 18 days ago | Handshake completed | 716 ms |
| 19 days ago | Failed - the check failed for an unclassified reason | — |
| 20 days ago | Handshake completed | 748 ms |
| 21 days ago | Failed - the check failed for an unclassified reason | — |
| 22 days ago | Failed - the check failed for an unclassified reason | — |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 10 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 com.footfally/site and makes no claim about it beyond what these checks measured.