Remote MCP · Endpoint

PassFast MCP server

No. PassFast answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://passfa.st/mcp

The last check completed an MCP handshake.

Registry name
st.passfa/passfast
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
214 ms
Tools exposed
47 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Remote HTTPS MCP for Apple + Google Wallet passes. Paste sk_live_ once.
Listing
From the official MCP registry (active).
Recent checks of PassFast
CheckedResultHandshake
1 hour agoHandshake completed214 ms
2 days agoHandshake completed95 ms
4 days agoHandshake completed240 ms
5 days agoHandshake completed119 ms
7 days agoHandshake completed190 ms
8 days agoHandshake completed122 ms
9 days agoHandshake completed198 ms
12 days agoHandshake completed110 ms
13 days agoHandshake completed139 ms
15 days agoHandshake completed117 ms
17 days agoHandshake completed84 ms
18 days agoHandshake completed87 ms
19 days agoHandshake completed113 ms
20 days agoHandshake completed110 ms
21 days agoHandshake completed194 ms
21 days agoHandshake completed104 ms
23 days agoHandshake completed113 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.

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.