OpenApps

AgentToolWorks MCP server — tools & history

AgentToolWorks MCP server: observed open status, tool schemas, linked apps and version history.

AgentToolWorks

Endpoint: https://verifydesk.agenttoolworks.com/mcp

Observed status: open. Checked: 2026-10-12T05:06:02+00:00.

Linked apps

  • AgentToolWorks

    Four remote MCP servers for agents, billed per call: company, VAT, IBAN and sanctions checks (VerifyDesk), job search across Greenhouse, Lever, Ashby and more (JobsRadar), EN 16931 e-invoices (InvoiceForge), and Shopify and WooCommerce product catalogs (Store Catalog). 100 free credits, no card.

Observed tools

  • enrich_company — Returns extended registry data for one company identified by its registration number: officers/directors currently in office (name and role), legal form, activity, address, headcount range when available. Input: country (FR or GB) and the exact registration number (SIREN for FR, company number for GB). Costs 1 credit.
  • get_usage — Returns your current plan, remaining credit balance and call volume over the last 30 days. Free to call.
  • screen_sanctions — Screens a person or company name against official sanctions lists: OFAC SDN and OFAC Consolidated (US Treasury), the UN Security Council Consolidated List, the EU consolidated financial sanctions list and the UK Sanctions List, primary names and aliases. Matching ignores case, accents, punctuation, word order and legal forms (LLC, PJSC, GmbH), and tolerates one typo in a word of 4+ letters and common transliterations (Sergei, Sergey, Sergej). Each match has a score from 0 to 1 and a match_type (exact, alias, fuzzy); only scores at or above min_score (default 0.85) are returned, at most 10 designated parties. Always reports which lists were screened, which were unavailable and when each was last refreshed: keep 'data_as_of' with the result as evidence of the check. Latin-script names only; dates of birth, nationalities and addresses are not compared. A match is a signal for enhanced due diligence, never a legal determination. Costs 1 credit.
  • validate_iban — Validates an IBAN offline against the SWIFT IBAN Registry (Release 103, Sep 2026, all 89 countries): registered country, length, the national account format (BBAN), check digits 02-98 and the ISO 7064 mod-97 checksum. Returns valid, and when invalid a stable reason_code (malformed, unknown_country, wrong_length, bad_bban_format, bad_check_digits, checksum_failed) with a human reason; on a valid IBAN, the bank_code and branch_code the registry defines for that country. Optional bic: checks the ISO 9362 format and its country code, returned as bic.valid; a BIC country that differs from the IBAN country is a warnings entry, not an invalid result. 'valid' is about the IBAN only. This checks structure, not that the account or BIC exists. Light read: costs 0.2 credit.
  • verify_company — Verifies a company against its official state registry and returns its legal status. France (SIREN/SIRET) and the United Kingdom (Companies House company number) are supported. Input: country and a query that is either a registration number or a company name. Returns up to 5 normalized records: registration number, legal name, active/closed status, legal form, activity code, registered address, creation date. Costs 1 credit.
  • verify_vat — Validates an EU VAT number live against VIES (European Commission) and returns whether it is currently valid, with the registered name and address when the member state provides them. Input: the full VAT number with its country prefix, e.g. 'FR40303265045'. Optional: requester_vat_number, your own EU VAT number; VIES then issues a consultationNumber, its official proof that you made this check at checkedAt. If VIES or the member state is down, returns the last answer VIES gave us for that number within the past 7 days, marked stale: true with its original checkedAt and never a consultation number; with no such answer, a retryable error. Fresh answers carry stale: false. Light read: costs 0.2 credit.

Data as of 2026-10-12T05:06:02+00:00.

OpenApps records store listings and observed changes. Store ranks are not download counts; launch dates may be derived or use the first observation. Coverage gaps are shown in the interactive catalog.

REST API specification · Guide for AI clients · Manage API keys and MCP connections