
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 分