FabTally Safe

Official registry Finance and payments

Read-only crypto safety: token honeypot checks, EIP-712 signature decode, approval scans.

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code
claude mcp add --transport http fabtally-safe 'https://safe.fabtally.com/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "fabtally-safe": {
            "type": "http",
            "url": "https://safe.fabtally.com/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. FabTally Safe — MCP server
  2. Tools
  3. Payment
  4. Transports
  5. Config

FabTally Safe — MCP server

Read-only crypto safety + "what am I signing" verification for AI agents and wallets. Fronts the FabTally Safe HTTP API (https://safe.fabtally.com).

  • Read-only. Never holds, moves, signs for, or broadcasts funds. No private key. Outputs are descriptive facts from public sources — not financial advice.
  • 8 tools: 4 free teasers + 4 paid (x402, USDC on Base).

Tools

ToolTierWhat it does
token_safetypaid $0.02Multi-chain token honeypot/rug check — aggregates GoPlus + honeypot.is into a 0-100 risk score with explainable reasons.
decode_signaturepaid $0.01"What am I signing" — decode EIP-712 / Permit / Permit2 / Seaport typed-data into plain English + risk flags (unlimited approval, malicious spender, expiry, NFT-drain).
approvalspaid $0.01Wallet approval-risk scan ranked by exposure + address-poisoning "revoke bait" detection + the revoke calldata you execute yourself.
simulatepaid $0.02Keyless pre-sign transaction analysis: eth_call revert check + static delta prediction + risk flags.
token_safety_free · decode_signature_free · approvals_free · simulate_freefreeReal teaser results, no wallet.

Chains: ethereum, base, bsc, polygon, arbitrum, optimism (honeypot.is signals on ethereum/base/bsc).

Payment

Paid tools use x402 (USDC on Base, eip155:8453). Call a paid tool with no x_payment to receive the decoded 402 challenge (price, network, asset, payTo); build an x402 authorization and call again with the token in x_payment. Humans can instead prepay by card and use an X-FabTally-Key credit header on the HTTP API.

Transports

  • stdio (default): node index.js — for Claude Desktop and local MCP clients.
  • streamable-http: MCP_HTTP_PORT=8113 node http.js — hosted at https://safe.fabtally.com/mcp.

Config

  • FABTALLY_SAFE_BASE — API base (default https://safe.fabtally.com).

Operator: Sunstone Soft · https://fabtally.com · Not financial advice · read-only.

Frequently asked questions

What is FabTally Safe?

Read-only crypto safety: token honeypot checks, EIP-712 signature decode, approval scans.

How do I install FabTally Safe?

It runs as a remote server. In Claude Code: claude mcp add --transport http fabtally-safe 'https://safe.fabtally.com/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does FabTally Safe need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is FabTally Safe open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains FabTally Safe?

It is published by zvmzaretsky. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.