SiteCheck

Search UK company insolvency notices

uk_insolvency

Read-only

UK company insolvency notices (administrations, liquidations, winding-up petitions) from The Gazette, via our nightly cache of the last 8 days. Filter by company name or number, postcode prefix, notice type and date. Returns company, number, notice type, date, nature of business, postcode and notice link, with the cache timestamp and any missing days; up to 10 rows can add Companies House status, SIC codes and address. Related tools on this server, for a different need: uk_company when you need to look up a UK company: officers, PSC and filings. Price: $0.003 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "uk_insolvency"
  }
}

Input Schema

Name	Required	Description
`q`	No	Company name text or company number
`type`	No	administration, liquidation, winding-up, petition, creditors, or a notice name or 4-digit code
`limit`	No	Max rows, 1-200, default 50
`since`	No	YYYY-MM-DD, default 7 days ago, clipped to the cache window
`postcode`	No	Postcode prefix, e.g. SW1 or M1 1AE

Output Schema

Name	Required	Description	Default
`query`	No
`total`	No
`source`	No
`results`	No
`returned`	No
`coveredDays`	No
`missingDays`	No
`dataTimestamp`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 14, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "coveredDays": {},
+    "dataTimestamp": {},
+    "missingDays": {},
+    "query": {},
+    "results": {},
+    "returned": {},
+    "source": {},
+    "total": {}
+  },
+  "type": "object"
+}

First observedOct 8, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations: it discloses the nightly cache with an 8-day window, that the response carries a cache timestamp and any missing days, that only up to 10 rows get Companies House enrichment, and the exact $0.003 x402 pricing with failed calls not charged. These are non-obvious operational facts an agent needs before calling.

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?

Front-loaded with purpose, filters, and returns, then related tools and pricing — a sensible order with no wasted sentences. Slight redundancy: it re-lists the return fields despite an output schema, and 'uk_company when you need to look up a UK company' repeats the same idea twice.

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?

Covers everything an agent needs for a paid, cached, filtered read tool: data source and latency, filter surface, return contents, enrichment limit, freshness caveats, pricing/charging rules, and the sibling alternative. Nothing material is missing relative to its complexity.

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 all five parameters are already documented, and the description largely restates them (name or number, type, postcode prefix, date). Its only added meaning is the hint that enrichment applies to 'up to 10 rows' plus the cache-window clipping, which the schema also states. 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?

States a specific verb+resource (search UK company insolvency notices), names the source (The Gazette), enumerates the notice types covered, and explicitly contrasts with the sibling uk_company. An agent can distinguish it from the other company tools without opening the schema.

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?

Explicitly routes the agent to uk_company 'when you need to look up a UK company: officers, PSC and filings', which is a clear alternative for a different need. It also implies scope via the 8-day cache window, but never states when NOT to use this tool (e.g. older than 8 days, non-insolvency registry queries).

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

All SiteCheck 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.