Is the Zvmzaretsky Validation Suite MCP server down?

mcp-registry/io.github.zvmzaretsky/validation-suite · v1.0.0

Also listed as glama/zvmzaretsky/fabtally-valid-mcp-server

healthy
Last checked 2026-10-22 08:13 UTC · handshake 469ms

As of 2026-10-22 08:13 UTC, the Zvmzaretsky Validation Suite MCP server is up with a Glimind reliability score of 93/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 10 minutes.

uptime (30d checks)
100%
checks observed
4,192
outages (90d)
12
tools
5

Validation suite: EU VAT (VIES), IBAN mod-97, email (MX+disposable), geo place lookup, VIN decode.

Install Zvmzaretsky Validation Suite MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http zvmzaretsky-validation-suite-mcp-server https://valid.fabtally.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

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

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

Agent-readiness: B (84/100)

B (84/100): 0 error(s), 2 warning(s) across 5 tool(s); ~1,418 tokens of tool definitions.
Scores higher than 44% of 15,519 MCP servers Glimind has audited.
Its tool list costs an agent ~1,418 tokens per session — lighter than 60% of servers.
84 → 84 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints30
Token cost100
Client compatibility70
Protocol100
Reliability85
Stability100

What to fix (3)

5 of 5 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: decode_vin, geo_lookup, validate_email, validate_iban, validate_vat

Handshake + tools/list takes ~1,920 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

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: 4 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%2Fvalidation-suite/fixes

geo_lookup 1 change
{
  "name": "geo_lookup",
  "description": "PAID $0.002 (x402, USDC on Base). Resolve a place against a bundled open dataset (no per-day API limits). Give {query:\"Munich, Bavaria, Germany\"} OR {country, state, city} and get normalized names, ISO 3166-1/-2 codes, the country→subdivision→city hierarchy, population and coordinates, and confirmation the place exists. Without payment returns the x402 challenge; pass x_payment to settle.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {
      "city": {
        "type": "string",
        "description": "City name."
      },
      "query": {
        "type": "string",
        "description": "Free-text place, e.g. \"Munich, Bavaria, Germany\" or \"France\"."
      },
      "state": {
        "type": "string",
        "description": "State/province/subdivision name or code (within the country)."
      },
      "country": {
        "type": "string",
        "description": "Country name or ISO 3166-1 alpha-2/alpha-3 code."
      },
      "x_payment": {
        "type": "string",
        "description": "x402 payment payload (base64) for this PAID validation. 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": "Resolve a country / state / city to ISO codes (paid $0.002)"
}
validate_email 1 change
{
  "name": "validate_email",
  "description": "PAID $0.002 (x402, USDC on Base). Validate an email address: give {email} and get RFC-ish syntax validation, a LIVE MX-record (DNS) existence check, disposable/throwaway-domain detection (bundled blocklist), and a role-address flag (info@, admin@…). STATELESS and non-PII — the address is never stored and no SMTP mailbox is probed. Without payment returns the x402 challenge; pass x_payment to settle.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "email"
    ],
    "properties": {
      "email": {
        "type": "string",
        "description": "The email address to validate."
      },
      "x_payment": {
        "type": "string",
        "description": "x402 payment payload (base64) for this PAID validation. 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": "Validate an email: syntax + MX + disposable + role (paid $0.002)"
}
validate_iban 1 change
{
  "name": "validate_iban",
  "description": "PAID $0.001 (x402, USDC on Base). Validate an IBAN: give {iban} and get ISO 13616 length + mod-97 checksum validation, the country, the human-formatted grouping, and the bank identifier (e.g. German Bankleitzahl, UK bank code + sort code) extracted from the BBAN where derivable. Pure-offline. Without payment returns the x402 challenge.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "iban"
    ],
    "properties": {
      "iban": {
        "type": "string",
        "description": "The IBAN (spaces/dashes tolerated), e.g. DE89 3704 0044 0532 0130 00."
      },
      "x_payment": {
        "type": "string",
        "description": "x402 payment payload (base64) for this PAID validation. 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": "Validate an IBAN (mod-97) + extract bank code (paid $0.001)"
}

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

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

Tools (5)

Compare: most reliable data servers · most reliable search servers · most reliable email 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 Validation Suite MCP server down right now?

As of 2026-10-22 08:13 UTC, the Zvmzaretsky Validation Suite MCP server is up with a Glimind reliability score of 93/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 10 minutes.

How many tools does Zvmzaretsky Validation Suite MCP server provide?

Zvmzaretsky Validation Suite MCP server advertises 5 tools, including decode_vin, geo_lookup, validate_email, validate_iban, validate_vat.

How do I install Zvmzaretsky Validation Suite MCP server?

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

Is the Zvmzaretsky Validation Suite MCP server safe to connect to an AI agent?

Glimind scanned all 5 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 Validation Suite 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