UK Due Diligence

Search Gazette Corporate Insolvency Notices

gazette_insolvency

Read-onlyIdempotent

Search The Gazette's insolvency notice index by entity name.

Searches The Gazette's corporate-insolvency notice index using the authoritative Gazette notice-code taxonomy. Results are sorted by an internal DD severity score; the notice label itself remains a source fact.

Each result includes a notice_numeric_id. Read the full legal wording via the notice://{notice_numeric_id} resource.

The Gazette is the official UK public record. A notice here means the event has been formally published and is legally effective.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	Company or individual name to search for in Gazette insolvency notices
`query`	No	Alias for name.
`end_date`	No	Filter notices up to this date (YYYY-MM-DD)
`start_date`	No	Filter notices from this date (YYYY-MM-DD)
`entity_name`	No	Deprecated alias for name.
`max_notices`	No	Cap on notices returned, applied after severity/date sort. Default 20. The Gazette insolvency feed returns up to 100 results per search — raise to 100 to see the full set.
`notice_type`	No	Filter by Gazette notice code (e.g. '2450' petition to wind up a company, '2452' winding-up order, '2410' appointment of administrators). Omit to search all.

Output Schema

TableJSON Schema

Name	Required	Description
`notices`	No	Matching notices, sorted by severity (desc) then date (desc).
`end_date`	No	Upper bound of the date range filter, if any.
`start_date`	No	Lower bound of the date range filter, if any.
`entity_name`	Yes	Entity name that was searched.
`total_notices`	Yes	Total notices returned after deduplication, sorting, and cap.
`max_notices_cap`	Yes	The max_notices cap applied. Upstream may have more matching notices.
`notice_type_filter`	No	Notice code filter applied, or null if all codes searched.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed3 schema fields changedAug 23, 2026

changedInput schema / properties / notice_type / description

Previous value: -"Filter by notice code (e.g. '2441' winding-up petition, '2443' winding-up order, '2448' administration order, '2460' striking-off). Omit to search all."New value: +"Filter by Gazette notice code (e.g. '2450' petition to wind up a company, '2452' winding-up order, '2410' appointment of administrators). Omit to search all."

changedOutput schema / properties / notices / items / properties / notice_code / description

Previous value: -"Gazette notice code (e.g. '2443' winding-up order, '2448' administration order)."New value: +"Gazette notice code (e.g. '2450' petition to wind up a company, '2452' winding-up order for a company)."

changedOutput schema / properties / notices / items / properties / severity / description

Previous value: -"Internal severity score 0-10. Higher = more serious (10 = Winding-Up Order, 9 = Administration Order / Receiver, 0 = unclassified)."New value: +"Internal severity score 0-10. Higher = more serious (10 = winding-up order, 9 = administration/receiver/liquidator appointment, 0 = informational or unclassified)."

Changed9 schema fields changedJul 28, 2026

addedInput schema / properties / entity_name / anyOf

Added value: +[
+  {
+    "maxLength": 200,
+    "minLength": 2,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / entity_name / default
```
Added value: +null
```

changedInput schema / properties / entity_name / description

Previous value: -"Company or individual name to search for in Gazette insolvency notices"New value: +"Deprecated alias for name."

removedInput schema / properties / entity_name / maxLength
```
Removed value: -200
```
removedInput schema / properties / entity_name / minLength
```
Removed value: -2
```
removedInput schema / properties / entity_name / type
```
Removed value: -"string"
```

addedInput schema / properties / name

Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 200,
+      "minLength": 2,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Company or individual name to search for in Gazette insolvency notices"
+}

addedInput schema / properties / query

Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 200,
+      "minLength": 2,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Alias for name."
+}

removedInput schema / required
```
Removed value: -[
-  "entity_name"
-]
```

AddedMay 16, 2026
RemovedMay 16, 2026

Changed2 schema fields changedApr 28, 2026

changedInput schema / properties / max_notices / description

Previous value: -"Global cap on total notices returned across all codes, after severity/date sort. Default 20. Raise up to 140 (14 codes × 10) to see the full result set."New value: +"Cap on notices returned, applied after severity/date sort. Default 20. The Gazette insolvency feed returns up to 100 results per search — raise to 100 to see the full set."

changedInput schema / properties / max_notices / maximum
```
Previous value: -140New value: +100
```

Changed8 schema fields changedApr 28, 2026

removedInput schema / properties / max_content_chars

Removed value: -{
-  "default": 500,
-  "description": "Per-notice cap on the free-text `content` field. Default 500 keeps responses bounded; raise for notices where the full legal wording matters.",
-  "maximum": 20000,
-  "minimum": 50,
-  "type": "integer"
-}

changedOutput schema / properties / notices / items / properties / content / description

Previous value: -"Notice body. May be truncated per the `max_content_chars` input."New value: +"Brief notice excerpt from the search feed (HTML stripped). For full legal wording read notice://{notice_numeric_id}."

removedOutput schema / properties / notices / items / properties / content_original_length

Removed value: -{
-  "default": 0,
-  "description": "Original length of the notice content before truncation.",
-  "type": "integer"
-}

removedOutput schema / properties / notices / items / properties / content_truncated

Removed value: -{
-  "default": false,
-  "description": "True if content was truncated.",
-  "type": "boolean"
-}

changedOutput schema / properties / notices / items / properties / date / description

Previous value: -"Publication/notice date (ISO format where available)."New value: +"Publication date (ISO YYYY-MM-DD)."

removedOutput schema / properties / notices / items / properties / edition

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Gazette edition identifier."
-}

changedOutput schema / properties / notices / items / properties / notice_id / description

Previous value: -"Upstream notice ID (typically a URI)."New value: +"Gazette notice URI (e.g. 'https://www.thegazette.co.uk/id/notice/5122793')."

addedOutput schema / properties / notices / items / properties / notice_numeric_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Numeric notice ID. Read full notice content via the notice://{notice_numeric_id} resource."
+}

Changed4 schema fields changedApr 28, 2026

addedInput schema / properties / max_notices

Added value: +{
+  "default": 20,
+  "description": "Global cap on total notices returned across all codes, after severity/date sort. Default 20. Raise up to 140 (14 codes × 10) to see the full result set.",
+  "maximum": 140,
+  "minimum": 1,
+  "type": "integer"
+}

addedOutput schema / properties / max_notices_cap

Added value: +{
+  "description": "The max_notices cap applied. Upstream may have more matching notices.",
+  "type": "integer"
+}

changedOutput schema / properties / total_notices / description

Previous value: -"Total notices returned after deduplication and sorting."New value: +"Total notices returned after deduplication, sorting, and cap."

changedOutput schema / required

Previous value: -[
-  "entity_name",
-  "total_notices"
-]New value: +[
+  "entity_name",
+  "total_notices",
+  "max_notices_cap"
+]

Changed12 schema fields changedApr 16, 2026

addedInput schema / properties / max_content_chars

Added value: +{
+  "default": 500,
+  "description": "Per-notice cap on the free-text `content` field. Default 500 keeps responses bounded; raise for notices where the full legal wording matters.",
+  "maximum": 20000,
+  "minimum": 50,
+  "type": "integer"
+}

removedInput schema / properties / response_format

Removed value: -{
-  "default": "markdown",
-  "description": "Output format: 'markdown' or 'json'",
-  "type": "string"
-}

changedOutput schema / description

Previous value: -"Generic wrapper for non-object return types."New value: +"Aggregated Gazette insolvency notice search result."

addedOutput schema / properties / end_date

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Upper bound of the date range filter, if any."
+}

addedOutput schema / properties / entity_name

Added value: +{
+  "description": "Entity name that was searched.",
+  "type": "string"
+}

addedOutput schema / properties / notice_type_filter

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Notice code filter applied, or null if all codes searched."
+}

addedOutput schema / properties / notices

Added value: +{
+  "description": "Matching notices, sorted by severity (desc) then date (desc).",
+  "items": {
+    "description": "A single corporate insolvency notice from The Gazette.",
+    "properties": {
+      "content": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Notice body. May be truncated per the `max_content_chars` input."
+      },
+      "content_original_length": {
+        "default": 0,
+        "description": "Original length of the notice content before truncation.",
+        "type": "integer"
+      },
+      "content_truncated": {
+        "default": false,
+        "description": "True if content was truncated.",
+        "type": "boolean"
+      },
+      "date": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Publication/notice date (ISO format where available)."
+      },
+      "edition": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Gazette edition identifier."
+      },
+      "notice_code": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Gazette notice code (e.g. '2443' winding-up order, '2448' administration order)."
+      },
+      "notice_id": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Upstream notice ID (typically a URI)."
+      },
+      "notice_type": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Human-readable notice type label (e.g. 'Winding-Up Order')."
+      },
+      "severity": {
+        "default": 0,
+        "description": "Internal severity score 0-10. Higher = more serious (10 = Winding-Up Order, 9 = Administration Order / Receiver, 0 = unclassified).",
+        "type": "integer"
+      },
+      "title": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Notice title."
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

removedOutput schema / properties / result

Removed value: -{
-  "type": "string"
-}

addedOutput schema / properties / start_date

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Lower bound of the date range filter, if any."
+}

addedOutput schema / properties / total_notices

Added value: +{
+  "description": "Total notices returned after deduplication and sorting.",
+  "type": "integer"
+}

changedOutput schema / required

Previous value: -[
-  "result"
-]New value: +[
+  "entity_name",
+  "total_notices"
+]

removedOutput schema / x-fastmcp-wrap-result
```
Removed value: -true
```

First observedApr 14, 2026

TDQS

A4.3/5.0

Behavior4/5

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

It adds meaningful behavioral context beyond the read-only annotations: results are sorted by an internal DD severity score, the notice label is a source fact, each result contains a notice_numeric_id, and the Gazette publication is legally effective. This helps the agent interpret results correctly, though rate limits and pagination behavior are not discussed.

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?

The description is front-loaded with the action, then gives sorting behavior, next-step guidance, and legal context. Every sentence serves a purpose, and the phrasing is compact for a tool with seven parameters and an output schema.

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?

The tool has full schema coverage, a rich output schema, and annotations, so the description only needs to supply the interpretative context: sorting semantics, source authority, and the notice:// follow-up. It does adequately, giving the agent enough context to invoke the tool and use its results correctly.

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 explains every parameter. The description adds modest semantic value by referencing entity-name search and the Gazette notice-code taxonomy, but it does not materially extend what the input schema already states.

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 names a specific verb ('Search') and resource ('The Gazette's corporate-insolvency notice index'), and adds distinguishing context by stating that results can be followed up via the notice:// resource for full legal wording. This separates it from related tools like gazette_notice and company_search even though those siblings are not explicitly named.

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 gives clear context for when this tool is appropriate: searching insolvency notices by entity name, filtering by notice code and date, and then reading full legal text via the notice resource. It does not explicitly list when not to use the tool or name alternative siblings, but the intended usage is strongly implied and supported by the schema.

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

All UK Due Diligence tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0

Disambiguation4/5

The domain-specific tools are clearly distinct (search vs profile for each register), and the generic search/fetch tools are designed to route across them. Potential overlap between company_officers and company_psc is resolved by clear descriptions of officers vs beneficial ownership. Slight ambiguity exists between generic fetch/search and the domain-specific counterparts, but the routing logic is well-documented.

Naming Consistency4/5

Most tools follow a consistent resource_action pattern with clear prefixes (charity_, company_, disqualified_, gazette_). Exceptions like company_officers, company_psc, sanctions_screen, and vat_validate deviate from the verb-first convention, and generic tools (fetch, search, get_prompt, list_prompts) do not follow the pattern. Overall, the naming is readable and predictable despite a few outliers.

Tool Count4/5

With 17 tools, the server sits slightly above the typical 3-15 well-scoped range, but the breadth of the domain (Companies House, Charity Commission, disqualifications, Gazette insolvency, sanctions, land registry, VAT) justifies the count. Each tool serves a distinct data source or action, and the two prompt-management tools are standard MCP utilities. The count feels appropriate rather than excessive.

Completeness4/5

The server covers the core due diligence workflow: searching and retrieving profiles for companies, charities, and disqualified directors, plus insolvency notices, sanctions screening, land transactions, and VAT validation. Minor gaps exist, such as no direct tool for company accounts or court judgments, but these are not core to the apparent purpose and can be worked around.

Search Gazette Corporate Insolvency Notices

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources