FabTally Safe
REMOTE · SAFE.FABTALLY.COM · SCANNED SEP 20
Read-only crypto safety: token honeypot checks, EIP-712 signature decode, approval scans.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1273 tokens (~159/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the FabTally Safe MCP server?
FabTally Safe is a hosted endpoint at https://safe.fabtally.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · safe.fabtally.com
claude mcp add --transport http zvmzaretsky-crypto-safety 'https://safe.fabtally.com/mcp'
{
"mcpServers": {
"zvmzaretsky-crypto-safety": {
"url": "https://safe.fabtally.com/mcp"
}
}
} {
"servers": {
"zvmzaretsky-crypto-safety": {
"type": "http",
"url": "https://safe.fabtally.com/mcp"
}
}
} [mcp_servers.zvmzaretsky-crypto-safety] url = "https://safe.fabtally.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"zvmzaretsky-crypto-safety": {
"type": "remote",
"url": "https://safe.fabtally.com/mcp",
"enabled": true
}
}
} openclaw mcp add zvmzaretsky-crypto-safety --url 'https://safe.fabtally.com/mcp' --transport streamable-http
mcp_servers:
zvmzaretsky-crypto-safety:
url: "https://safe.fabtally.com/mcp" {
"McpServers": {
"zvmzaretsky-crypto-safety": {
"Transport": "http",
"Url": "https://safe.fabtally.com/mcp"
}
}
} assistant mcp add zvmzaretsky-crypto-safety -t streamable-http -u 'https://safe.fabtally.com/mcp'
{
"mcpServers": {
"zvmzaretsky-crypto-safety": {
"type": "http",
"url": "https://safe.fabtally.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 31 Aug 26 +1
- Stability: 0.97 → pass security
- 29 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 2 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 1 Aug 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://safe.fabtally.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=safe.fabtally.com | CN=YR2,O=Let's Encrypt,C=US | 1 Aug 2026 | 30 Oct 2026 | RSA 2048 | SHA256-RSA | 5af80a72d51ef16570e9ea23cf4b1abe4ea |
| SANs: safe.fabtally.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of safe.fabtally.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| fabtally.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://safe.fabtally.com/mcp | Verified | 200 | |
| http (plaintext) | http://safe.fabtally.com/mcp | HTTPS enforced | 301 | https://safe.fabtally.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
approvals Wallet approval-risk scan + revoke calldata (paid $0.01) ~190
PAID $0.01 (x402, USDC on Base). Scan a wallet's ERC-20/721 approvals ranked by exposure; flags unlimited amounts, unverified/known-malicious spenders, and address-poisoning 'fake-approval revoke bait'; returns the exact revoke calldata you execute YOURSELF (never executed/broadcast by us). Without payment returns the x402 challenge; pass x_payment. Free teaser: approvals_free.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | 0x wallet address to scan. |
| chain | string | yes | Chain: ethereum | base | bsc | polygon | arbitrum | optimism. |
| x_payment | string | – | x402 payment payload (base64) for this PAID tool. If supplied it is forwarded as the X-PAYMENT header to settle the call and return the real result instead of a 402 challenge. Omit to get the price c… |
No output schema declared.
No examples provided.
approvals_free Approvals — counts + top-3 risks (FREE) ~80
FREE. Approval counts + top-3 riskiest spenders for {address, chain}. Real result, no wallet. Upgrade to approvals for EVERY approval ranked + revoke calldata.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | 0x wallet address to scan. |
| chain | string | yes | Chain: ethereum | base | bsc | polygon | arbitrum | optimism. |
No output schema declared.
No examples provided.
decode_signature Decode 'what am I signing' EIP-712 signature (paid $0.01) ~220
PAID $0.01 (x402, USDC on Base). Decode an off-chain EIP-712 typed-data signature (Permit / Permit2 / Seaport / generic) into plain English with risk flags: unlimited approval, unknown/known-malicious spender, never-expiring or already-expired deadlines, zero-consideration NFT-drain orders. Off-chain signatures are the top wallet-drainer vector. Pure offline decode — never signs/broadcasts. Without payment returns the x402 challenge; pass x_payment. Free teaser: decode_signature_free.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | Optional chain override (else read from domain.chainId). |
| typed_data | object | yes | EIP-712 typed data object: {domain, types, primaryType, message}. |
| x_payment | string | – | x402 payment payload (base64) for this PAID tool. If supplied it is forwarded as the X-PAYMENT header to settle the call and return the real result instead of a 402 challenge. Omit to get the price c… |
No output schema declared.
No examples provided.
decode_signature_free Signature decode — type + summary + risk level (FREE) ~98
FREE. Type + plain-English summary + risk level for an EIP-712 `typed_data`. Real result, no wallet. Upgrade to decode_signature for the full field-by-field decode + all risk flags + malicious-spender screening.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | Optional chain override (else read from domain.chainId). |
| typed_data | object | yes | EIP-712 typed data object: {domain, types, primaryType, message}. |
No output schema declared.
No examples provided.
simulate Keyless pre-sign transaction simulation (paid $0.02) ~244
PAID $0.02 (x402, USDC on Base). Keyless pre-sign analysis of {chain, from?, to, data, value?}: public-RPC eth_call revert check + static calldata decode predicting approval/transfer deltas + risk flags (unlimited approval, approval-for-all, reverts). Honest keyless limitation stated in the response (no full fork trace). Without payment returns the x402 challenge; pass x_payment. Free teaser: simulate_free.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Chain: ethereum | base | bsc | polygon | arbitrum | optimism. |
| data | string | – | 0x calldata (omit for a plain value transfer). |
| from | string | – | 0x sender (optional but improves accuracy). |
| to | string | yes | 0x target contract/recipient. |
| value | string | – | Value in wei (optional). |
| x_payment | string | – | x402 payment payload (base64) for this PAID tool. If supplied it is forwarded as the X-PAYMENT header to settle the call and return the real result instead of a 402 challenge. Omit to get the price c… |
No output schema declared.
No examples provided.
simulate_free Simulate — method + revert + risk level (FREE) ~127
FREE. Method + revert flag + risk level + predicted effect types for a transaction. Real result, no wallet. Upgrade to simulate for the full predicted deltas + all risk flags.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Chain: ethereum | base | bsc | polygon | arbitrum | optimism. |
| data | string | – | 0x calldata (omit for a plain value transfer). |
| from | string | – | 0x sender (optional but improves accuracy). |
| to | string | yes | 0x target contract/recipient. |
| value | string | – | Value in wei (optional). |
No output schema declared.
No examples provided.
token_safety Token honeypot / rug safety check (paid $0.02) ~228
PAID $0.02 (x402, USDC on Base). Multi-chain token honeypot/rug check aggregating GoPlus token-security + honeypot.is buy/sell-tax simulation into a normalized 0-100 risk score with explainable reasons: honeypot/can't-sell, buy/sell tax, mint/blacklist/pausable/ownership privileges, top-holder concentration, LP-lock, contract verified/bytecode. Descriptive facts only — NOT a buy/sell signal. Without payment returns the x402 challenge; pass x_payment to settle. Free teaser: token_safety_free.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | 0x token contract address. |
| chain | string | yes | Chain: ethereum | base | bsc | polygon | arbitrum | optimism. |
| x_payment | string | – | x402 payment payload (base64) for this PAID tool. If supplied it is forwarded as the X-PAYMENT header to settle the call and return the real result instead of a 402 challenge. Omit to get the price c… |
No output schema declared.
No examples provided.
token_safety_free Token safety — score band + top-line flags (FREE) ~86
FREE. Score band + top-line honeypot/tax/privilege flags for a token {address, chain}. Real result, no wallet. Upgrade to token_safety for the full numeric breakdown.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | 0x token contract address. |
| chain | string | yes | Chain: ethereum | base | bsc | polygon | arbitrum | optimism. |
No output schema declared.
No examples provided.
What is the FabTally Safe MCP server?
FabTally Safe is an MCP server listed in the public MCP registry as io.github.zvmzaretsky/crypto-safety. Read-only crypto safety: token honeypot checks, EIP-712 signature decode, approval scans. This page covers its hosted endpoint (https://safe.fabtally.com/mcp).
Is the FabTally Safe MCP server safe to use?
FabTally Safe scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the FabTally Safe MCP server expose?
FabTally Safe exposes 8 tools: token_safety, token_safety_free, decode_signature, decode_signature_free, approvals, and 3 more. Their descriptions and schemas cost roughly 1,273 tokens of context every time the server is loaded.
Does the FabTally Safe MCP server require authentication?
No. We connected to FabTally Safe without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the FabTally Safe MCP server still maintained?
FabTally Safe is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.