Security & Testing

bitfence.ai

Pre-transaction risk scoring for AI agents on Solana and Base, providing a score, recommendation, and reason before signing transactions.

x402 supported1 endpoint0 known toolsFirst detected July 25, 2026Last detected July 29, 2026

ENDPOINT 1

https://api.bitfence.ai/mcp

No auth detected

No tool metadata was available in the registry cache.

CONNECT WITH APPROVAL

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.bitfence-ai]
url = "https://api.bitfence.ai/mcp"
enabled = true

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: bitfence-ai
Remote MCP URL: https://api.bitfence.ai/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "bitfence-ai": {
      "url": "https://api.bitfence.ai/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

{
  "name": "bitfence-ai",
  "transport": "streamable-http",
  "url": "https://api.bitfence.ai/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

BuiltWith Trust API v2 evidence for bitfence.ai was fetched 2026-08-02T15:39:21.706Z.

Trust status Trusted

bitfence.ai is assessed as Trusted: Domain runs a meaningful technology spend, consistent with a real business.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.