mcpbeat

Commerce Validators MCP Server

org.scienceswarm/commerce-validators
answering

Commerce Validators is answering right now. Last checked 13 min ago. It exposes 10 tools. Last commit 16 Jul 2026.

Commerce validators: live EU VAT (VIES), EORI, email/MX lookups; IBAN/ABA/GTIN checksums; VAT rates.

Uptime history 42 hours of history · worst hour 0%
42 hours agonow
57.1%
Uptime 24h
52 of 91 checks
10
Tools
read from the server
289 ms
Response time
average over 24h
0
Stars
last commit 16 Jul 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

run in your terminal
claude mcp add commerce-validators --transport http https://mcp.scienceswarm.org/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "commerce-validators": {
      "url": "https://mcp.scienceswarm.org/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.commerce-validators]
url = "https://mcp.scienceswarm.org/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "commerce-validators": {
      "url": "https://mcp.scienceswarm.org/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "commerce-validators": {
      "url": "https://mcp.scienceswarm.org/mcp"
    }
  }
}

Available tools 10

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

validate
validate_aba_routing
Validate a US ABA bank routing number (9 digits) by its checksum. Catch typos before initiating an ACH/wire payout. Pure-algorithm; nothing leaves the machine.
validate_eori
Validate an EORI number (Economic Operators Registration and Identification) against the official EU customs database (live lookup). An EORI is required for EU imports/exports — check a trading partner's or your own EORI before customs filings / freight bookings. Input e.g. 'DE1234567890123' (country code + number).
validate_eu_vat
Validate an EU VAT number against the official EU VIES service (live government lookup). Returns whether it is registered/valid and, if available, the registered trader name + address. An LLM cannot know this without the real lookup — use this before invoicing/reverse-charging an EU B2B customer. Input e.g. 'DE811569869' or 'IE6388047V' (country code + number).
validate_gtin
Validate a GTIN / UPC / EAN barcode (GTIN-8/12/13/14) by its check digit. Catches mistyped product barcodes in inventory/catalog workflows. Pure-algorithm.
validate_iban
Validate an IBAN (International Bank Account Number) by structure + the ISO 7064 mod-97 checksum. Catches typos/invalid accounts before you initiate a transfer. Pure-algorithm; no data leaves the machine.
email
check_email_domain
Check whether a domain can actually receive email (has MX records) via a real DNS-over-HTTPS lookup — validate a customer/supplier email's domain before sending or invoicing. An LLM can't know current DNS; this does the live lookup.
payout
payout_reconciliation
Explain why a payout is less than sales: walk gross -> deductions -> expected, and (if actual_deposit given) flag the unexplained gap (shortfall/surplus).
reorder
reorder_point
Reorder point = lead-time demand + safety stock. If on_hand is given, returns whether to reorder now and the days of cover remaining.
stripe
stripe_connect_split
Compute the Stripe Connect three-way split for one charge. Returns what the buyer pays, what Stripe takes, what the platform nets (its application fee), and what the connected seller nets — plus the platform's effective take rate. fee_bearer: 'seller' | 'platform' | 'buyer' (who absorbs the Stripe processing fee). Rates are editable; defaults are US card standard 2.9%+$0.30.
vat
vat_rate_by_country
EU VAT rates (standard / reduced / super-reduced / parking) for a country, from the maintained ibericode/vat-rates dataset (fetched live, cached 24h) — including which rate set was in force on an optional 'date' (YYYY-MM-DD) and the names of regional exceptions (e.g. Canary Islands). Input e.g. 'DE', 'FR', 'HU'.

Endpoints

URLTransportStateLatencyChecked
https://mcp.scienceswarm.org/mcp streamable-http answering 243 ms 13 min ago

Commerce Validators — questions

Answers built from our own checks of this server.

What can Commerce Validators do?
It exposes 10 tools, read directly from the server on our last check. Among them: check_email_domain, payout_reconciliation, reorder_point, stripe_connect_split, validate_aba_routing, validate_eori and 4 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Commerce Validators working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 52 of 91 checks got a reply (57.1%), average response time 289 ms. The bar chart above shows every period we have measured.
How do I connect Commerce Validators?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Commerce Validators need an API key?
No. Commerce Validators completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 10 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Commerce Validators?
It answers our handshake in 289 ms on average, which is faster than 48% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Commerce Validators open source?
Yes — it is published under the NOASSERTION licence, written in Python and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.