Remote MCP · Endpoint
PassFast MCP server
Yes, as of 1 hour ago: the server returned an HTTP error.
DownLast checked 1 hour ago
Server URL
https://passfa.st/mcp
The last check failed: the server returned an HTTP error.
- Registry name
- st.passfa/passfast
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 47 tools
- Uptime, last 30 days
- 89.5% from 19 checks
- Described by its publisher as
- Remote HTTPS MCP for Apple + Google Wallet passes. Paste sk_live_ once.
- Website
- https://passfa.st/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Failed - the server returned an HTTP error | — |
| 1 day ago | Failed - the server returned an HTTP error | — |
| 2 days ago | Handshake completed | 395 ms |
| 3 days ago | Handshake completed | 140 ms |
| 4 days ago | Handshake completed | 139 ms |
| 5 days ago | Handshake completed | 186 ms |
| 6 days ago | Handshake completed | 992 ms |
| 8 days ago | Handshake completed | 188 ms |
| 11 days ago | Handshake completed | 124 ms |
| 13 days ago | Handshake completed | 110 ms |
| 16 days ago | Handshake completed | 293 ms |
| 18 days ago | Handshake completed | 194 ms |
| 20 days ago | Handshake completed | 214 ms |
| 22 days ago | Handshake completed | 95 ms |
| 24 days ago | Handshake completed | 240 ms |
| 26 days ago | Handshake completed | 119 ms |
| 27 days ago | Handshake completed | 190 ms |
| 29 days ago | Handshake completed | 122 ms |
| 29 days ago | Handshake completed | 198 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 27 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 PassFast and makes no claim about it beyond what these checks measured.