Skip to main content
Glama
kaylum54

companies-house-screening-mcp

by kaylum54
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to companies-house-screening-mcp

No user-submitted related servers found.

    Related Servers

    • Companies-House-MCP-Server

      fab-ai-up
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP 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.
      -

    • Companies House MCP Server

      stefanoamorelli
      A
      license
      C
      quality
      F
      maintenance
      Access 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.
      37
      17 npm
      27
      AGPL 3.0

    • companies-house-mcp

      jamescash1976
      F
      license
      Not graded
      quality
      D
      maintenance
      A local MCP server that exposes the UK Companies House API as tools for Claude Desktop and Cowork, enabling company search, profile retrieval, officer lookup, and document downloads.
      -
    • swissco by prospex-ch

      swisscoofficial

      prospex-ch
      A
      license
      A
      quality
      B
      maintenance
      An MCP server for Swiss company data. Nine tools that look a company up by UID, search 790,000 of them by name or by statutory purpose, trace what changed in the commercial register, browse public tenders, check a bank licence, resolve a UID to an LEI and its group parent, and find federally funded research a company took part in. Built by https://prospex.ch
      9
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.4/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool targets a distinct resource/action: company search vs company profile, officer search vs officer list vs officer appointments, and individual getters vs aggregate snapshot/batch screening. The one area of potential overlap, company_snapshot with get_company/get_officers/get_charges/get_insolvency, is explicitly described as a replacement for combined calls, so agents can choose correctly.

    Naming Consistency4/5

    The naming mostly follows a clear find_/get_ pattern, where find_ is for search and get_ is for retrieval by an ID. The pattern is weakened slightly by company_snapshot and screen_companies, which are descriptive but break the verb-prefix convention.

    Tool Count5/5

    11 tools is well within the ideal range and every tool earns its place: seven single-resource lookups, two search entry points, one aggregate snapshot, and one batch screening tool. The count feels deliberately scoped for a Companies House screening domain rather than padded or thin.

    Completeness5/5

    The surface covers the full screening workflow: company identification, company status, officers, ownership/PSC, charges, insolvency, filing history, officer appointment networks, individual deep-dives, and batch comparison. There are no obvious dead ends or missing operations that would prevent an agent from answering typical due-diligence questions.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources