UK Business Tools - Ledgerhall
Related Servers
Alternatives to UK Business Tools - Ledgerhall
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables AI assistants to search and retrieve UK Companies House data including company profiles, officers, and filing history via the official API.4170 npm1MIT
- FlicenseNot gradedqualityNot gradedmaintenanceProvides UK company lookups via Companies House, web scraping, and search tools designed to be context-efficient for AI agents. It includes integrated micro-payment monetization and supports data extraction and format conversion.-
- AlicenseAqualityAmaintenanceEnables AI agents to investigate corporate ownership, trace ultimate beneficial owners, screen sanctions, detect offshore exposure, and access fully cited dossiers from 130M+ entities across 31 global registries.2196 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables looking up UK companies, officers, ownership, filings, and running due diligence checks via the Companies House API, usable from AI tools like Claude or Cursor.9 npm13MIT
- AlicenseAqualityCmaintenanceConnects AI agents to AgentData's company intelligence platform, enabling natural language queries for structured company data like tech stacks, emails, people, and signals.66 npmMIT
- AlicenseNot gradedqualityAmaintenanceProvides real-time company verification and corporate intelligence by accessing global registries like UK Companies House, Singapore ACRA, and OpenCorporates. It enables AI agents to perform KYC tasks, retrieve company profiles, and conduct automated risk assessments for due diligence workflows.75 npmMIT
TDQS
Scored across 74 tools
Multiple tools overlap significantly within domains: prop_property_epc, prop_property_epc_summaries, prop_property_epc_search (deprecated but present) all handle EPC data, and gov_govuk_search vs gov_govuk_grep_content vs gov_govuk_get_section vs gov_govuk_get_content cover overlapping content retrieval. Several DD tools (dd_company_search vs prop_company_search, dd_search vs dd_fetch) duplicate functionality with unclear distinctions. The prefixes help, but within each cluster an agent will struggle to select the right tool.
Naming is inconsistent across modules: some use domain prefixes with snake_case verbs (gov_govuk_search, law_judgment_get_header), others use short opaque prefixes with no clear pattern (dd_search, prop_company_search), and one uses a different hierarchy (prop_property_epc vs prop_epc_certificate). The `law_` prefix mixes legal and DD tools inconsistently, and deprecated tools remain visible. No uniform verb_noun or consistent prefix convention.
74 tools is far beyond the well-scoped range, and the surface appears to bundle four independent domains (GOV.UK content, legal research, due diligence, property data) into one server. Many tools are near-duplicates (e.g., dd_company_search vs prop_company_search; prop_property_epc vs prop_property_epc_summaries), and the deprecated prop_property_epc_search should be removed. The count itself creates selection overhead that outweighs any benefit.
Each domain has notable gaps: GOV.UK lacks a tool to fetch full page content (only sections via govuk_get_section); property data has search and EPC tools but no explicit valuation or sale-date filtering beyond vague descriptions; law covers judgments/legislation/Hansard but lacks tools for court documents or lower-court records. The due-diligence domain is the most complete, but the overall surface has no cohesive workflow — it is four partial APIs stapled together. Deprecated tools and missing document retrieval (dd_company_filing_document requires a resource-capable client) create dead ends.