Is the Zvmzaretsky Crypto Safety MCP server down?

mcp-registry/io.github.zvmzaretsky/crypto-safety · v1.0.0

Also listed as glama/zvmzaretsky/fabtally-safe

healthy
Last checked 2026-10-26 22:06 UTC · handshake 555ms

As of 2026-10-26 22:06 UTC, the Zvmzaretsky Crypto Safety MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 12 outages in 90 days, with a median recovery of 6 minutes.

uptime (30d checks)
100%
checks observed
4,905
outages (90d)
12
tools
8

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

Point your MCP client at this streamable-http endpoint: https://safe.fabtally.com/mcp

Agent-readiness: B (82/100)

B (82/100): 0 error(s), 2 warning(s) across 8 tool(s); ~1,982 tokens of tool definitions.
Scores higher than 36% of 15,763 MCP servers Glimind has audited.
Its tool list costs an agent ~1,982 tokens per session — lighter than 55% of servers.
81 → 82 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints10
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (3)

8 of 8 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: approvals, approvals_free, decode_signature, decode_signature_free, simulate and 3 more

1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: approvals

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 3 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.zvmzaretsky%2Fcrypto-safety/fixes

approvals 1 change 
{
  "name": "approvals",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "address",
      "chain"
    ],
    "properties": {
      "chain": {
        "type": "string",
        "description": "Chain: ethereum | base | bsc | polygon | arbitrum | optimism."
      },
      "address": {
        "type": "string",
        "description": "0x wallet address to scan."
      },
      "x_payment": {
        "type": "string",
        "description": "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 challenge first."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": true,
    "idempotentHint": false
  },
  "title": "Wallet approval-risk scan + revoke calldata (paid $0.01)"
}
approvals_free 1 change 
{
  "name": "approvals_free",
  "description": "FREE. Approval counts + top-3 riskiest spenders for {address, chain}. Real result, no wallet. Upgrade to approvals for EVERY approval ranked + revoke calldata.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "address",
      "chain"
    ],
    "properties": {
      "chain": {
        "type": "string",
        "description": "Chain: ethereum | base | bsc | polygon | arbitrum | optimism."
      },
      "address": {
        "type": "string",
        "description": "0x wallet address to scan."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Approvals — counts + top-3 risks (FREE)"
}
token_safety 1 change 
{
  "name": "token_safety",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "address",
      "chain"
    ],
    "properties": {
      "chain": {
        "type": "string",
        "description": "Chain: ethereum | base | bsc | polygon | arbitrum | optimism."
      },
      "address": {
        "type": "string",
        "description": "0x token contract address."
      },
      "x_payment": {
        "type": "string",
        "description": "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 challenge first."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Token honeypot / rug safety check (paid $0.02)"
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.zvmzaretsky/crypto-safety"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.zvmzaretsky/crypto-safety"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown 
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.zvmzaretsky%2Fcrypto-safety.svg)](https://glimind.com/server/mcp-registry%2Fio.github.zvmzaretsky%2Fcrypto-safety?ref=badge)
HTML 
<a href="https://glimind.com/server/mcp-registry%2Fio.github.zvmzaretsky%2Fcrypto-safety?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.zvmzaretsky%2Fcrypto-safety.svg" alt="MCP agent-readiness"></a>
reStructuredText 
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.zvmzaretsky%2Fcrypto-safety.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.zvmzaretsky%2Fcrypto-safety?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:748b549d5107d92a…, first seen 2026-10-17, included at leaf 3382 of 75,736. Version history · verify what your client received.

Tools (8)

Compare: most reliable security servers · most reliable finance servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Zvmzaretsky Crypto Safety MCP server down right now?

As of 2026-10-26 22:06 UTC, the Zvmzaretsky Crypto Safety MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 12 outages in 90 days, with a median recovery of 6 minutes.

How many tools does Zvmzaretsky Crypto Safety MCP server provide?

Zvmzaretsky Crypto Safety MCP server advertises 8 tools, including approvals, approvals_free, decode_signature, decode_signature_free, simulate.

How do I install Zvmzaretsky Crypto Safety MCP server?

Point your MCP client at this streamable-http endpoint: https://safe.fabtally.com/mcp

Is the Zvmzaretsky Crypto Safety MCP server safe to connect to an AI agent?

Glimind scanned all 8 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Zvmzaretsky Crypto Safety MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve