
Frisk
dev.tryfrisk由 tryfrisk.dev 發布v0.0.1更新於 Oct 24, 2026
Screen the counterparty of an x402 payment before an agent pays it. Runs offline by default.
概覽
Frisk 是一個本機 MCP 伺服器,讓助理在 x402 付款前篩查交易對手,並回傳允許、複核或阻擋的結論。
- 可以做什麼
- 篩查付款對手方:對代理打算支付的地址執行確定性檢查,包括地址合理性與動態 payTo 比對,回傳結論、原因、信任分與信心度。檢查傳輸與政策:標記明文端點,並套用自訂的單次支出上限、允許資產與嚴格程度。離線或託管執行:無設定時完全在本機篩查;設定 API 金鑰後同一工具由託管服務回應並加入信譽訊號。
- 適用情境
- 適用於代理即將向 x402 對手方付款、需要先做一次檢查的情境,或代理無法引入 Frisk 篩查函式庫時。README 指出,模型可以跳過的檢查,保障弱於放在簽署付款程式路徑上的檢查。
- 執行需求
- 透過 npx 以 stdio 本機程序執行,需要 Node.js。離線篩查不需帳號、API 金鑰或網路呼叫。選用的託管模式需要 FRISK_API_KEY,並可用 FRISK_BASE_URL 覆寫預設託管端點。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Frisk,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。
其他 MCP 客戶端
參照 儲存庫 中的啟動說明。
README
frisk-mcp
An MCP server for Frisk: screen the counterparty of an x402 payment before an agent pays it.
It exposes one tool, screen_payment, which runs Frisk's deterministic checks —
address sanity, dynamic-payTo comparison, transport safety, and your own
spending policy — and returns allow / review / block with reasons.
Where this belongs, and where it does not
An MCP tool runs when a model decides to call it. A payment check that the model can skip is a weaker guarantee than the same check on the code path that signs the payment.
So:
- Use the library —
frisk-screen— where the money actually moves. It is MIT, dependency-free, and runs locally. - Use this server for inspection ("is this address safe to pay?"), and for agents that cannot import a library.
Frisk is advisory in both cases: it returns a verdict and your code decides. It never holds funds and cannot stop a payment by itself.
Install
In any MCP client's server configuration:
No API key, no account, no network call: with no configuration the server screens entirely on your machine.
Hosted mode (optional)
Set FRISK_API_KEY to have the same tool answered by the hosted service, which
adds reputation-graph signals and returns higher-confidence verdicts:
The hosted tier is in early access — email [email protected]. Everything above works without it.
The tool
screen_payment
Returns verdict, trustScore, confidence, reasons, policyHits,
source (lite or hosted), and allowed.
What it does not do
It does not detect Sybil clusters, and offline it has no view of an address's
history — lite screening always reports "low" confidence for that reason. It
also cannot repair the protocol underneath a payment: replay, settlement races,
and facilitator trust live in x402 itself, not in the request being signed.
Those limits are discussed in
Five ways an x402 payment can go wrong.
License
MIT
來源:mcp/README.md,提交 168d7f8
工具
0版本歷史
1- v0.0.1最新Sep 16, 2026
評分
已滿足適用檢查項的 50%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通25 分
請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。
- 已宣告認證方式10 分
請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分