# CompanyVerify (remote · api.companyverify.uk)

UK company lookup, LEIs and sanctions name matching for agents, with source provenance.

- Trust score: 57/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `api.companyverify.uk`: 57/100 (this document), [markdown](https://verifymcp.io/servers/greg-wilko-companyverify/api.md), [page](https://verifymcp.io/servers/greg-wilko-companyverify/api)

## Channel facts

- Endpoint: `https://api.companyverify.uk/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 21 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1519 tokens (~72/item across 21 items; 21 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability check failed: schema churn in the 3 days we've observed: 0 tool removals, 5 breaking changes, 0 auth/transport breaks, 1 additions.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "charge_register" implies "charge" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the CompanyVerify MCP server?

CompanyVerify is a hosted endpoint at https://api.companyverify.uk/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http greg-wilko-companyverify 'https://api.companyverify.uk/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "greg-wilko-companyverify": {
      "url": "https://api.companyverify.uk/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "greg-wilko-companyverify": {
      "type": "http",
      "url": "https://api.companyverify.uk/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.greg-wilko-companyverify]
url = "https://api.companyverify.uk/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "greg-wilko-companyverify": {
      "type": "remote",
      "url": "https://api.companyverify.uk/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add greg-wilko-companyverify --url 'https://api.companyverify.uk/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  greg-wilko-companyverify:
    url: "https://api.companyverify.uk/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "greg-wilko-companyverify": {
      "Transport": "http",
      "Url": "https://api.companyverify.uk/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add greg-wilko-companyverify -t streamable-http -u 'https://api.companyverify.uk/mcp'
```

### Other

```json
{
  "mcpServers": {
    "greg-wilko-companyverify": {
      "type": "http",
      "url": "https://api.companyverify.uk/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 57, 0)

- [functional regression] Schema quality: 1354 → 1519
- [functional] New tool “counterparty_evidence”

### 2026-11-04 (score 57, 0)

- [security regression] Stability: 0.03 → fail
- [security regression] A breaking change shipped without a version bump: still 0.1.0
- [security] Tool “lei_lookup” rewrote its description, which is the text the model reads
- [functional regression] “fca_register_check” added a required parameter “identifier_type”, so existing callers break
- [functional regression] “fca_register_check” added a required parameter “identifier_value”, so existing callers break
- [functional regression] “kyb_verdict” added a required parameter “identifier_type”, so existing callers break
- [functional regression] “kyb_verdict” added a required parameter “identifier_value”, so existing callers break
- [functional regression] “lei_lookup” added a required parameter “identifier_type”, so existing callers break
- [functional regression] “lei_lookup” added a required parameter “identifier_value”, so existing callers break
- [functional regression] “uk_insolvency_notices” added a required parameter “identifier_type”, so existing callers break
- [functional regression] “uk_insolvency_notices” added a required parameter “identifier_value”, so existing callers break
- [functional regression] “vessel_sanctions” added a required parameter “identifier_type”, so existing callers break
- [functional regression] “vessel_sanctions” added a required parameter “identifier_value”, so existing callers break
- [cosmetic] “fca_register_check” dropped the optional parameter “firm”
- [cosmetic] “fca_register_check” dropped the optional parameter “frn”
- [cosmetic] “kyb_verdict” dropped the optional parameter “company_number”
- [cosmetic] “kyb_verdict” dropped the optional parameter “name”
- [cosmetic] “lei_lookup” dropped the optional parameter “lei”
- [cosmetic] “lei_lookup” dropped the optional parameter “name”
- [cosmetic] “uk_insolvency_notices” dropped the optional parameter “company_number”
- [cosmetic] “uk_insolvency_notices” dropped the optional parameter “name”
- [cosmetic] “vessel_sanctions” dropped the optional parameter “imo”
- [cosmetic] “vessel_sanctions” dropped the optional parameter “name”

### 2026-11-03 (score 57, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-02 (score 57)

First indexed and scored.

## MCP tools (21)

### `uk_company_search` (~74 tokens)

UK company search

Search the UK Companies House register by name or number. Returns candidate companies with number, status, type, incorporation date and registered address, with provenance. Primary source with retrieval timestamp; cached for up to 24 hours.

Input parameters:

- `limit` (integer): Max results
- `q` (string, required): Company name or company number

### `uk_company_profile` (~76 tokens)

UK company profile with officers

Full Companies House profile for a company number: status, SIC codes, registered office, accounts and confirmation statement dates, plus the first page of officers (up to 35), with explicit total/coverage metadata. Primary source, cached for up to 24 hours, provenance attached.

Input parameters:

- `company_number` (string, required): Companies House number

### `lei_lookup` (~98 tokens)

LEI lookup (GLEIF)

Resolve a legal entity to its Legal Entity Identifier via the GLEIF API. Supply identifier_type as lei or name, and identifier_value accordingly. Returns LEI, legal name, jurisdiction, status and registration dates. CC0 source data, provenance attached.

Input parameters:

- `identifier_type` (string, required): Whether identifier_value is a 20-character LEI or a legal name
- `identifier_value` (string, required): 20-character LEI or legal entity name

### `sanctions_screen` (~90 tokens)

Sanctions screen (primary lists)

Screen a person or entity name against sanctions lists loaded directly from primary government sources (configurable: OFAC SDN and consolidated, the UK Sanctions List). Returns match verdict, candidate hits with scores, list versions and retrieval timestamps. Not a PEP or adverse-media screen.

Input parameters:

- `name` (string, required): Person or entity name to screen
- `threshold` (number): Match threshold 0..1

### `entity_match` (~111 tokens)

Entity match verdict

Compare two company references using supplied company-number/LEI equality and normalised name similarity. When one reference has a UK company number and the other only a name, optionally corroborates against Companies House. LEIs are compared as supplied, not validated against GLEIF by this tool. Returns a verdict, heuristic confidence and signal provenance.

Input parameters:

- `a` (object, required): First reference: {name, company_number?, lei?}
- `b` (object, required): Second reference: {name, company_number?, lei?}

### `counterparty_evidence` (~165 tokens)

UK counterparty evidence pack

In one call, assemble a Companies House candidate and profile with optional GLEIF and sanctions evidence. Supply a company number for a direct lookup, or a name and optional registered postcode for candidate resolution. Exact title matches are preferred; ambiguous or fuzzy-only matches are flagged for review. This is evidence assembly, not identity verification, a KYB decision, or sanctions clearance.

Input parameters:

- `company_name` (string): Registered or supplied company name to resolve or compare
- `company_number` (string): Companies House number for a direct lookup
- `include_lei` (boolean): Include GLEIF name candidates
- `include_sanctions` (boolean): Include screening against the configured sanctions lists
- `registered_postcode` (string): Optional postcode to compare with the register address

### `uk_psc_ubo` (~62 tokens)

UK beneficial ownership (PSC) resolution

Roadmap probe, not yet served: resolved beneficial-ownership chain for a UK company from PSC data, entity-resolved across registries. Calling this records your requirement and returns a structured not-covered response.

Input parameters:

- `company_number` (string, required): company_number

### `cross_registry_resolve` (~78 tokens)

Cross-registry entity resolution

Roadmap probe, not yet served: resolve a company across Companies House, GLEIF, OpenOwnership and sanctions lists into one entity record with per-assertion provenance. Calling records the ask and returns not-covered.

Input parameters:

- `identifiers` (object): identifiers
- `jurisdiction` (string): jurisdiction
- `name` (string, required): name

### `pep_screen` (~65 tokens)

PEP screen

Roadmap probe, not yet served: politically exposed person screening. Calling records the requirement and returns a structured not-covered response. Sanctions-only screening is live at /v1/screen/sanctions.

Input parameters:

- `country` (string): country
- `name` (string, required): name

### `adverse_media` (~39 tokens)

Adverse media screen

Roadmap probe, not yet served: adverse media screening with citations. Calling records the requirement and returns not-covered.

Input parameters:

- `name` (string, required): name

### `uk_director_changes` (~53 tokens)

Director change monitoring

Roadmap probe, not yet served: per-entity change feed for officer appointments and resignations, priced per delta. Calling records the requirement and returns not-covered.

Input parameters:

- `company_number` (string, required): company_number

### `uk_insolvency_notices` (~73 tokens)

Insolvency notice feed (Gazette)

Roadmap probe, not yet served: structured Gazette insolvency notices for a monitored entity, per event. Calling records the requirement.

Input parameters:

- `identifier_type` (string, required): Whether identifier_value is a Companies House number or entity name
- `identifier_value` (string, required): Companies House number or entity name to monitor

### `fca_register_check` (~69 tokens)

FCA register check

Roadmap probe, not yet served: authorisation status of a firm or individual on the FCA register. Calling records the requirement.

Input parameters:

- `identifier_type` (string, required): Whether identifier_value is an FCA reference number or firm name
- `identifier_value` (string, required): FCA reference number or firm name

### `kyb_verdict` (~92 tokens)

Full KYB verdict

Roadmap probe, not yet served: single-call KYB verdict (exists, active, officers, PSC, sanctions, insolvency) with signed provenance receipt. Calling records the requirement and returns not-covered.

Input parameters:

- `identifier_type` (string, required): Whether identifier_value is a Companies House number or company name
- `identifier_value` (string, required): Companies House number or company name
- `jurisdiction` (string): jurisdiction

### `vessel_sanctions` (~69 tokens)

Vessel sanctions screen

Roadmap probe, not yet served: screen a vessel (IMO, name, flag) against sanctions designations. Calling records the requirement.

Input parameters:

- `identifier_type` (string, required): Whether identifier_value is an IMO number or vessel name
- `identifier_value` (string, required): IMO number or vessel name

### `uk_procurement_awards` (~45 tokens)

UK procurement award lookup

Roadmap probe, not yet served: contract awards for a supplier from Find a Tender OCDS data. Calling records the requirement.

Input parameters:

- `supplier` (string, required): supplier

### `eu_vat_check` (~38 tokens)

EU VAT number check

Roadmap probe, not yet served: VIES VAT validation with provenance. Calling records the requirement.

Input parameters:

- `vat` (string, required): vat

### `registry_doc_fetch` (~54 tokens)

Registry filing fetch

Roadmap probe, not yet served: fetch and parse a specific Companies House filing into structured JSON. Calling records the requirement.

Input parameters:

- `company_number` (string, required): company_number
- `filing_type` (string): filing_type

### `charge_register` (~40 tokens)

Charges register lookup

Roadmap probe, not yet served: outstanding charges and security for a UK company. Calling records the requirement.

Input parameters:

- `company_number` (string, required): company_number

### `find_capability` (~35 tokens)

Find a data capability

Search live and honestly planned data capabilities. Searches inform build priority.

Input parameters:

- `query` (string): What data or verdict you need

### `request_data` (~93 tokens)

Request a dataset or capability

State a data requirement, intended use, expected monthly volume and acceptable price. Free and logged to inform build priority.

Input parameters:

- `contact` (string): Optional contact for a future reply
- `description` (string, required): The data or verdict you need
- `max_price_usd` (number): max_price_usd
- `use_case` (string): use_case
- `volume_per_month` (integer): volume_per_month

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/greg-wilko-companyverify/api#diagnostics

## Score history

- 2026-11-05: 57
- 2026-11-04: 57
- 2026-11-03: 57
- 2026-11-02: 57

## Common questions

### What is the CompanyVerify MCP server?

CompanyVerify is an MCP server listed in the public MCP registry as io.github.greg-wilko/companyverify. UK company lookup, LEIs and sanctions name matching for agents, with source provenance. This page covers its hosted endpoint (https://api.companyverify.uk/mcp).

### Is the CompanyVerify MCP server safe to use?

CompanyVerify scores 57 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the CompanyVerify MCP server expose?

CompanyVerify exposes 21 tools: uk_company_search, uk_company_profile, lei_lookup, sanctions_screen, entity_match, and 16 more. Their descriptions and schemas cost roughly 1,519 tokens of context every time the server is loaded.

### Does the CompanyVerify MCP server require authentication?

No. We connected to CompanyVerify without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the CompanyVerify MCP server still maintained?

CompanyVerify is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://api.companyverify.uk/mcp
- Website: https://companyverify.uk/
- Changelog RSS feed: https://verifymcp.io/servers/greg-wilko-companyverify/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/greg-wilko-companyverify/api.json
- HTML version of this page: https://verifymcp.io/servers/greg-wilko-companyverify/api