Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

org.scienceswarm/commerce-validators

REMOTE · MCP.SCIENCESWARM.ORG · SCANNED SEP 20

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

0 this week 18 Trust /100
Trust breakdown (7 categories)

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 Security46
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Install

How do I install the org.scienceswarm/commerce-validators MCP server?

org.scienceswarm/commerce-validators is a hosted endpoint at https://mcp.scienceswarm.org/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 · mcp.scienceswarm.org

# add to Claude Code
claude mcp add --transport http org-scienceswarm-commerce-validators 'https://mcp.scienceswarm.org/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "org-scienceswarm-commerce-validators": {
      "url": "https://mcp.scienceswarm.org/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "org-scienceswarm-commerce-validators": {
      "type": "http",
      "url": "https://mcp.scienceswarm.org/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.org-scienceswarm-commerce-validators]
url = "https://mcp.scienceswarm.org/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "org-scienceswarm-commerce-validators": {
      "type": "remote",
      "url": "https://mcp.scienceswarm.org/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add org-scienceswarm-commerce-validators --url 'https://mcp.scienceswarm.org/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  org-scienceswarm-commerce-validators:
    url: "https://mcp.scienceswarm.org/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "org-scienceswarm-commerce-validators": {
      "Transport": "http",
      "Url": "https://mcp.scienceswarm.org/mcp"
    }
  }
}
# add to Vellum
assistant mcp add org-scienceswarm-commerce-validators -t streamable-http -u 'https://mcp.scienceswarm.org/mcp'
// mcp.json
{
  "mcpServers": {
    "org-scienceswarm-commerce-validators": {
      "type": "http",
      "url": "https://mcp.scienceswarm.org/mcp"
    }
  }
}

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

Changelog

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.

  • 20 Sept 26 −49
    • Endpoint reachability: reachable → not serving MCP security
    • Tool safety: pass → unverified security
    • Stability: 0.87 → unverified security
    • Transport: pass → fail security
    • Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
    • Capabilities: pass → unverified functional
    • Tool coverage: 100 → unverified functional
  • 19 Sept 26 +49
    • Injection markers: unverified → pass security
    • Transport: fail → pass security
    • Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 10 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
    • Endpoint reachability: not serving MCP → reachable functional
    • Tool coverage: unverified → 100 functional
    • MCP protocol: unverified → pass functional
    • Stability: unverified → 0.87 functional
  • 11 Sept 26 −48
    • Endpoint reachability: reachable → not serving MCP security
    • Stability: 0.77 → unverified security
    • Tool safety: pass → unverified security
    • Transport: pass → fail security
    • Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
    • Capabilities: pass → unverified functional
    • Tool coverage: 100 → unverified functional
  • 10 Sept 26 +48
    • Injection markers: unverified → pass security
    • Transport: fail → pass security
    • Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 10 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
    • Endpoint reachability: not serving MCP → reachable functional
    • Tool coverage: unverified → 100 functional
    • Stability: unverified → 0.77 functional
    • MCP protocol: unverified → pass functional
  • 8 Sept 26 −50
    • Endpoint reachability: reachable → not serving MCP security
    • Stability: 0.93 → unverified security
    • Tool safety: pass → unverified security
    • Transport: pass → fail security
    • Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
    • Capabilities: pass → unverified functional
    • Tool coverage: 100 → unverified functional
  • 6 Sept 26 +1

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

  • 5 Sept 26 −2
    • Stability: pass → 0.87 functional
  • 4 Sept 26 0
    • Stability: 0.97 → pass security
Diagnostics

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://mcp.scienceswarm.org/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=scienceswarm.org CN=YE1,O=Let's Encrypt,C=US 9 Sept 2026 8 Dec 2026 ECDSA 256 ECDSA-SHA384 6c5906334aab1b50a4e93992d5932dc7e60
SANs: *.scienceswarm.org, scienceswarm.org
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.scienceswarm.org. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
org. present 26974 8 Verified
scienceswarm.org. 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 530
Header Value
x-frame-options SAMEORIGIN
referrer-policy same-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.scienceswarm.org/mcp HTTP error 530
http (plaintext) http://mcp.scienceswarm.org/mcp Inconclusive 530
MCP tools · 10 exposed · ~875 tokens

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 →

Tool Tokens
check_email_domain ~70

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.

NameTypeReqDescription
email_or_domainstringyes

No output schema declared.

No examples provided.

payout_reconciliation ~94

Explain why a payout is less than sales: walk gross -> deductions -> expected, and (if actual_deposit given) flag the unexplained gap (shortfall/surplus).

NameTypeReqDescription
actual_deposit
chargebacksnumber
gross_salesnumberyes
other_deductionsnumber
processing_feesnumber
refundsnumber

No output schema declared.

No examples provided.

reorder_point ~70

Reorder point = lead-time demand + safety stock. If on_hand is given, returns whether to reorder now and the days of cover remaining.

NameTypeReqDescription
avg_daily_salesnumberyes
lead_time_daysnumberyes
on_hand
safety_stocknumber

No output schema declared.

No examples provided.

stripe_connect_split ~152

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.

NameTypeReqDescription
application_fee_fixednumber
application_fee_pctnumber
charge_amountnumberyes
fee_bearerstring
processing_fixednumber
processing_pctnumber

No output schema declared.

No examples provided.

validate_aba_routing ~56

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.

NameTypeReqDescription
routing_numberstringyes

No output schema declared.

No examples provided.

validate_eori ~88

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).

NameTypeReqDescription
eoristringyes

No output schema declared.

No examples provided.

validate_eu_vat ~111

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).

NameTypeReqDescription
vat_numberstringyes

No output schema declared.

No examples provided.

validate_gtin ~60

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.

NameTypeReqDescription
codestringyes

No output schema declared.

No examples provided.

validate_iban ~64

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.

NameTypeReqDescription
ibanstringyes

No output schema declared.

No examples provided.

vat_rate_by_country ~110

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'.

NameTypeReqDescription
country_codestringyes
datestring

No output schema declared.

No examples provided.

Common questions

What is the org.scienceswarm/commerce-validators MCP server?

org.scienceswarm/commerce-validators is an MCP server listed in the public MCP registry as org.scienceswarm/commerce-validators. Commerce validators: live EU VAT (VIES), EORI, email/MX lookups; IBAN/ABA/GTIN checksums; VAT rates. This page covers its hosted endpoint (https://mcp.scienceswarm.org/mcp).

Is the org.scienceswarm/commerce-validators MCP server safe to use?

org.scienceswarm/commerce-validators scores 18 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 org.scienceswarm/commerce-validators MCP server expose?

org.scienceswarm/commerce-validators exposes 10 tools: validate_iban, validate_gtin, validate_aba_routing, validate_eu_vat, validate_eori, and 5 more. Their descriptions and schemas cost roughly 875 tokens of context every time the server is loaded.

Does the org.scienceswarm/commerce-validators MCP server require authentication?

No. We connected to org.scienceswarm/commerce-validators without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the org.scienceswarm/commerce-validators MCP server still maintained?

org.scienceswarm/commerce-validators 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.