Companies House

Get Company

get_company

Read-onlyIdempotent

Fetch a single UK company profile by company number. Returns registered name, status, type, SIC codes, registered office, accounts/confirmation-statement due dates, and links to officers/filings/charges/PSCs.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`company_number`	Yes	UK company number (e.g., "00006245")

Output Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Registered company name
`type`	Yes	Company type (private limited, public limited, etc.)
`ch_url`	No	Link to company profile on Companies House website
`status`	Yes	Company status (active, dissolved, etc.)
`sic_codes`	Yes	Standard Industrial Classification codes
`dissolved_on`	No	Dissolution date (ISO format) if applicable
`jurisdiction`	No	Company jurisdiction (England and Wales, Scotland, etc.)
`status_detail`	No	Additional status details
`company_number`	Yes	UK company number
`incorporated_on`	Yes	Incorporation date (ISO format)
`accounts_next_due`	No	Next accounts filing due date (ISO format)
`registered_office`	No	Registered office address details
`accounts_next_made_up_to`	No	Next accounts period end date (ISO format)
`last_accounts_made_up_to`	No	Last filed accounts period end date (ISO format)
`confirmation_statement_next_due`	No	Next confirmation statement due date (ISO format)

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 24, 2026

addedInput schema / examples

Added value: +[
+  {
+    "company_number": "00006245"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "accounts_next_due": {
+      "description": "Next accounts filing due date (ISO format)",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "accounts_next_made_up_to": {
+      "description": "Next accounts period end date (ISO format)",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "ch_url": {
+      "description": "Link to company profile on Companies House website",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "company_number": {
+      "description": "UK company number",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "confirmation_statement_next_due": {
+      "description": "Next confirmation statement due date (ISO format)",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "dissolved_on": {
+      "description": "Dissolution date (ISO format) if applicable",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "incorporated_on": {
+      "description": "Incorporation date (ISO format)",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "jurisdiction": {
+      "description": "Company jurisdiction (England and Wales, Scotland, etc.)",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "last_accounts_made_up_to": {
+      "description": "Last filed accounts period end date (ISO format)",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "name": {
+      "description": "Registered company name",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "registered_office": {
+      "description": "Registered office address details",
+      "properties": {
+        "address_line_1": {
+          "type": "string"
+        },
+        "address_line_2": {
+          "type": "string"
+        },
+        "country": {
+          "type": "string"
+        },
+        "locality": {
+          "type": "string"
+        },
+        "postal_code": {
+          "type": "string"
+        },
+        "region": {
+          "type": "string"
+        }
+      },
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "sic_codes": {
+      "description": "Standard Industrial Classification codes",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "status": {
+      "description": "Company status (active, dissolved, etc.)",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "status_detail": {
+      "description": "Additional status details",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "type": {
+      "description": "Company type (private limited, public limited, etc.)",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "company_number",
+    "name",
+    "status",
+    "type",
+    "sic_codes",
+    "incorporated_on"
+  ],
+  "type": "object"
+}

First observedMay 11, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive. Description adds value by detailing exact return fields (status, type, SIC codes, etc.) and links. Could mention error handling for missing company, but overall good.

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

Conciseness5/5

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

Two sentences: first states action, second lists returns. No fluff, efficient, and front-loaded with the key purpose.

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

Completeness4/5

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

Given output schema exists and annotations cover safety, description is thorough for a simple read tool. Lists all major return fields. Could mention pagination or rate limits, but not critical.

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 coverage is 100% with a good description of the parameter. Description reinforces it's a UK company number but adds no new syntax or format details. 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 clearly states the verb 'fetch' and the resource 'UK company profile', specifying the input as company number. It lists returned data, distinguishing it from sibling tools like search_companies (search) and get_filings (filings only).

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?

Implied that this tool is for fetching a specific company by number, versus searching. No explicit when-not-to-use or alternatives mentioned, but the context is clear enough.

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

All Companies House tools Inspect

Try in Browser

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

Glama MCP Gateway

Add one secure layer between your agents and this server.