VATFind — VAT & EIN Lookup

npx add-mcp 'https://vatfind.com/api/mcp'

Company data for AI agents.VAT and EIN lookup through MCP.

Give an AI assistant tools to find a company’s VAT number, match a supplied VAT ID or US EIN, and retrieve the evidence behind the result. Connect through OAuth and use your VATFind workspace’s data access and credits.

How to connect an AI assistant to VATFind.

A company data MCP server exposes company-search and retrieval tools to an AI client through the Model Context Protocol. VATFind provides a remote Streamable HTTP endpoint with OAuth authorization. The client discovers the tools; VATFind handles each request within your workspace.

MCP SERVER URL https://vatfind.com/api/mcp

1. 01

   Open your client’s connections

   Add a custom remote MCP server in a client that supports Streamable HTTP and OAuth discovery. Use VATFind as the connection name.
2. 02

   Enter the server URL

   Paste https://vatfind.com/api/mcp into the remote server URL field. Use the endpoint above rather than this website page.
3. 03

   Sign in and authorize

   Follow the VATFind sign-in screen, review the client and requested permissions, and approve the scopes needed for your workflow.
4. 04

   Inspect the available tools

   Check that tools appear, then ask for country capabilities or workspace usage. Run a company lookup after confirming live access and credits.

Using Claude or another AI client?

The connection requires remote MCP support, compatible OAuth discovery and permission from your client or workspace administrator. Labels and availability depend on the client and plan. VATFind uses OAuth for MCP; you do not paste a live REST API key into the conversation.

Ask a specific question. Get company evidence.

Use a company name and country when the tax ID is missing. Use the supplied VAT number or US EIN when the task is to check the associated company. Give the agent enough context to distinguish a trading name, subsidiary and legal counterparty.

FIND A VAT NUMBER

Resolve the company first

“Find the VAT number for [legal company name] in [country]. Show the candidates if the company is ambiguous.”

find_vat_number returns company candidates. The agent should compare them before reporting an identifier.

Company grounding workflow →

MATCH A US EIN

Check the vendor identity

“Match this US EIN to the available company record. Compare the legal name with our vendor and show the result state.”

check_tax_identifier returns the company association and separate evidence states.

EIN lookup workflow →

MONITOR A SUPPLIER

Review company changes

“Create a weekly company-record monitor for this supplier, then show me any changes to its name, address or legal status.”

Monitoring tools establish a baseline and return company-change events for review.

Company monitoring through MCP →

These prompts describe workflows, not precomputed results. The host client controls tool use. A lookup can return a match, several candidates, no match or an unavailable source; the response tells the agent which outcome occurred.

Search companies, check identifiers and monitor changes.

Tool access depends on the OAuth scopes granted to the connection. Start with lookup and retrieval permissions; add monitoring write access when the workflow needs to create or change a schedule.

Tool	Scope	Purpose
check_vat_number	checks:run	Check VAT format and company-record association.
find_vat_number	companies:search	Find company candidates from a name or registration number.
check_tax_identifier	checks:run	Check a US EIN without applying VAT claims.
get_check	checks:read	Retrieve a prior result by check ID.
get_country_capabilities	coverage:read	Read supported formats and verification dimensions.
get_usage	usage:read	Read current-period usage and remaining allowance.
create_vat_monitor	monitoring:write	Create a paid baseline and scheduled company-record monitor.
list_vat_monitors	monitoring:read	List monitors, health, cadence and latest snapshots.
get_vat_monitor	monitoring:read	Retrieve one monitor and its current schedule state.
update_vat_monitor	monitoring:write	Pause, resume, or change cadence and watched fields.
run_vat_monitor	monitoring:write	Run an idempotent on-demand monitoring refresh.
archive_vat_monitor	monitoring:write	Stop future checks while retaining event evidence.
list_vat_monitor_events	monitoring:events	List material changes and operational events.
get_vat_monitor_event	monitoring:events	Retrieve one event and its delivery state.

The monitoring tools retain vat_monitor in their names for compatibility. Their current function is scheduled company-record monitoring. They do not watch live VIES or HMRC VAT-registration status.

Give the agent a result it can explain.

VATFind MCP returns the same company and check evidence model as REST, with a text summary for clients that need one. A returned company can include its legal name, registration number, country, VAT numbers, tax identifiers, registered address, legal status, sources and retrieval timestamp. Optional attributes depend on the record.

Response field	Question it answers	How the agent should use it
format_status	Does the identifier follow the supported format?	Ask for a corrected number when its structure is invalid.
registry_match_status	Was the identifier associated with a company?	Report the match state; request clarification for ambiguous candidates.
tax_authority_status	Is there an authority-registration result?	State when authority status is unsupported or not checked.
company_legal_status	What is the returned legal-company state?	Keep company status separate from VAT-registration status.
evidence[]	What supports each evidence dimension?	Retain source context and retrieval time when explaining the answer.
warnings / credits_used	What limits and usage apply to the result?	Surface relevant limitations and track the workspace cost.

The current service does not query live tax-authority systems. An agent must not describe a VAT registration as active or claim an IRS TIN match from company-record evidence alone.

Choose how your system will request company data.

Requirement	MCP	REST API
Typical caller	An MCP-compatible AI assistant or agent.	Your application, backend service or integration job.
Authentication	OAuth consent and scoped access tokens.	Server-side bearer API key.
Discovering operations	The client discovers typed tools.	Developers use API documentation and OpenAPI.
Testing	Live workspace processing.	Deterministic sandbox fixtures or live requests.
Company evidence	Structured check results with a text summary.	Structured JSON responses.

Both interfaces use the same live workspace credit balance. Billable MCP operations require active paid access and available credits. Read-only retrieval, country capabilities, events and usage do not consume a check credit. A large initial dataset or recurring file delivery is handled through a separately scoped bulk feed.

Keep permissions and retries explicit.

VATFind uses authorization code flow with PKCE, short-lived resource-bound tokens and rotating refresh tokens. Each tool call checks its required scope. A client should reconnect when it needs additional permissions.

Billable and mutating calls require an idempotency_key. Keep the same value when retrying the same operation. Handle rate limits and temporary source failures before allowing an automated retry loop.

If the connection fails

401: reconnect to refresh authentication. 403: review the required scope. If a tool is missing, refresh the client’s catalogue and check the current documentation. For a payment-required response, inspect workspace billing and credits.

MCP tool catalogue and capabilities reviewed 8 September 2026.

Connect an agent with a clear understanding of the data.

Endpoint, OAuth, clients, VAT and EIN lookup, sandbox testing and workspace credits.

What is a company data MCP server?

A company data MCP server exposes company-search and retrieval tools to AI clients through the Model Context Protocol. VATFind provides tools for company discovery, VAT number lookup, US EIN matching, country capabilities, usage and company-record monitoring.

What is the VATFind MCP server URL?

The remote endpoint is https://vatfind.com/api/mcp. Add that exact URL as a remote Streamable HTTP MCP server in a compatible client, then complete VATFind OAuth sign-in and authorization.

How do I connect VATFind MCP to an AI assistant?

Add a custom remote MCP connection, enter the VATFind server URL, and follow the OAuth sign-in and consent screen. Confirm that tools appear before running a lookup. The client must support remote HTTP and OAuth discovery; menu labels and availability vary.

Can I use VATFind company data in Claude?

Use a Claude client or workspace configuration that supports a compatible remote MCP connection and VATFind OAuth discovery. Add the VATFind server URL and authorize the required scopes. Check the client version, plan and administrator settings; compatibility is not established by opening the URL in a browser.

Can an AI agent find a VAT number or match an EIN?

Yes, where the relevant company data is available. find_vat_number searches company candidates; check_vat_number checks a VAT identifier association; check_tax_identifier checks a US EIN. The agent should report the returned match state and ask for clarification when results are ambiguous.

Do I need to give the AI agent my REST API key?

No. VATFind MCP uses OAuth with scoped, resource-bound tokens. Complete the sign-in and consent flow through the client instead of pasting a live REST API key into a prompt.