# FabTally Valid (remote · valid.fabtally.com)

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

- Trust score: 61/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `valid.fabtally.com`: 61/100 (this document), [markdown](https://verifymcp.io/servers/zvmzaretsky-validation-suite/valid.md), [page](https://verifymcp.io/servers/zvmzaretsky-validation-suite/valid)

## Channel facts

- Endpoint: `https://valid.fabtally.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1010 tokens (~202/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

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

### Codex

```toml
[mcp_servers.zvmzaretsky-validation-suite]
url = "https://valid.fabtally.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "zvmzaretsky-validation-suite": {
      "type": "remote",
      "url": "https://valid.fabtally.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add zvmzaretsky-validation-suite --url https://valid.fabtally.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  zvmzaretsky-validation-suite:
    url: "https://valid.fabtally.com/mcp"
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-02 (score 60, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-08-01 (score 60)

First indexed and scored.

## MCP tools (5)

### `validate_vat` (~222 tokens)

Validate an EU VAT number via VIES (paid $0.003)

PAID $0.003 (x402, USDC on Base). FLAGSHIP. Validate an EU/EEA VAT number: give {country_code, vat_number} and get a per-country format + checksum pre-check AND a LIVE lookup against the official VIES service — returning valid/registered plus the registered company name & address when VIES provides them (cached ~1h to shield the flaky VIES). Without payment returns the x402 challenge; pass x_payment to settle.

Input parameters:

- `country_code` (string, required): 2-letter EU VAT country code (e.g. IE, DE, FR; GB/XI for Northern Ireland; GR accepted as EL).
- `vat_number` (string, required): The VAT number without the country prefix (prefix is tolerated and stripped).
- `x_payment` (string): 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 p…

### `validate_iban` (~191 tokens)

Validate an IBAN (mod-97) + extract bank code (paid $0.001)

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.

Input parameters:

- `iban` (string, required): The IBAN (spaces/dashes tolerated), e.g. DE89 3704 0044 0532 0130 00.
- `x_payment` (string): 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 p…

### `validate_email` (~178 tokens)

Validate an email: syntax + MX + disposable + role (paid $0.002)

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.

Input parameters:

- `email` (string, required): The email address to validate.
- `x_payment` (string): 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 p…

### `geo_lookup` (~240 tokens)

Resolve a country / state / city to ISO codes (paid $0.002)

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.

Input parameters:

- `city` (string): City name.
- `country` (string): Country name or ISO 3166-1 alpha-2/alpha-3 code.
- `query` (string): Free-text place, e.g. "Munich, Bavaria, Germany" or "France".
- `state` (string): State/province/subdivision name or code (within the country).
- `x_payment` (string): 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 p…

### `decode_vin` (~179 tokens)

Decode a VIN via NHTSA vPIC (paid $0.002)

PAID $0.002 (x402, USDC on Base). Decode a Vehicle Identification Number: give {vin} and get a 17-char format + North-American check-digit validation and a full decode via NHTSA's public vPIC API — make, model, year, body class, engine, plant country and more. VIN-only (never plate→owner). Without payment returns the x402 challenge; pass x_payment to settle.

Input parameters:

- `vin` (string, required): A 17-character Vehicle Identification Number (excludes I, O, Q).
- `x_payment` (string): 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 p…

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/zvmzaretsky-validation-suite/valid#diagnostics

## Score history

- 2026-08-03: 61
- 2026-08-02: 60
- 2026-08-01: 60

## Links

- Remote endpoint: https://valid.fabtally.com/mcp
- Repository: https://github.com/zvmzaretsky/validation-suite-mcp
- Website: https://valid.fabtally.com/
- Changelog RSS feed: https://verifymcp.io/servers/zvmzaretsky-validation-suite/valid/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/zvmzaretsky-validation-suite/valid/changelog.json
- HTML version of this page: https://verifymcp.io/servers/zvmzaretsky-validation-suite/valid