Anthropic's KYC Screener agent has a UK data gap — no PAF address verification, no real-time Companies House PSC register, no HMRC VAT validation. Here's what that looks like in practice and how the APITier MCP connector closes it.
Anthropic just shipped ten finance agents. One of them — the KYC Screener — is exactly the kind of workflow that UK compliance teams have been waiting for AI to handle. Automated document screening, entity verification, beneficial ownership checks, decision-ready output.
The problem is that it has a data gap. And in UK AML compliance, data gaps are audit findings.
In May 2026, Anthropic released ten ready-to-run agent templates for financial services, available as plugins in Claude Code and as Claude Managed Agents cookbooks. The agents cover two categories:
Each agent is built on a composable connector architecture. The agent handles reasoning and workflow orchestration; data connectors handle grounding — giving the agent access to authoritative, real-time data rather than relying on the model's training knowledge. Current data partners include Dun & Bradstreet, Moody's, FactSet, MSCI, and LSEG.
Claude Opus 4.7 is the recommended model for these agents. It currently leads the Vals AI Finance Agent benchmark at 64.37%.
Claude's finance agents are not standalone AI outputs. They are grounded reasoning systems. When the KYC Screener runs a check on a UK company, it does not hallucinate company details from training data. It calls a data connector, gets a structured response, and reasons over that response.
This is the right architecture for compliance. Auditable data sources. Traceable decisions. No fabricated entity details.
The weakness is that the connector is only as good as the data it returns. If the connector has gaps for a specific market — say, the UK — the agent produces incomplete output. The model is working correctly. The data isn't.
Every current connector in the Anthropic finance agent ecosystem is US-centric or global-aggregate. None of them are UK-native.
A KYC workflow needs to verify that the address on a document is real, canonical, and matches a known registered address. In the UK, the canonical address database is the Royal Mail Postcode Address File (PAF) — 32 million UK addresses, each assigned a unique property reference: the UPRN (Unique Property Reference Number).
D&B's UK address coverage is derived from Companies House filings and third-party aggregation. It is not PAF. It does not include UPRN. For a UK compliance workflow, that means no canonical address verification against the national standard, no UPRN to anchor cross-source entity resolution, and address mismatches that look like discrepancies even when the entity is legitimate.
A PAF-unverified address in a KYC output is a flag. The compliance reviewer has to resolve it manually. That is the opposite of automation.
UK entity verification requires Companies House — the official UK government register of all 5+ million active UK companies. It provides the registered company name, registered office address, company status, SIC codes, director register, and the PSC register (Persons with Significant Control — beneficial ownership).
The PSC register is a UK legal requirement under the 4th Anti-Money Laundering Directive. D&B sources from Companies House rather than querying it in real time. For a PSC update filed yesterday — D&B will lag. Companies House is the authoritative source.
UK VAT numbers are validated against the HMRC VAT register in real time. A VAT number that was valid last quarter may be deregistered today. None of the current finance agent connectors provide real-time HMRC VAT validation.
For GL Reconciler and Month-End Closer workflows, UK bank sort code validation requires the EISCD (Extended Industry Sort Code Directory) and modulus check algorithms — a UK-specific data source that US-oriented connectors do not have.
Scenario: Onboarding a UK private company — Acme Services Ltd, registered in Birmingham.
{
"entity": "Acme Services Limited",
"address": "14 Broad Street, Birmingham",
"country": "GB",
"status": "Active",
"duns": "21-234-5678",
"confidence": 0.74
}{
"address": {
"canonical": "14 Broad Street, B1 2HF",
"paf_verified": true,
"uprn": "100070489101",
"match_confidence": 0.99
},
"company": {
"company_number": "08234567",
"status": "Active",
"psc": [{"control": "75-100%"}]
},
"vat": { "status": "Active" }
}APITier has built and submitted a Model Context Protocol (MCP) connector to the Anthropic connector directory, specifically to close this gap. The connector exposes six tools:
| Tool | Data Source | Use Case |
|---|---|---|
| verify_uk_address | Royal Mail PAF | Canonical address + UPRN verification |
| lookup_uprn | OS AddressBase | Full address record + property metadata |
| verify_uk_company | Companies House API | Entity name, address, status, SIC codes |
| get_company_psc | Companies House PSC register | Beneficial ownership / AML compliance |
| validate_vat_number | HMRC VAT register | Live VAT status verification |
| validate_sort_code | EISCD modulus check | UK bank sort code validation |
npm install @apitier/mcp-server
For hosted endpoint access and API keys, contact us at hello@apitier.com or visit www.apitier.com.
UK compliance is the wedge use case. The same PAF + UPRN + Companies House data layer that powers KYC screening also underpins:
We are expanding the connector to cover these use cases across the Anthropic finance agent suite. If you are building UK financial workflows on Claude and want to talk about integration, reach out.
APITier is a UK financial data API provider. The @apitier/mcp-server MCP connector is available on npm. APITier has submitted a connector application to the Anthropic connector directory and applied to the Anthropic Partner Network.
The APITier MCP connector is live on npm. Add UK-native PAF, Companies House, and HMRC VAT data to your agent in minutes.
Published May 2026 · APITier