Resolve the company.
Return the evidence.
Find available VAT numbers and US EINs, match tax identifiers to legal companies and monitor company-record changes. Start with the legal name and country; preserve the evidence behind every result.
| Integration | Connect | Start here |
|---|---|---|
| Remote MCP | https://vatfind.com/api/mcpOAuth with PKCE | MCP setup and scopes |
| REST API | https://vatfind.com/v1Bearer API key | Sandbox quickstart |
MCP clients need remote HTTP and OAuth support. Client availability and menus vary. Your client discovers the connection; the user signs in and approves permissions. See the setup reference for ChatGPT, Claude and other compatible clients.
REST as Markdown · MCP as Markdown · OpenAPI JSON · Registry metadata
Complete the first company lookup
- Read country capabilities. Use
get_country_capabilitiesorGET /v1/countries/{country_code}to establish the supported evidence dimensions. - Find candidates. Use
find_vat_numberorPOST /v1/companies/searchwith the legal company name and registration country. Give each billable operation a stable retry key. - Choose the legal entity. Compare registration number, address and jurisdiction with supplier documents. Ask the user when several candidates remain plausible.
- Check the supplied number. Use
check_vat_numberfor a VAT number orcheck_tax_identifierfor a US EIN. - Return the evidence. Include the selected entity, independent statuses, sources, times and warnings. Apply the customer's approval policy separately.
Available MCP tools and permissions
| Tool | Required scope | Purpose |
|---|---|---|
check_vat_number | checks:run | Check a VAT number |
find_vat_number | companies:search | Find VAT numbers |
check_tax_identifier | checks:run | Check a tax identifier |
get_check | checks:read | Get a saved check |
get_country_capabilities | coverage:read | Get country capabilities |
get_usage | usage:read | Get usage |
create_vat_monitor | monitoring:write | Create a company-record monitor |
list_vat_monitors | monitoring:read | List company-record monitors |
get_vat_monitor | monitoring:read | Get a company-record monitor |
update_vat_monitor | monitoring:write | Update a company-record monitor |
run_vat_monitor | monitoring:write | Run a company-record monitor now |
archive_vat_monitor | monitoring:write | Archive a company-record monitor |
list_vat_monitor_events | monitoring:events | List company-monitor events |
get_vat_monitor_event | monitoring:events | Get a company-monitor event |
Read the complete input schemas. Obtain explicit user confirmation before starting or changing monitoring.
What the agent can conclude
A company-record match establishes a source-reported association with the selected legal entity. Number format, company legal status and tax-authority registration status are separate facts. Current REST checks do not call a live tax authority; a matched company or a correctly formatted number does not establish current VAT registration.
Keep unavailable, not_supported and not_checked states intact. A missing EIN or VAT field means it was not supplied. A source outage needs a retry or review, rather than an inferred rejection. Retrieval time records when VATFind received the result; it is separate from a registry update date.
Cost, coverage and enterprise requirements
Sandbox REST calls use deterministic fixtures and no checks. MCP uses live workspace processing. Live dashboard, REST and MCP lookups share 3 free checks per account per day, resetting at 00:00 UTC, then use any available paid allowance. Each completed lookup uses one check. Monitoring requires paid access. A monitor establishes a billable baseline and each successful refresh uses a check. Coverage, usage and stored evidence retrieval do not consume another check.
Read the current plans and country coverage before running a batch. Review licensing and service terms and security information. For bulk delivery, resale rights or enterprise volume, discuss the requirement with VATFind.