VerifyDesk

What is actually checked

One line per check, so you know what a pass means.

• verify_company and enrich_company read the official registry live on every call, with no cache: recherche-entreprises (SIRENE and RNE) for France, the Companies House API for the United Kingdom. Officers are the ones currently in office; resigned officers are left out.
• verify_vat calls VIES live on every request, and returns the VIES consultation number when you pass your own VAT number as requester_vat_number. If VIES or the member state is down, it returns the last answer VIES gave for that number in the past 7 days, marked stale: true with its original checkedAt and never with a consultation number. That fallback lives in the Cloudflare cache of each location, so it exists only where a recent check went through the same location; otherwise you get a retryable error, not a guess.
• validate_iban checks an IBAN offline against the SWIFT IBAN Registry (Release 103, September 2026, all 89 countries): registered country, exact length, the national account format (BBAN), check digits 02 to 98 and the ISO 7064 mod-97 checksum. It returns a stable reason_code when invalid, and the bank and branch codes the registry defines when valid.
• The optional BIC check confirms the ISO 9362 format SWIFT implements and a real ISO 3166 country code; it does not confirm that SWIFT issued the BIC. A BIC country that differs from the IBAN country is a warning, not an error, unless the registry lists it as a territory using that IBAN prefix (for example GP with FR).
• screen_sanctions screens names against the OFAC SDN and Consolidated (non-SDN) lists with every alias, the UN Security Council Consolidated List, the EU consolidated financial sanctions list and the UK Sanctions List, mirrored from the official files. Every result states which lists were screened and how old each one is, and says stale: true if a list has not been refreshed for more than 7 days.
• Sanctions matching ignores case, accents, punctuation, word order and legal forms, tolerates one typo in words of four letters or more and common transliterations, weighs words by how rare they are in the lists, and returns designated parties scoring 0.85 or more (adjustable from 0.7 to 1) as exact, alias or fuzzy matches. Dates of birth and other identifiers are not compared, and only Latin-script names are read.
• Measured on 2026-10-10: 92.36% of 9,130 realistic spelling variants of listed names (case, word order, legal form, one typo, a dropped middle name) and 89.2% of 1,000 real transliterations from the EU list were found, and 0.78% of 36,070 real company and person names that are not designated (SEC issuers, GLEIF entities, US legislators, Nobel laureates) were wrongly flagged. Every flagged name was read by hand to separate designated companies from false positives.
• Every tool declares its required and optional parameters in its JSON Schema (vat_number, iban and bic are separate fields, never one generic identifier), and the endpoint passes the official MCP Inspector over Streamable HTTP.

Use cases

What agents use it for, with real calls.

• Verify an EU VAT number via API, from an agent. Check that an EU VAT number is valid before invoicing or paying, and read back the registered name and address, with one tool call against VIES.
• Screen a company or person against sanctions lists from an agent. Screen a person or company name against the OFAC SDN and Consolidated, UN, EU and UK sanctions lists in one call, aliases included, with scored matches and the date of each list.
• Validate an IBAN via API before a payment goes out. Catch mistyped IBANs before money moves: length, national account format and mod-97 checksum per the SWIFT IBAN Registry (89 countries), plus an optional BIC check. Runs offline.
• Look up a French company by SIREN or name, via API. Find a French company in the official registry by SIREN, SIRET or name and get its legal status, legal form, activity code, address and creation date in one normalized shape.
• Supplier onboarding checks an agent can run on its own. Know who you are paying: pull the registry record and the officers of a French company, then screen the company against the US, UN, EU and UK sanctions lists, in two tool calls.

Every use case, across all products.

Connect

The endpoint.

A remote MCP server over Streamable HTTP. Any MCP client reaches it, and so does plain HTTP if you would rather call it directly. Swap in the key from your free account and the first call works.

https://verifydesk.agenttoolworks.com/mcp

claude mcp add --transport http verifydesk \
  https://verifydesk.agenttoolworks.com/mcp \
  --header "Authorization: Bearer atw_live_your_key"

Docs, including Claude Desktop, Cursor and Windsurf.

Where the data comes from

Only official, public sources, documented per tool. France uses the state company registry API, the United Kingdom uses the Companies House API, VAT validation uses the European Commission VIES service, and IBAN validation follows the SWIFT IBAN Registry and runs locally, so the number never leaves our server. Sanctions screening uses the US Treasury OFAC lists, the UN Security Council Consolidated List, the EU consolidated financial sanctions list published by the European Commission, and the UK Sanctions List published by the Foreign, Commonwealth and Development Office, which contains public sector information licensed under the Open Government Licence v3.0.

We do not scrape sources behind a login, and we do not resell data we are not allowed to serve.