companies-house-screening-mcp

Get a company profile

get_company

Read-onlyIdempotent

Verify a UK company by retrieving its Companies House profile, including status, SIC codes, accounts, and due dates. The result flags overdue filings, charges, insolvency, and recent incorporation.

Instructions

The registered profile for one UK company: legal name, status, type, incorporation date, registered office, SIC codes, and the accounts and confirmation statement due dates. Also returns derived flags that Companies House does not provide — whether filings are overdue, whether the company holds charges or has insolvency history, and whether it was incorporated within the last year. Use it to verify a company is real and active before relying on it. Needs a company number; call find_company first if you only have a name.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`verbose`	No	Also return the untouched Companies House payload under `raw`, alongside the shaped result. Roughly two and a half times the size; use it only when a field you need is missing from the shaped result.
`company_number`	Yes	Eight-character Companies House number, such as 00000006 or SC123456. Leading zeros may be omitted. This tool does not accept a company name — call find_company first if that is all you have.

Output Schema

TableJSON Schema

Name	Required	Description
`raw`	No	The untouched Companies House payload. Present only when verbose was true.
`meta`	Yes	Provenance and budget for this answer.
`name`	Yes
`type`	No
`flags`	Yes	Derived risk signals. Each one is computed here, not returned by Companies House.
`status`	No
`accounts`	Yes
`age_years`	No	Whole years since incorporation.
`sic_codes`	Yes	Standard Industrial Classification codes for the trade.
`dissolved_on`	No
`jurisdiction`	No
`status_detail`	No
`company_number`	Yes
`incorporated_on`	No
`type_description`	No
`confirmation_statement`	Yes
`registered_office_address`	No
`registered_office_in_dispute`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.4.0Sep 5, 2026

changedOutput schema / properties / meta / properties / licence / description

Previous value: -"Companies House data is Open Government Licence v3.0."New value: +"OGL v3.0 applies to eligible public-sector information. Personal data and other OGL exclusions are not licensed by this label; applicable data-protection duties still apply."

First observedv0.2.0Aug 30, 2026

TDQS

A4.2/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish that the tool is read-only, idempotent, and non-destructive. The description adds valuable behavioral context beyond annotations: it returns derived flags that Companies House itself does not provide, such as overdue indicators, charges/insolvency history presence, and recent incorporation. It also repeats the input constraint that only a company number is accepted. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is longer than minimal but every sentence earns its place: first the returned data inventory, then the derived flags, then the intended use case and prerequisite. It is front-loaded with the resource and scope, and there is no filler or tautology.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the read-only annotations, complete parameter schema, and existing output schema, the description covers everything an agent needs to select and invoke this tool correctly: what it returns, what derived flags it adds, when to use it, and how to handle a name-only input. No critical behavioral or prerequisite information is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already fully documents both company_number and verbose. The tool description reinforces the 'do not pass a name' caveat and the find_company prerequisite, but it does not add meaningful parameter-level semantics beyond what the input schema already provides. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: it returns the registered profile for one UK company, and enumerates the exact fields included (legal name, status, type, incorporation date, registered office, SIC codes, due dates). It also distinguishes the tool from find_company by clarifying that get_company needs a company number and does not accept a name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says to use this tool to verify a company is real and active before relying on it, and directs agents to call find_company first if only a name is available. It does not explicitly mention when to prefer related sibling tools like get_charges or get_insolvency, but it does clarify that it returns only derived flags about those topics rather than full details.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server