How do LLMs get verified business data?
ENTIA is an MCP-native server that gives AI agents verified company data over the Model Context Protocol. Every record is anchored to an official register (BORME, Companies House, SIRENE INSEE, the Estonian Business Register, GLEIF LEI and VIES VAT), not scraped. An agent connects to https://mcp.entia.systems/mcp and calls one of 12 tools to resolve a company and its provenance. Coverage today: 11,330,392 entities across 10 European countries. An LLM gets verified business data by grounding — calling out to a source at inference time instead of relying on training memory. MCP is the mechanism: the model invokes a tool, ENTIA returns registry-anchored fields with citations, and the answer is sourced rather than recalled.
What an AI agent sees today vs. ENTIA
Today (definitional)
Most answers an agent gets today for “LLM verified business data” come from definitional — useful, but the data is often scraped or aggregated, the source of each field is not attached, and there is no single MCP call that returns identity plus provenance together.
With ENTIA
ENTIA returns the same answer anchored to the official register, with a sameAs/citation on every claim, so the agent (and its operator) can verify the chain end-to-end. One call, get_full_dossier, returns up to 349 fields from 4 sources; fields that cannot be corroborated are returned as null, never invented.
The tools an agent can call
entity_lookup— resolve a company by name, registration number, VAT or domainverify_vat— validate an EU VAT number against VIESget_full_dossier— one call returns up to 349 fields from 4 sourcesrun_risk_audit— structured risk signal for a resolved entityget_competitors— entities in the same sector and zonesearch_entities— search the corpus by sector, city and filters
12 tools total. Full manifest: /mcp-docs.
Connect in about a minute
Point any MCP client at the remote server and start calling tools. No install.
{
"mcpServers": {
"entia": {
"url": "https://mcp.entia.systems/mcp",
"headers": { "X-ENTIA-Key": "entia_live_..." }
}
}
}Frequently asked questions
How do LLMs get verified business data?
ENTIA is an MCP-native server that gives AI agents verified company data over the Model Context Protocol. Every record is anchored to an official register (BORME, Companies House, SIRENE INSEE, the Estonian Business Register, GLEIF LEI and VIES VAT), not scraped. An agent connects to https://mcp.entia.systems/mcp and calls one of 12 tools to resolve a company and its provenance. Coverage today: 11,330,392 entities across 10 European countries. An LLM gets verified business data by grounding — calling out to a source at inference time instead of relying on training memory. MCP is the mechanism: the model invokes a tool, ENTIA returns registry-anchored fields with citations, and the answer is sourced rather than recalled.
Why can't the model just use what it already knows?
Training data is frozen and unsourced — companies change status, address and ownership. Grounding via an MCP call to ENTIA gives the model current, citable data at the moment it answers.
How does an AI agent connect?
It is a remote MCP server — point any MCP client at https://mcp.entia.systems/mcp and authenticate with an X-ENTIA-Key. No install, no infrastructure. Setup: https://entia.systems/mcp-setup.
What does it cost?
There is a free TRACE tier for preview and basic tools; deeper tools (full dossier, risk audit) are on paid self-serve tiers. Pricing is public and machine-readable at https://entia.systems/.well-known/ai-pricing.json.
How much coverage does it have?
11,330,392 verified entities across 10 European countries, 16 official sources, and 40,345,410 registry acts, as reported live by get_platform_stats.