MCP FOR AI AGENTS

Give every agent a company identity tool.
Ground answers before action.

Connect MCP-compatible agents to six typed VATFind tools through OAuth. Resolve the entity, retrieve structured evidence, and keep each verification status explicit.

RESOLVE

Resolve the legal company

Start with a company name, VAT number, EIN or supported identifier and return the most likely legal-entity record.

GROUND

Return evidence, not prose

Give the agent structured identifiers, company attributes, source and retrieval time instead of an untraceable generated answer.

RECHECK

Refresh evidence deliberately

Run a new scoped check when a workflow needs current company evidence rather than relying on an earlier result.

THE AGENT FLOW

One evidence layer between the model and the decision.

MCP makes company-data capabilities available inside the agent’s tool environment. Your policy still controls when a tool is called, which fields are returned and what the agent may do next.

01

Agent identifies the task

The agent detects a company claim, identifier or action that requires external evidence.

02

MCP invokes the capability

The host sends typed company inputs using the access scope and country rules configured for the workflow.

03

VATFind resolves the entity

The result separates clear matches, ambiguous candidates, conflicts and no-match outcomes.

04

Policy governs the action

The agent cites the evidence, requests more information, escalates or proceeds within defined limits.

STRUCTURED OUTPUT

Designed for agent reasoning and audit.

Company evidence is more useful when the model does not have to infer what each field means. VATFind keeps identifiers, jurisdiction, match state, company status, source and retrieval time explicit.

Entity result
Canonical legal name, jurisdiction, registration number and available tax identifiers.
Resolution state
Matched, ambiguous, conflicting or no match—never a silent first-result selection.
Evidence context
Relevant returned company fields with source and retrieval time.
Policy signals
Missing data and discrepancies that can trigger a follow-up tool or human review.

CONTROL THE AGENT

MCP access is not permission to decide everything.

Grant only the scopes the client needs, constrain tool use in the agent policy, and require review for ambiguous or unavailable results. Company identity can ground the agent, while ownership, sanctions, bank verification, tax-authority status and transaction risk remain independent controls.

Review data boundaries See agentic KYB

PUBLIC MCP ENDPOINT

Connect with OAuth. Keep every tool scoped.

Use https://vatfind.com/api/mcp. VATFind handles discovery, PKCE consent, short-lived tokens, usage, and workspace isolation.

Read connection instructions