# Saifuban (remote · zrphnuvrsldcycxtdftv.supabase.co)

Hard daily caps on AI agents' API spend, plus phone approval before any other payment.

- Trust score: 82/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `zrphnuvrsldcycxtdftv.supabase.co`: 82/100 (this document), [markdown](https://verifymcp.io/servers/ut181749ut-saifuban/functions-v1-saifuban-mcp.md), [page](https://verifymcp.io/servers/ut181749ut-saifuban/functions-v1-saifuban-mcp)

## Channel facts

- Endpoint: `https://zrphnuvrsldcycxtdftv.supabase.co/functions/v1/saifuban-mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.4.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 94/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 917 tokens (~229/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 94/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 83% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Saifuban MCP server?

Saifuban is a hosted endpoint at https://zrphnuvrsldcycxtdftv.supabase.co/functions/v1/saifuban-mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http ut181749ut-saifuban 'https://zrphnuvrsldcycxtdftv.supabase.co/functions/v1/saifuban-mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ut181749ut-saifuban": {
      "url": "https://zrphnuvrsldcycxtdftv.supabase.co/functions/v1/saifuban-mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ut181749ut-saifuban": {
      "type": "http",
      "url": "https://zrphnuvrsldcycxtdftv.supabase.co/functions/v1/saifuban-mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ut181749ut-saifuban]
url = "https://zrphnuvrsldcycxtdftv.supabase.co/functions/v1/saifuban-mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ut181749ut-saifuban": {
      "type": "remote",
      "url": "https://zrphnuvrsldcycxtdftv.supabase.co/functions/v1/saifuban-mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ut181749ut-saifuban --url 'https://zrphnuvrsldcycxtdftv.supabase.co/functions/v1/saifuban-mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ut181749ut-saifuban:
    url: "https://zrphnuvrsldcycxtdftv.supabase.co/functions/v1/saifuban-mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ut181749ut-saifuban": {
      "Transport": "http",
      "Url": "https://zrphnuvrsldcycxtdftv.supabase.co/functions/v1/saifuban-mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ut181749ut-saifuban -t streamable-http -u 'https://zrphnuvrsldcycxtdftv.supabase.co/functions/v1/saifuban-mcp'
```

### Other

```json
{
  "mcpServers": {
    "ut181749ut-saifuban": {
      "type": "http",
      "url": "https://zrphnuvrsldcycxtdftv.supabase.co/functions/v1/saifuban-mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-19 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 81, 0)

- [functional] Server version: 0.7.1 → 0.8.0

### 2026-11-17 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-15 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-13 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-11 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-10 (score 77, +5)

- [security improvement] Authorization: partial → pass
- [security] First check of Authorization: partial
- [security] Tool “get_budget” rewrote its description, which is the text the model reads
- [security] Tool “request_payment” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 202 → 229
- [functional] Server version: 0.5.0 → 0.7.1
- [cosmetic] “request_payment” added an optional parameter “idempotency_key”

### 2026-11-09 (score 72, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “request_payment” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 167 → 202
- [functional improvement] Tool coverage: 71% → 82%
- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 0.4.0 → 0.5.0
- [functional] New tool “list_payments”
- [cosmetic] “request_payment” added an optional parameter “recurring”

## MCP tools (4)

### `request_payment` (~534 tokens)

お金を使う前に必ず呼ぶツール。支払先・金額・理由を財布番に申請し、許可が出たかを返す。status が approved のときだけ支払ってよい。pending_approval は持ち主の承認待ちで、まだ支払ってはいけない(持ち主のスマホに通知が届く)。denied や expired のときは支払わず、reason をユーザーに伝える。 / Call this BEFORE spending any money. Pay only when status is approved. pending_approval means the owner must approve on their phone — do not pay yet. When approved, the result includes payment_token: a single-use token that payment tools can verify, so payments made without approval can be refused. If the payment is a subscription or renews automatically, set recurring. Before buying something you may already have paid for, call list_payments. If you get pending_approval, poll check_payment_status instead of calling request_payment again (a repeat of a pending request returns the same request).

Input parameters:

- `amount` (number, required): 支払う金額(税込) / amount to pay, tax included
- `currency` (string): amount の通貨。省略すると持ち主の通貨 / currency of amount; defaults to the owner's currency
- `idempotency_key` (string): 同じ支払いをやり直すときは同じ値を渡す。新しい申請は作られず、前の申請が返る / Pass the same value when retrying the same payment; the earlier request is returned instead of creating a new one
- `merchant` (string, required): 支払先のサービス名や店名 / merchant or service name (e.g. OpenAI API, AWS)
- `reason` (string, required): なぜこの支払いが必要か。持ち主が承認するときに読む / why this payment is needed (the owner reads this)
- `recurring` (string): サブスク・定期購入・自動更新なら、その間隔を必ず指定する。定期購入は金額に関係なく持ち主の承認が必要 / If this starts or renews a subscription or any recurring charge, set the billing interval. Recurring charges always need the owner's approval, wha…
- `wait_for_approval_seconds` (integer): 承認待ちのとき待つ秒数(最大45秒) / seconds to wait for approval

### `check_payment_status` (~68 tokens)

以前の申請(request_id)が承認されたかを確認する。approved になってから支払うこと。 / Check whether an earlier request was approved. Pay only after it is approved.

Input parameters:

- `request_id` (integer, required)
- `wait_seconds` (integer)

### `list_payments` (~168 tokens)

このAI自身の過去の支払い申請を調べる(二重払い・二重契約を避けるため)。例: 今月すでにSpotifyを承認済みか。 / Look up this agent's own past payment requests, e.g. to check whether a Spotify charge was already approved this month, and avoid paying twice.

Input parameters:

- `days` (integer): 何日前までさかのぼるか(既定30) / how many days back (default 30)
- `limit` (integer): 最大件数(既定20) / max results (default 20)
- `merchant` (string): 支払先の名前で絞り込む(部分一致) / filter by merchant name (partial match)

### `get_budget` (~70 tokens)

このAIが今日・今週・今月あといくら使えるか、1回の上限、自動承認ライン、使ってよい支払先を確認する。 / Check the remaining daily, weekly and monthly budget, per-payment limit, auto-approve amount and allowed merchants.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ut181749ut-saifuban/functions-v1-saifuban-mcp#diagnostics

## Score history

- 2026-11-21: 82
- 2026-11-20: 82
- 2026-11-19: 82
- 2026-11-18: 81
- 2026-11-17: 81
- 2026-11-16: 80
- 2026-11-15: 80
- 2026-11-14: 79
- 2026-11-13: 79
- 2026-11-12: 78
- 2026-11-11: 78
- 2026-11-10: 77
- 2026-11-09: 72
- 2026-11-08: 71

## Common questions

### What is the Saifuban MCP server?

Saifuban is an MCP server listed in the public MCP registry as io.github.ut181749ut/saifuban. Hard daily caps on AI agents' API spend, plus phone approval before any other payment. This page covers its hosted endpoint (https://zrphnuvrsldcycxtdftv.supabase.co/functions/v1/saifuban-mcp).

### Is the Saifuban MCP server safe to use?

Saifuban scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Saifuban MCP server expose?

Saifuban exposes 4 tools: request_payment, check_payment_status, list_payments, get_budget. Their descriptions and schemas cost roughly 840 tokens of context every time the server is loaded.

### Does the Saifuban MCP server require authentication?

Yes. Saifuban asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Saifuban MCP server still maintained?

Saifuban is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Saifuban MCP server?

VerifyMCP ran 13 checks on Saifuban, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://zrphnuvrsldcycxtdftv.supabase.co/functions/v1/saifuban-mcp
- Authorisation metadata: https://zrphnuvrsldcycxtdftv.supabase.co/.well-known/oauth-protected-resource/functions/v1/saifuban-mcp
- Repository: https://github.com/ut181749ut/saifuban
- Website: https://ut181749ut.github.io/saifuban/
- Changelog RSS feed: https://verifymcp.io/servers/ut181749ut-saifuban/functions-v1-saifuban-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ut181749ut-saifuban/functions-v1-saifuban-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/ut181749ut-saifuban/functions-v1-saifuban-mcp.json
- HTML version of this page: https://verifymcp.io/servers/ut181749ut-saifuban/functions-v1-saifuban-mcp
