FabTally Valid MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@FabTally Valid MCP Server Can you validate the VAT number DE123456789?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
FabTally Valid — MCP server
A developer validation suite — the per-call utilities incumbents charge for (Vatstack $0.01–0.09/call) or lock behind subscriptions, unified. Fronts the Valid HTTP API at https://valid.fabtally.com. Holds no private key.
Tools (all paid; a call with no payment returns the decoded x402 402 challenge)
Tool | Price | What it does |
| $0.003 | Flagship. EU/EEA VAT: |
| $0.001 |
|
| $0.002 |
|
| $0.002 |
|
| $0.002 |
|
Every tool also accepts an optional x_payment (base64 x402 payload) that is
forwarded as the X-PAYMENT header to settle the call and return the real result.
Humans can instead prepay by card and use an X-FabTally-Key credit key against
the HTTP API.
Related MCP server: phone-validation-x402
Transports
stdio (portable):
npx fabtally-valid-mcp(bin:fabtally-valid-mcp)streamable-http (hosted):
https://valid.fabtally.com/mcp
Config: FABTALLY_VALID_BASE (default https://valid.fabtally.com).
Read-only, keyless, stateless, non-PII. Operated by Sunstone Soft (fabtally.com). Not legal, tax, or financial advice.
Available Tools
5 toolsdecode_vinDecode a VIN via NHTSA vPIC (paid $0.002)AInspect
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.
Inputs: vin (required), x_payment.
geo_lookupResolve a country / state / city to ISO codes (paid $0.002)AInspect
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.
Inputs: city, query, state, country, +1 more.
validate_emailValidate an email: syntax + MX + disposable + role (paid $0.002)AInspect
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.
Inputs: email (required), x_payment.
validate_ibanValidate an IBAN (mod-97) + extract bank code (paid $0.001)AInspect
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.
Inputs: iban (required), x_payment.
validate_vatValidate an EU VAT number via VIES (paid $0.003)AInspect
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.
Inputs: vat_number (required), country_code (required), x_payment.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 5 tools
Each tool targets a distinct entity type (VAT, IBAN, email, location, VIN) with no overlap. The descriptions clearly differentiate the validation/lookup purpose of each.
Three tools follow the validate_<entity> pattern, while two use different verbs (geo_lookup, decode_vin). The pattern is still predictable and readable, but minor inconsistency exists.
Five tools is a well-scoped number for a validation/lookup server. Each tool has a clear, distinct function and none feel redundant or excessive.
The server covers common validation and lookup needs well. A few additional validators (phone, credit card) could be added, but the current set is coherent and functional for its apparent purpose.
Maintenance
Related MCP Connectors
Email, phone, domain, URL & OFAC verification; phishing and IBAN checks via x402.
Email, DNS, SPF/DMARC, site contacts, Markdown, IBAN, Swedish validators. Pay per call (x402).
Verify an EU VAT number live in VIES before invoicing or paying. $0.02/call via x402.
Company registry, VAT, sanctions, vendor KYB, IBAN and wallet checks; pay per call by x402 or card.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceValidates JSON syntax and optionally checks against a JSON Schema, with pay-per-call via x402 micropayments.MIT
- AlicenseNot gradedqualityCmaintenanceValidates phone numbers worldwide (carrier, line type, country) via single or batch requests, with pay-per-call using x402 micropayments (USDC on Base) — no API key required.MIT
- FlicenseNot gradedqualityCmaintenanceProvides real validation and live registry lookups for ecommerce and fintech workflows, including EU VAT, EORI, email domain, IBAN, ABA routing, and GTIN checks.-
- AlicenseAqualityCmaintenanceEnables MCP-capable agents to validate EU VAT numbers, IBANs, and EORI customs numbers, look up company data by LEI or VAT, and fetch current VAT rates, with built-in service health checks.722 PyPIMIT