Is the Zvmzaretsky Fabtally Guard MCP server down?

mcp-registry/io.github.zvmzaretsky/fabtally-guard · v1.0.0

Also listed as glama/zvmzaretsky/fabtally-guard

healthy
Last checked 2026-10-24 04:00 UTC · handshake 479ms

As of 2026-10-24 04:00 UTC, the Zvmzaretsky Fabtally Guard MCP server is up with a Glimind reliability score of 94/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 11 outages in 90 days, with a median recovery of 10 minutes.

uptime (30d checks)
100%
checks observed
4,487
outages (90d)
11
tools
4

Verify before you act: deps-check, x402-preflight, json-repair & url-read for agents.

Install Zvmzaretsky Fabtally Guard MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http zvmzaretsky-fabtally-guard-mcp-server https://guard.fabtally.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "zvmzaretsky-fabtally-guard-mcp-server": {
      "type": "http",
      "url": "https://guard.fabtally.com/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: B (81/100)

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

What to fix (3)

4 of 4 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: deps_check, json_repair, url_read, x402_preflight

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: x402_preflight

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%2Ffabtally-guard/fixes

deps_check 1 change
{
  "name": "deps_check",
  "description": "PAID $0.003 (x402, USDC on Base). Vet a software package BEFORE installing it. Returns existence, latest-vs-requested, deprecation/yank markers, known CVEs from OSV.dev, typosquat similarity to popular names, SPDX license, and age/download signals with a plain-English risk verdict. Args: ecosystem (npm|pypi|crates), name, version (optional). Without payment returns the x402 challenge; pass x_payment to settle.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "ecosystem",
      "name"
    ],
    "properties": {
      "name": {
        "type": "string",
        "description": "Package name, e.g. 'lodash', 'requests', 'serde'."
      },
      "version": {
        "type": "string",
        "description": "Specific version to check for CVEs (optional; defaults to latest)."
      },
      "ecosystem": {
        "enum": [
          "npm",
          "pypi",
          "crates"
        ],
        "type": "string",
        "description": "Package ecosystem: npm | pypi | crates."
      },
      "x_payment": {
        "type": "string",
        "description": "x402 payment payload (base64) for this PAID check. 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": "Vet a dependency before install (paid $0.003)"
}
url_read 1 change
{
  "name": "url_read",
  "description": "PAID $0.004 (x402, USDC on Base). Fetch a PUBLIC url and return clean Markdown + a token estimate for RAG ingestion — readability extraction, boilerplate stripped. Respects robots.txt, public pages only, no login/paywall bypass, nothing stored. Args: url. Without payment returns the x402 challenge; pass x_payment to settle.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "url"
    ],
    "properties": {
      "url": {
        "type": "string",
        "description": "The public web page URL to fetch and convert to Markdown."
      },
      "x_payment": {
        "type": "string",
        "description": "x402 payment payload (base64) for this PAID check. 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": "Public url -> clean Markdown + token count (paid $0.004)"
}
x402_preflight 1 change
{
  "name": "x402_preflight",
  "description": "PAID $0.002 (x402, USDC on Base). Verify another x402 endpoint BEFORE paying it: does an unpaid call return a valid x402 v2 402 challenge? do the quoted amount/asset/network/payTo match the site's /.well-known/x402? is TLS valid, host reachable, openapi present? Returns pass/fail + per-check reasons + the parsed price you would pay. Args: url. Without payment returns the x402 challenge; pass x_payment to settle.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "url"
    ],
    "properties": {
      "url": {
        "type": "string",
        "description": "The x402 endpoint URL to verify, e.g. https://example.com/v1/thing."
      },
      "x_payment": {
        "type": "string",
        "description": "x402 payment payload (base64) for this PAID check. 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": false,
    "idempotentHint": false
  },
  "title": "Verify an x402 endpoint before paying (paid $0.002)"
}

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/fabtally-guard"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.zvmzaretsky/fabtally-guard"}) 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%2Ffabtally-guard.svg)](https://glimind.com/server/mcp-registry%2Fio.github.zvmzaretsky%2Ffabtally-guard?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.zvmzaretsky%2Ffabtally-guard?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.zvmzaretsky%2Ffabtally-guard.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.zvmzaretsky%2Ffabtally-guard.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.zvmzaretsky%2Ffabtally-guard?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:319e32db0cc6b0e5…, first seen 2026-10-17, included at leaf 2078 of 56,397. Version history · verify what your client received.

Tools (4)

Compare: most reliable security servers · most reliable data servers · most reliable web servers · most reliable payments 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 Fabtally Guard MCP server down right now?

As of 2026-10-24 04:00 UTC, the Zvmzaretsky Fabtally Guard MCP server is up with a Glimind reliability score of 94/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 11 outages in 90 days, with a median recovery of 10 minutes.

How many tools does Zvmzaretsky Fabtally Guard MCP server provide?

Zvmzaretsky Fabtally Guard MCP server advertises 4 tools, including deps_check, json_repair, url_read, x402_preflight.

How do I install Zvmzaretsky Fabtally Guard MCP server?

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

Is the Zvmzaretsky Fabtally Guard MCP server safe to connect to an AI agent?

Glimind scanned all 4 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 Fabtally Guard 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