FabTally Valid
REMOTE · VALID.FABTALLY.COM · SCANNED SEP 20
Validation suite: EU VAT (VIES), IBAN mod-97, email (MX+disposable), geo place lookup, VIN decode.
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 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. 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 Usability71
- AI-judged instruction clarity (excellent).Pass
- 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. 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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 Valid MCP server?
FabTally Valid is a hosted endpoint at https://valid.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 · valid.fabtally.com
claude mcp add --transport http zvmzaretsky-validation-suite 'https://valid.fabtally.com/mcp'
{
"mcpServers": {
"zvmzaretsky-validation-suite": {
"url": "https://valid.fabtally.com/mcp"
}
}
} {
"servers": {
"zvmzaretsky-validation-suite": {
"type": "http",
"url": "https://valid.fabtally.com/mcp"
}
}
} [mcp_servers.zvmzaretsky-validation-suite] url = "https://valid.fabtally.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"zvmzaretsky-validation-suite": {
"type": "remote",
"url": "https://valid.fabtally.com/mcp",
"enabled": true
}
}
} openclaw mcp add zvmzaretsky-validation-suite --url 'https://valid.fabtally.com/mcp' --transport streamable-http
mcp_servers:
zvmzaretsky-validation-suite:
url: "https://valid.fabtally.com/mcp" {
"McpServers": {
"zvmzaretsky-validation-suite": {
"Transport": "http",
"Url": "https://valid.fabtally.com/mcp"
}
}
} assistant mcp add zvmzaretsky-validation-suite -t streamable-http -u 'https://valid.fabtally.com/mcp'
{
"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.
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://valid.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=valid.fabtally.com | CN=YR2,O=Let's Encrypt,C=US | 1 Aug 2026 | 30 Oct 2026 | RSA 2048 | SHA256-RSA | 6de8789ef26ca3f6d60779d706819c3f92c |
| SANs: valid.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 valid.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://valid.fabtally.com/mcp | Verified | 200 | |
| http (plaintext) | http://valid.fabtally.com/mcp | HTTPS enforced | 301 | https://valid.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 →
decode_vin Decode a VIN via NHTSA vPIC (paid $0.002) ~179
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.
| Name | Type | Req | Description |
|---|---|---|---|
| vin | string | yes | 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… |
No output schema declared.
No examples provided.
geo_lookup Resolve a country / state / city to ISO codes (paid $0.002) ~240
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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… |
No output schema declared.
No examples provided.
validate_email Validate an email: syntax + MX + disposable + role (paid $0.002) ~178
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | 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… |
No output schema declared.
No examples provided.
validate_iban Validate an IBAN (mod-97) + extract bank code (paid $0.001) ~191
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.
| Name | Type | Req | Description |
|---|---|---|---|
| iban | string | yes | 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… |
No output schema declared.
No examples provided.
validate_vat Validate an EU VAT number via VIES (paid $0.003) ~222
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.
| Name | Type | Req | Description |
|---|---|---|---|
| country_code | string | yes | 2-letter EU VAT country code (e.g. IE, DE, FR; GB/XI for Northern Ireland; GR accepted as EL). |
| vat_number | string | yes | 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… |
No output schema declared.
No examples provided.
What is the FabTally Valid MCP server?
FabTally Valid is an MCP server listed in the public MCP registry as io.github.zvmzaretsky/validation-suite. Validation suite: EU VAT (VIES), IBAN mod-97, email (MX+disposable), geo place lookup, VIN decode. This page covers its hosted endpoint (https://valid.fabtally.com/mcp).
Is the FabTally Valid MCP server safe to use?
FabTally Valid scores 78 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 Valid MCP server expose?
FabTally Valid exposes 5 tools: validate_vat, validate_iban, validate_email, geo_lookup, decode_vin. Their descriptions and schemas cost roughly 1,010 tokens of context every time the server is loaded.
Does the FabTally Valid MCP server require authentication?
No. We connected to FabTally Valid without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the FabTally Valid MCP server still maintained?
FabTally Valid 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.