Saifuban MCP server
io.github.ut181749ut/saifubanut181749utstreamable-httpv0.4.1Scanned
Hard daily caps on AI agents' API spend, plus phone approval before any other payment.
3 tools: 1 do something that can't be undone, 1 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here does something that can't be undone. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Saifuban MCP server can do
The Saifuban MCP server is published by the GitHub account ut181749ut. It has 3 tools. It can do things that cannot be undone, such as sending, paying or publishing (request_payment) and create or change data (1 tool: check_payment_status), but cannot delete data. 1 tool only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 8, 2026, version 0.4.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
3 tools
Can't be undone 1Claude Code: ask
request_paymentお金を使う前に必ず呼ぶツール。支払先・金額・理由を財布番に申請し、許可が出たかを返す。status が approved のときだけ支払ってよい。pending_approval は持ち主の承認待ちで、まだ支払ってはいけない(持ち主のスマホに通知が届く)。denied や expired のときは支払わず、reason をユーザーに伝える。 / Call t…No findings
Why it is in this group
- The name "request_payment" says "request": a word for a change.
- The name "request_payment" also says "payment": a word that usually means money moves, which cannot be taken back.
- The input carries an amount (input.amount) and a currency, so it moves money.
Description, as the server wrote it お金を使う前に必ず呼ぶツール。支払先・金額・理由を財布番に申請し、許可が出たかを返す。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.
Annotations the server declares
- title: 支払いを申請する / Request a payment
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
Changes things 1Claude Code: ask
check_payment_status以前の申請(request_id)が承認されたかを確認する。approved になってから支払うこと。 / Check whether an earlier request was approved.1 finding
Why it is in this group
- The name "check_payment_status" says "status": a word for reading.
- The description's first verb is "request": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "check_payment_status" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "check_payment_status" says "status": a word for reading.
Description, as the server wrote it 以前の申請(request_id)が承認されたかを確認する。approved になってから支払うこと。 / Check whether an earlier request was approved. Pay only after it is approved.
Annotations the server declares
- title: 承認されたか確認する
- readOnlyHint: true
- openWorldHint: false
Only reads 1Show 1 read-only tool
get_budgetこのAIが今日あといくら使えるか、1回の上限、自動承認ライン、使ってよい支払先を確認する。 / Check today's remaining budget, per-payment limit, auto-approve amount and allowed merchants.No findings
Why it is in this group
- The name "get_budget" says "get": a word for reading.
Description, as the server wrote it このAIが今日あといくら使えるか、1回の上限、自動承認ライン、使ってよい支払先を確認する。 / Check today's remaining budget, per-payment limit, auto-approve amount and allowed merchants.
Annotations the server declares
- title: 残りの予算を見る
- readOnlyHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 15, 2026, 13:21 UTC, unchanged since Nov 8, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (1 irreversible, 1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://zrphnuvrsldcycxtdftv.supabase.co/functions/v1/saifuban-mcp: tools/list returned 4 tools to an anonymous client, including request_payment (irreversible), check_payment_status (write)
Findings
Matches of fixed checks, with the text they matched.
The server marks "check_payment_status" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "check_payment_status" says "status": a word for reading.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.4.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http saifuban https://zrphnuvrsldcycxtdftv.supabase.co/functions/v1/saifuban-mcp --header 'Authorization: <your-authorization>'claude mcp add --transport http saifuban https://zrphnuvrsldcycxtdftv.supabase.co/functions/v1/saifuban-mcp --header 'Authorization: <your-authorization>'Run in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__saifuban__get_budget"
],
"ask": [
"mcp__saifuban__request_payment",
"mcp__saifuban__check_payment_status"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as saifuban. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.ut181749ut/saifuban/verify?hash=0dc28b9380381be3301669911e0886ce664b243719a30b1d2d554fdfef6320af" | jq -e '.changed == false'Pinned hash 0dc28b938038, from Nov 8, 2026, 13:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.ut181749ut/saifuban/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.ut181749ut/saifuban)Source: MCP Registry · repository. Synced Nov 8, 2026, 14:18 UTC.
Saifuban MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Saifuban MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 2 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Saifuban MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Saifuban MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: request_payment.
What tools does the Saifuban MCP server have?
- 3 tools: 1 irreversible, 1 write, 1 read. request_payment, check_payment_status and get_budget.
Does the Saifuban MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Saifuban MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Saifuban MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 8, 2026.