bitfence Risk Oracle

io.github.bitfenceai由 GitHub 账号 bitfenceai 发布v0.7.7更新于 Oct 24, 2026

Pre-transaction token risk checks for autonomous agents on six chains. Read-only; paid via x402.

已验证Streamable HTTP可网页运行金融安全与监控

概览

AI 生成的概览

远程 MCP 风险预言机,为助手提供六条链上代币的交易前风险评分、建议与风险标记。

可以做什么
  • 评估代币整体风险:综合评分、风险等级、置信度、PROCEED / REQUIRE_HUMAN_APPROVAL / BLOCK 建议、理由及触发的标记。
  • 评估计划中的仓位:在完整风险评估之外,给出预估滑点、实际成本、最大安全仓位、组合集中度与 MEV 暴露。
  • 覆盖 Solana、Base、Ethereum、Arbitrum、BSC 与 HyperEVM,评分维度包括退出、供应、流动性、持有者、来源与市场完整性。
适用场景
当智能体即将兑换、转账或以其他方式与某代币交互,需要在行动前获得结构化安全检查时使用;也适合在确定仓位规模时,将滑点与集中度信息与风险结论一并参考。
运行要求
需要远程 MCP 端点;无需账户、API 密钥或注册。每次查询通过 x402 以 Base 上的 USDC 付费(风险查询 0.10,上下文查询 0.20),因此需要可进行 x402 支付的已充值钱包及网络访问。
安装前请注意
每次调用都会产生费用,自动化循环可能在无人监督下持续花费 USDC。该服务为只读,返回的是参考性评分而非保证;评分引擎为闭源,阈值与权重无法审计。代币地址与链标识会发送给第三方服务。

安装

在 SourceWeft 中

  1. 打开 控制台中的 bitfence Risk Oracle,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.bitfenceai%2Fbitfence/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "bitfence-risk-oracle": {
      "type": "http",
      "url": "https://api.bitfence.ai/mcp"
    }
  }
}

README

bitfence

The risk layer agents can't skip.

bitfence is a pre-transaction token risk oracle for autonomous AI agents operating on Solana, Base, Ethereum, Arbitrum, BSC, and HyperEVM. Before an agent swaps, transfers, or interacts with a token, bitfence returns a structured risk assessment in under a second: a composite score, confidence value, action recommendation, and any active circuit-breaker flags.

  • Live on Solana, Base, Ethereum, Arbitrum, BSC, and HyperEVM
  • HTTP API · MCP server · Rig (Rust) — Coinbase AgentKit coming soon
  • $0.10 per risk query in USDC on Base via x402 — no API keys

🔗 bitfence.ai · 📄 Whitepaper · 𝕏 @bitfenceai


Why this exists

Autonomous agents now hold keys, read mandates, and broadcast transactions without a human in the loop. The agent frameworks shipping today expose swap and transfer actions with no systematic pre-transaction safety check. The risk-assessment tooling that exists was built for a human reading a wallet pop-up — not a machine routing on structured fields.

bitfence fills the gap: a pre-intent token risk layer designed for machine consumption. Neutral, transparent, agent-native, per-call priced. It is complementary to existing wallet-grade tools, not competitive with them.

What it scores

Risk is decomposed into six categories — each a distinct mechanism by which a holder's position is destroyed — and assembled into a 0–100 composite with maturity-aware scoring and structured circuit-breaker overrides.

CategoryWhat it covers
Exit IntegrityHoneypot behaviour (measured by bitfence's own transaction simulation on EVM chains), sell/transfer taxes and their modifiability, freeze authority, transfer blocking
Supply IntegrityMint authority, hidden ownership, owner-editable balances, permanent delegates, upgradeable proxies, selfdestruct, metadata mutability
Liquidity IntegrityLP lock and burn status, unlock schedule, pool depth, deployer-held LP, pool age
Holder & Insider RiskTop-holder share, deployer share, holder count, sniper/insider/bundler cohorts, holder wallet ages
ProvenanceDeployer track record, observed prior rugs, vendor scam verdicts, launchpad lifecycle, verification registries
Market IntegrityWash-trade ratios, old-wallet flow share, price/volume divergence

Circuit breakers override the composite: measured threats (honeypot, confiscatory sell tax, selfdestruct) block even trusted tokens; heuristic flags floor the score for any token outside the curated trusted-token registry. The reported confidence value reflects only the data sources actually consulted, with cross-source disagreements excluded.

The full methodology is in the whitepaper.

Integration surfaces

The same scoring engine is exposed through four interfaces. Each returns the same RiskAssessment structure.

  • HTTP/JSON API — for any caller that speaks HTTP
  • MCP server — for tool-calling LLM agents (Claude Desktop, MCP-enabled IDEs)
  • Coinbase AgentKit — ActionProvider coming soon
  • Rig (Rust) — typed in-process tool binding for Rust-native agents

For integration details, contact [email protected].

Pricing and access

  • $0.10 per risk query, $0.20 per contextual query in USDC on Base via x402
  • Implemented against the Coinbase CDP facilitator
  • No accounts, no API keys, no signups
  • Listed on the Coinbase x402 Bazaar

Open-source posture

Documentation, whitepaper, and integration surfaces are open under Apache 2.0. The scoring engine source remains closed for security reasons: publishing exact circuit-breaker thresholds, signal weights, and maturity logic would let adversarial token deployers engineer tokens that sit immediately below the trigger points, defeating the protection bitfence provides to agents downstream. This trade-off is discussed in the whitepaper.

A publishable methodology document — one useful to other Ethereum security teams without exposing trigger logic to deployers — is in active development.

Security

See SECURITY.md for vulnerability disclosure.

License

Apache License 2.0

来源:README.md,提交 ff33298

工具

2

analyze_token

Full risk assessment for a token. Returns risk score (0-100), risk level, confidence, recommendation (PROCEED/REQUIRE_HUMAN_APPROVAL/BLOCK), reasoning, and flags triggered. Equivalent to GET /v1/risk/{chain}/{address}.

输入参数chain必填address必填

contextual_risk

Position-aware contextual risk assessment. Returns the full risk assessment plus position context: estimated slippage, effective cost, max safe position, portfolio concentration, and MEV exposure. Equivalent to POST /v1/risk/contextual.

输入参数chain必填address必填position_size_usd必填portfolio_size_usd必填

版本历史

1
  1. v0.7.7最新Sep 16, 2026

评分

已满足适用检查项的 100%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分