Companies House MCP Server

A comprehensive Know Your Business (KYB) toolkit via Model Context Protocol (MCP). This server provides 22 production-ready tools that integrate with the UK Companies House API to enable complete due diligence automation, beneficial owner discovery, risk detection, and regulatory compliance.

Status: ✅ Production Ready | Version: 2.0.0 | Tools: 22 (17 new + 5 backward compatible) | API Endpoints: 16

🎯 The 10 KYB Requirements (All Implemented)

Features

Core KYB Capabilities

• ✅ Company Search & Verification: Advanced search by name, number, or address with fuzzy matching
• ✅ Company Profiles: Complete company details (status, address, incorporation date)
• ✅ Insolvency Detection (MANDATORY): Hard-stop risk signal for any credit/partnership decision
• ✅ Officer Verification: Directors, secretaries with complete appointment history
• ✅ Disqualification Checks (MANDATORY): Screen natural persons and corporate entities
• ✅ Beneficial Owner Discovery (PSC): Identify Persons with Significant Control with ownership %
• ✅ Officer Network Analysis: Detect serial directors and company connections
• ✅ Registered Office Address: Direct verification without parsing full profile
• ✅ Filing History & Documents: Access accounts, confirmations, PSC notifications with PDF download
• ✅ Charges & Mortgages: View secured lending exposure and creditor priorities
• ✅ Comprehensive Reports: Single-call KYB aggregation (search → verify → risk-check → report)

Operational Excellence

• Production Ready: All 10 requirements implemented, tested, documented
• Complete API Coverage: 16 Companies House endpoints fully integrated
• Pagination Support: Handle large result sets across all list tools
• Error Standardization: Consistent error responses with codes and descriptions
• Backward Compatible: 5 legacy tools maintained for existing integrations
• Stateless Design: No data stored, secure for public cloud deployment
• Rate Limiting: Passes through Companies House rate limits with error codes
• Base64 Documents: PDFs returned with metadata for secure transmission

Use Cases

• Know Your Business (KYB): Complete 10-requirement compliance for company onboarding
• Risk Assessment: Insolvency detection, disqualification screening, charge analysis
• Due Diligence: Deep research via filing history, document access, officer networks
• Beneficial Owner Verification: UBO identification with control percentages
• Serial Director Detection: Map director networks across companies
• Compliance Reporting: Generate audit trails and risk assessments

📚 Documentation

Getting Started: Start with one of these based on your needs:

• QUICK_REFERENCE.md - 5-minute overview of all 10 requirements
• INDEX.md - Complete documentation index and navigation hub
• IMPLEMENTATION_SUMMARY.md - Comprehensive implementation guide
• API_ENDPOINT_MAPPING.md - Complete API-to-tool reference
• REQUIREMENTS_IMPLEMENTATION.md - Detailed requirement mapping
• CHECKLIST.md - Verification checklist

🔄 Complete KYB Workflow

This is what a full Know Your Business process looks like using the server:

1. Search for company
   → search_companies_advanced("Company Name")
   
2. Verify correct company
   → get_company_profile(company_number)
   
3. ⚠️  CHECK INSOLVENCY (MANDATORY - HARD STOP IF FOUND)
   → get_insolvency(company_number)
   
4. Get company details
   → get_registered_office_address(company_number)
   → get_filing_history_list(company_number)
   
5. Get officers
   → get_company_officers(company_number)
   → For each officer:
      • get_disqualification_natural(officer_id)  [RED FLAG]
      • get_officer_appointments(officer_id)      [NETWORK]
   
6. Get beneficial owners (PSC)
   → get_psc_list(company_number)
   → For each PSC:
      • get_psc(company_number, psc_id)
      • Check disqualifications
   → get_psc_statements(company_number)
   
7. Get financial exposure
   → get_charges_list(company_number)           [MORTGAGES]
   
8. Review documents if needed
   → get_filing_history_list(company_number)
   → download_filing_document(company_number, transaction_id)
   
9. Generate final report
   → generate_company_report(company_number)

Result: Complete due diligence report with all compliance checks passed ✅

Architecture

• Transport: HTTP (Stateless Streamable) - Ideal for public/cloud deployment.
• Authentication: Client-side API Key injection (users provide their own key).
• Stack: Python, FastMCP, Docker, Kubernetes.

Prerequisites

1. Companies House API Key: You must obtain a "Live" API Key from the Companies House Developer Hub.
2. Docker (for local running).
3. Kubernetes (optional, for deployment).

Quick Start (Docker)

1. Build the Image:

   Terminal

   Copy

   docker build -t companies-house-mcp .
   

2. Run the Container:

   Terminal

   Copy

   docker run -p 8001:8001 companies-house-mcp
   

3. Test with Postman:

   • Import mcp_postman_collection.json.
   • Set the apiKey variable to your Companies House API Key.
   • Send a POST request to http://localhost:8001/mcp.

Usage with Claude Desktop (or other MCP Clients)

Configure your MCP client to connect to the server. Since this server uses HTTP transport, you might need an adapter or a client that supports HTTP MCP.

Tool Call Example (JSON-RPC):

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "generate_company_report",
    "arguments": {
      "company_number": "00000006",
      "api_key": "YOUR_REAL_API_KEY"
    }
  }
}

Tools Reference

All 22 Available Tools

Company Search & Profile (3 tools)

Filing & Documents (4 tools)

Officers & Management (2 tools)

Beneficial Owners (PSC) (3 tools)

Risk & Compliance (3 tools)

Security & Assets (1 tool)

Comprehensive Reports (1 tool)

Backward Compatibility (5 deprecated tools)

search_companies, get_filing_history, get_company_charges, get_persons_with_significant_control, get_company_insolvency (Still available but use new tools above)

Deployment (Kubernetes)

1. Deploy:

   bash

   Copy

   kubectl apply -f k8s/deployment.yaml
   kubectl apply -f k8s/service.yaml
   

   (Note: The secret.yaml is no longer strictly required if you rely on client-side keys, but can be used for server-side defaults).

2. Access: The service is exposed via NodePort on port 30001 (or LoadBalancer depending on your K8s setup).

Security Note