Pre-transaction token risk checks for autonomous agents on six chains. Read-only; paid via x402.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
π‘ Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
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.
π bitfence.ai Β· π Whitepaper Β· π @bitfenceai
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.
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.
| Category | What it covers |
|---|---|
| Exit Integrity | Honeypot behaviour (measured by bitfence's own transaction simulation on EVM chains), sell/transfer taxes and their modifiability, freeze authority, transfer blocking |
| Supply Integrity | Mint authority, hidden ownership, owner-editable balances, permanent delegates, upgradeable proxies, selfdestruct, metadata mutability |
| Liquidity Integrity | LP lock and burn status, unlock schedule, pool depth, deployer-held LP, pool age |
| Holder & Insider Risk | Top-holder share, deployer share, holder count, sniper/insider/bundler cohorts, holder wallet ages |
| Provenance | Deployer track record, observed prior rugs, vendor scam verdicts, launchpad lifecycle, verification registries |
| Market Integrity | Wash-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.
The same scoring engine is exposed through four interfaces. Each returns the
same RiskAssessment structure.
For integration details, contact info@bitfence.ai.
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.
See SECURITY.md for vulnerability disclosure.
No reviews yet β be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/bitfence-risk-oracle)<a href="https://allmcps.com/mcp/bitfence-risk-oracle"><img src="https://allmcps.com/api/badge/bitfence-risk-oracle?style=directory" alt="Bitfence Risk Oracle on AllMCPs" /></a>