bitfence
MCP serverAI & modelsBitfence lets your AI check how risky a token is before it makes a transaction, across six blockchains. Checks are read-only, so nothing is moved or executed when one runs. Payment for checks is handled through x402.
Use bitfence in Claude, ChatGPT or Ahel Desktop
Free. Sign in, add bitfence and connect your AI. About a minute.
Also: Claude Code · Cursor · Codex
Then ask your AI: use bitfence to analyze token
No key or account is asked for. Not verified by us yet: Ahel has not run a call through it.
Details
Available today. Use it from your connected AI after setup.
No key or account is asked for. Not verified by us yet: Ahel has not run a call through it.
Add bitfence, then ask your AI to run a risk check on any token it plans to transact with. Checks are paid via x402.
What your AI can do with it
- Check a token's risk before a transaction goes through
- Screen tokens across six blockchains
- Run risk checks automatically before acting on a token
- Get risk information without moving funds or executing anything, since checks are read-only
Install bitfence
The server’s own address, for the clients that take one directly. Or connect Ahel once and every client you use reads it from one address, with the account kept on Ahel rather than in each client’s config.
Claude Code
claude mcp add --transport http --scope user bitfence 'https://api.bitfence.ai/mcp'Run it once in your project, then open /mcp to approve any sign-in the server asks for.
Claude Desktop
https://api.bitfence.ai/mcpAdd a custom connector in Settings, paste this address, and approve the sign-in.
Cursor
cursor://anysphere.cursor-deeplink/mcp/install?name=bitfence&config=eyJ1cmwiOiJodHRwczovL2FwaS5iaXRmZW5jZS5haS9tY3AifQ==Open the link and Cursor adds the server at that address.
ChatGPT
https://api.bitfence.ai/mcpIn Settings, enable Developer mode, create an MCP app, and paste this address. Your plan and workspace must allow custom apps.
Codex
codex mcp add bitfence --url 'https://api.bitfence.ai/mcp'Run it once, then sign in with codex mcp login bitfence if the server asks for an account.
From the project's README
As published by bitfenceai/bitfence in README.md.
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.
| 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.
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 info@bitfence.ai.
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
Tools it offers (2)
What this server listed when Ahel dialed its public endpoint in Oct 2026, with no key and no account of yours. The names are the server’s own.
analyze_tokencontextual_risk
Signals
- GitHub stars
- 1
- Last commit
- Aug 2026
Advanced
- Delivery
- bitfence MCP server → your Ahel connector (mcp.ahel.ai) → your AI.
- Item type
- mcp-server
- Key
io-github-bitfenceai-bitfence- Source
- github.com/bitfenceai/bitfence
- Hosted endpoint
https://api.bitfence.ai/mcp
github.com/bitfenceai/bitfence
More in AI & models
MCP server · upstash
More in AI & modelsAdButler
MCP server · adbutler
More in AI & modelsatom-mcp-server
MCP server · a7om-ai
More in AI & modelsottasia
MCP server · aiweather-anurag
More in AI & modelsunphurl
MCP server · 123ergo
More in AI & modelsmicrosoft-learn-mcp
MCP server · microsoftdocs
More in AI & models