Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

CompanyVerify

REMOTE · API.COMPANYVERIFY.UK

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

57 Trust /100

Last scanned (22 hours ago)

Scores higher than 43% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Security

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security46
Transport & Reachability100
Schema Quality & AI Usability66
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1354 tokens (~67/item across 20 items; 20 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability check failed: schema churn in the 2 days we've observed: 0 tool removals, 5 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 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. See how to fix → Fail
  • An AI judge read all 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 0
    • Stability: 0.03 → fail ▼ security
    • 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 security
    • “fca_register_check” added a required parameter “identifier_type”, so existing callers break ▼ functional
    • “fca_register_check” added a required parameter “identifier_value”, so existing callers break ▼ functional
    • “kyb_verdict” added a required parameter “identifier_type”, so existing callers break ▼ functional
    • “kyb_verdict” added a required parameter “identifier_value”, so existing callers break ▼ functional
    • “lei_lookup” added a required parameter “identifier_type”, so existing callers break ▼ functional
    • “lei_lookup” added a required parameter “identifier_value”, so existing callers break ▼ functional
    • “uk_insolvency_notices” added a required parameter “identifier_type”, so existing callers break ▼ functional
    • “uk_insolvency_notices” added a required parameter “identifier_value”, so existing callers break ▼ functional
    • “vessel_sanctions” added a required parameter “identifier_type”, so existing callers break ▼ functional
    • “vessel_sanctions” added a required parameter “identifier_value”, so existing callers break ▼ functional
    • “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” cosmetic
  • 3 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 2 Nov 26 57

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 4 Nov 2026 · Probed https://api.companyverify.uk/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=companyverify.uk CN=YE2,O=Let's Encrypt,C=US 2 Nov 2026 31 Jan 2027 ECDSA 256 ECDSA-SHA384 6bb268fd5a8e0e8a858e96ff34f3914ffa2
SANs: *.companyverify.uk, companyverify.uk
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.companyverify.uk. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
uk. present 43876 8 Verified
companyverify.uk. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.companyverify.uk/mcp Verified 200
http (plaintext) http://api.companyverify.uk/mcp Inconclusive 405
MCP tools · 20 exposed · ~1,354 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
adverse_media ~39

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

NameTypeReqDescription
namestringyesname

No output schema declared.

No examples provided.

charge_register ~40

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

NameTypeReqDescription
company_numberstringyescompany_number

No output schema declared.

No examples provided.

cross_registry_resolve ~78

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.

NameTypeReqDescription
identifiersobject–identifiers
jurisdictionstring–jurisdiction
namestringyesname

No output schema declared.

No examples provided.

entity_match ~111

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.

NameTypeReqDescription
aobjectyesFirst reference: {name, company_number?, lei?}
bobjectyesSecond reference: {name, company_number?, lei?}

No output schema declared.

No examples provided.

eu_vat_check ~38

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

NameTypeReqDescription
vatstringyesvat

No output schema declared.

No examples provided.

fca_register_check ~69

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

NameTypeReqDescription
identifier_typestringyesWhether identifier_value is an FCA reference number or firm name
identifier_valuestringyesFCA reference number or firm name

No output schema declared.

No examples provided.

find_capability ~35

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

NameTypeReqDescription
querystring–What data or verdict you need

No output schema declared.

No examples provided.

kyb_verdict ~92

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.

NameTypeReqDescription
identifier_typestringyesWhether identifier_value is a Companies House number or company name
identifier_valuestringyesCompanies House number or company name
jurisdictionstring–jurisdiction

No output schema declared.

No examples provided.

lei_lookup ~98

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.

NameTypeReqDescription
identifier_typestringyesWhether identifier_value is a 20-character LEI or a legal name
identifier_valuestringyes20-character LEI or legal entity name

No output schema declared.

No examples provided.

pep_screen ~65

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.

NameTypeReqDescription
countrystring–country
namestringyesname

No output schema declared.

No examples provided.

registry_doc_fetch ~54

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

NameTypeReqDescription
company_numberstringyescompany_number
filing_typestring–filing_type

No output schema declared.

No examples provided.

request_data ~93

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

NameTypeReqDescription
contactstring–Optional contact for a future reply
descriptionstringyesThe data or verdict you need
max_price_usdnumber–max_price_usd
use_casestring–use_case
volume_per_monthinteger–volume_per_month

No output schema declared.

No examples provided.

sanctions_screen ~90

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.

NameTypeReqDescription
namestringyesPerson or entity name to screen
thresholdnumber–Match threshold 0..1

No output schema declared.

No examples provided.

uk_company_profile ~76

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.

NameTypeReqDescription
company_numberstringyesCompanies House number

No output schema declared.

No examples provided.

uk_company_search ~74

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.

NameTypeReqDescription
limitinteger–Max results
qstringyesCompany name or company number

No output schema declared.

No examples provided.

uk_director_changes ~53

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.

NameTypeReqDescription
company_numberstringyescompany_number

No output schema declared.

No examples provided.

uk_insolvency_notices ~73

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

NameTypeReqDescription
identifier_typestringyesWhether identifier_value is a Companies House number or entity name
identifier_valuestringyesCompanies House number or entity name to monitor

No output schema declared.

No examples provided.

uk_procurement_awards ~45

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

NameTypeReqDescription
supplierstringyessupplier

No output schema declared.

No examples provided.

uk_psc_ubo ~62

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.

NameTypeReqDescription
company_numberstringyescompany_number

No output schema declared.

No examples provided.

vessel_sanctions ~69

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

NameTypeReqDescription
identifier_typestringyesWhether identifier_value is an IMO number or vessel name
identifier_valuestringyesIMO number or vessel name

No output schema declared.

No examples provided.

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.

remote · api.companyverify.uk

# add to Claude Code
claude mcp add --transport http greg-wilko-companyverify 'https://api.companyverify.uk/mcp'
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 20 tools: uk_company_search, uk_company_profile, lei_lookup, sanctions_screen, entity_match, and 15 more. Their descriptions and schemas cost roughly 1,354 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 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.