FabTally Chain MCP server
io.github.zvmzaretsky/fabtally-chainzvmzaretskystreamable-httpv1.0.0Scanned
On-chain monitoring reads: ENS/Basename expiry, gas, token unlocks & Chainlink oracle health.
4 tools: 4 change things.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
4 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the FabTally Chain MCP server can do
The FabTally Chain MCP server is published by the GitHub account zvmzaretsky. It has 4 tools. It can create or change data (4 tools: ens_expiry, gas, token_unlocks and oracle_health), but cannot delete data. None of its tools only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 1 finding (base64-blob). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 20, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
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.
What this check looks forMatched text
inputSchema.properties.feed_address.description: "...-hex), e.g. ETH/USD 0x5f4eC3Df9cbd43714FE2740f5E3616155c5b8419."
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.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:23 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 4
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://chain.fabtally.com/mcp: tools/list returned 4 tools to an anonymous client, including ens_expiry (write), gas (write), token_unlocks (write), oracle_health (write)
Findings
Matches of fixed checks, with the text they matched.
- Warnoracle_health
The input schema at properties.feed_address.description contains a 42-character base64 string.
What this check looks forMatched text
inputSchema.properties.feed_address.description: "...-hex), e.g. ETH/USD 0x5f4eC3Df9cbd43714FE2740f5E3616155c5b8419."
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
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/mcpclaude mcp add --transport http fabtally-chain https://chain.fabtally.com/mcpRun 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.
{
"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.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.zvmzaretsky/fabtally-chain/verify?hash=6ea8224036d8624e8784091e5bd41c80a7c183f9d2bc2cec9f4486d27c917a65" | jq -e '.changed == false'Pinned hash 6ea8224036d8, from Nov 20, 2026, 20:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.zvmzaretsky/fabtally-chain/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.zvmzaretsky/fabtally-chain)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:52 UTC.
FabTally Chain MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the FabTally Chain MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 4 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the FabTally Chain MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the FabTally Chain MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the FabTally Chain MCP server have?
- 4 tools: 4 write. ens_expiry, gas, token_unlocks and oracle_health.
Does the FabTally Chain MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the FabTally Chain MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the FabTally Chain MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.