Remote MCP · Endpoint

Saifuban MCP server

No. Saifuban answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://zrphnuvrsldcycxtdftv.supabase.co/functions/v1/saifuban-mcp

The last check completed an MCP handshake.

Registry name
io.github.ut181749ut/saifuban
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
252 ms
Tools exposed
4 tools
Uptime, last 30 days
3 checks from 3 checks
Described by its publisher as
Hard daily caps on AI agents' API spend, plus phone approval before any other payment.
Listing
From the official MCP registry (active).
Recent checks of Saifuban
CheckedResultHandshake
3 hours agoHandshake completed252 ms
4 days agoHandshake completed300 ms
7 days agoHandshake completed213 ms

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

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