UK Due Diligence
Related Servers
Alternatives to UK Due Diligence
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceMCP server exposing the full UK Companies House Public Data API, enabling natural language queries for company profiles, search, officers, filing history, charges, insolvency, and persons with significant control, as well as downloading and reading PDF documents.-
- AlicenseNot gradedqualityDmaintenanceEnables MCP clients to look up, search, compare, and monitor UK companies using Companies House register data and iXBRL accounts, including financial history, risk signals, market statistics, lead-generation triggers, and watchlist alerts.MIT
- AlicenseNot gradedqualityDmaintenanceProduction-grade MCP server for the UK Companies House API, enabling AI assistants to search companies, get profiles, list officers, filings, and PSCs.MIT

yaml-ai-mcpofficial
AlicenseAqualityBmaintenanceAn MCP server for anti-money laundering (AML) compliance, including customer due diligence, transaction monitoring, and SAR filing, compliant with 6AMLD, UK MLR 2017, and FinCEN.432 PyPIMIT- AlicenseCqualityFmaintenanceAccess UK company data through the Companies House API directly in MCP clients, with 45+ tools for company info, search, officers, filing history, ownership, and charges.3764 npm31AGPL 3.0

whetstone-mcpofficial
AlicenseAqualityDmaintenanceAn MCP server for U.S. public-records data, enabling AI agents to search business registrations, screen names against government watchlists, and pull federal awards.447 npmMIT
TDQS
Scored across 18 tools
The register-specific tools (company_officers, company_psc, company_charges, charity_profile, etc.) are clearly distinct, but there are two competing paths to the same data: `search`→`fetch` duplicates `company_search`→`company_profile`, `charity_search`→`charity_profile`, `disqualified_search`→`disqualified_profile`, and `gazette_insolvency`→`gazette_notice`. An agent must decide whether to use the federated generic pair or the register-specific pair, which is a real ambiguity despite the descriptions explaining both.
Most names follow a predictable register_prefix + action pattern (company_search, company_psc, charity_profile, disqualified_profile, land_title_search, sanctions_screen). The two exceptions are the bare verbs `fetch` and `search`, which lack the resource noun and sit awkwardly beside their specific counterparts.
18 tools span six registers (Companies House, Charity Commission, disqualifications, Gazette, sanctions, Land Registry) and each tool maps to a real DD step, so the count is earned. It is on the heavy side and one pair (`search`/`fetch`) is arguably redundant with the specific search/profile tools.
Coverage is strong: search + profile + officers + PSC + charges + filing history + document metadata for Companies House, search/profile for charities and disqualifications, Gazette insolvency, sanctions screening, and Land Registry sales. Gaps are minor but real: no officer-name lookup (only officer ID from company_officers), Gazette limited to insolvency notices, and land_title_search only hits the Price Paid Index rather than actual title/ownership data despite its name.