Skip to content

FabTally Chain

by zvmzaretsky · remote · no sign-in to list tools · v1.0.0 · published by GitHub user zvmzaretsky

On-chain monitoring reads: ENS/Basename expiry, gas, token unlocks & Chainlink oracle health.

Changes · 4
CompareRegistry entry

4 tools: 4 change things.

Scanned Oct 21, 2026

1 check matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http fabtally-chain https://chain.fabtally.com/mcp

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • Warnoracle_health

    The input schema at properties.feed_address.description contains a 42-character base64 string.

    Matched text

    inputSchema.properties.feed_address.description: "...-hex), e.g. ETH/USD 0x5f4eC3Df9cbd43714FE2740f5E3616155c5b8419."

    What this check looks for

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

4 tools

Changes things 4Claude Code: ask
  • ens_expiryPAID $0.001 (x402, USDC on Base).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    PAID $0.001 (x402, USDC on Base). Resolve an ENS .eth or Basename .base.eth name's registration expiry ON-CHAIN (public RPC). Returns expiry date, days-left, whether it's in the 90-day grace period, the release date it becomes registrable again, and the current owner. Read-only, descriptive. Args: name. Without payment returns the x402 challenge; pass x_payment to settle.
  • gasPAID $0.001 (x402, USDC on Base).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    PAID $0.001 (x402, USDC on Base). Current gas for a chain via public RPC: base fee + suggested priority + suggested max fee (gwei) at the latest block. If below_gwei is set, also returns whether the base fee is at/below your threshold right now. Read-only. Args: chain (ethereum|base|arbitrum|polygon|bsc|optimism), below_gwei (optional). Without payment returns the x402 challenge; pass x_payment to settle.
  • oracle_healthPAID $0.003 (x402, USDC on Base).1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    Findings

    • Warn

      The input schema at properties.feed_address.description contains a 42-character base64 string.

      Matched text

      inputSchema.properties.feed_address.description: "...-hex), e.g. ETH/USD 0x5f4eC3Df9cbd43714FE2740f5E3616155c5b8419."

      What this check looks for
    Description, as the server wrote it
    PAID $0.003 (x402, USDC on Base). Chainlink price-feed health via public RPC: last-update age, latest answer (scaled by decimals), round monotonicity (is the answer current?), a stale flag vs the heartbeat, optional deviation vs a reference price, and per-factor flags. Read-only, descriptive. Args: feed_address, chain, heartbeat_seconds (optional), reference (optional). Without payment returns the x402 challenge; pass x_payment.
  • token_unlocksPAID $0.003 (x402, USDC on Base).No findings

    Why it is in this group

    • The name "token_unlocks" says "unlock": a word for a change.
    Description, as the server wrote it
    PAID $0.003 (x402, USDC on Base). Next token vesting/unlock event(s) from DefiLlama's PUBLIC emissions dataset: upcoming unlock date(s), token amount, and % of max supply, with a human description. Cleanly says so when a token has no public unlock schedule. Read-only, descriptive — NOT a price signal. Args: token (symbol, protocol name, or contract address), chain (optional, for address lookup). Without payment returns the x402 challenge; pass x_payment to settle.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http fabtally-chain https://chain.fabtally.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__fabtally-chain__ens_expiry",
      "mcp__fabtally-chain__gas",
      "mcp__fabtally-chain__token_unlocks",
      "mcp__fabtally-chain__oracle_health"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as fabtally-chain. Review it before you use it.