Skip to content

CompanyVerify MCP server

io.github.greg-wilko/companyverifygreg-wilkostreamable-httpv0.1.1Scanned

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

21 tools: 1 do something that can't be undone, 14 change things and 6 only read.

Tools: 0 delete, 1 irreversible, 14 write, 6 read.
  • Reads private data · 1
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the CompanyVerify MCP server can do

The CompanyVerify MCP server is published by the GitHub account greg-wilko. It has 21 tools. It can do things that cannot be undone, such as sending, paying or publishing (charge_register) and create or change data (14 tools: uk_company_profile, sanctions_screen, counterparty_evidence, uk_psc_ubo and 10 more), but cannot delete data. 6 tools only read.

1 tool reads private data (registry_doc_fetch).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 16, 2026, version 0.1.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

21 tools

Can't be undone 1Claude Code: ask
  • charge_registerRoadmap probe, not yet served: outstanding charges and security for a UK company.No findings

    Why it is in this group

    • The name "charge_register" says "charge": a word that usually means money moves, which cannot be taken back.
    Description, as the server wrote it
    Roadmap probe, not yet served: outstanding charges and security for a UK company. Calling records the requirement.
Changes things 14Claude Code: ask
  • adverse_mediaRoadmap probe, not yet served: adverse media screening with citations.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Roadmap probe, not yet served: adverse media screening with citations. Calling records the requirement and returns not-covered.
  • counterparty_evidenceIn one call, assemble a Companies House candidate and profile with optional GLEIF and sanctions evidence.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • eu_vat_checkRoadmap probe, not yet served: VIES VAT validation with provenance.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Roadmap probe, not yet served: VIES VAT validation with provenance. Calling records the requirement.
  • fca_register_checkRoadmap probe, not yet served: authorisation status of a firm or individual on the FCA register.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Roadmap probe, not yet served: authorisation status of a firm or individual on the FCA register. Calling records the requirement.
  • kyb_verdictRoadmap probe, not yet served: single-call KYB verdict (exists, active, officers, PSC, sanctions, insolvency) with signed provenance receipt.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • pep_screenRoadmap probe, not yet served: politically exposed person screening.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • request_dataState a data requirement, intended use, expected monthly volume and acceptable price.No findings

    Why it is in this group

    • The name "request_data" says "request": a word for a change.
    Description, as the server wrote it
    State a data requirement, intended use, expected monthly volume and acceptable price. Free and logged to inform build priority.
  • sanctions_screenScreen a person or entity name against sanctions lists loaded directly from primary government sources (configurable: OFAC SDN and consolidated, the UK Sanctions List).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • uk_company_profileFull 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…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • uk_director_changesRoadmap probe, not yet served: per-entity change feed for officer appointments and resignations, priced per delta.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • uk_insolvency_noticesRoadmap probe, not yet served: structured Gazette insolvency notices for a monitored entity, per event.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Roadmap probe, not yet served: structured Gazette insolvency notices for a monitored entity, per event. Calling records the requirement.
  • uk_procurement_awardsRoadmap probe, not yet served: contract awards for a supplier from Find a Tender OCDS data.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Roadmap probe, not yet served: contract awards for a supplier from Find a Tender OCDS data. Calling records the requirement.
  • uk_psc_uboRoadmap probe, not yet served: resolved beneficial-ownership chain for a UK company from PSC data, entity-resolved across registries.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • vessel_sanctionsRoadmap probe, not yet served: screen a vessel (IMO, name, flag) against sanctions designations.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Roadmap probe, not yet served: screen a vessel (IMO, name, flag) against sanctions designations. Calling records the requirement.
Only reads 6Show 6 read-only tools
  • cross_registry_resolveRoadmap probe, not yet served: resolve a company across Companies House, GLEIF, OpenOwnership and sanctions lists into one entity record with per-assertion provenance.No findings

    Why it is in this group

    • The name "cross_registry_resolve" says "resolve": a word for reading.
    Description, as the server wrote it
    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.
  • entity_matchCompare two company references using supplied company-number/LEI equality and normalised name similarity.No findings

    Why it is in this group

    • The description's first verb is "compare": a word for reading.
    Description, as the server wrote it
    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 an identifier-comparison verdict, review reasons and signal provenance. Names alone remain uncertain. Conflicting identifiers require review; confidence is null because no calibrated identity probability is available.
  • find_capabilitySearch live and honestly planned data capabilities.No findings

    Why it is in this group

    • The name "find_capability" says "find": a word for reading.
    Description, as the server wrote it
    Search live and honestly planned data capabilities. Searches inform build priority.
  • lei_lookupResolve a legal entity to its Legal Entity Identifier via the GLEIF API.No findings

    Why it is in this group

    • The name "lei_lookup" says "lookup": a word for reading.
    Description, as the server wrote it
    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.
  • registry_doc_fetchRoadmap probe, not yet served: fetch and parse a specific Companies House filing into structured JSON.Reads private dataNo findings

    Why it is in this group

    • The name "registry_doc_fetch" says "fetch": a word for reading.

    What it can reach

    • private-dataThe name "registry_doc_fetch" says "fetch" and "doc": it reads documents.
    Description, as the server wrote it
    Roadmap probe, not yet served: fetch and parse a specific Companies House filing into structured JSON. Calling records the requirement.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 17, 2026, 15:22 UTC, unchanged since Nov 10, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
15
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 15 tools that change things (1 irreversible, 14 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.companyverify.uk/mcp: tools/list returned 21 tools to an anonymous client, including charge_register (irreversible), uk_company_profile (write), sanctions_screen (write), counterparty_evidence (write), uk_psc_ubo (write) and 10 more

    What this check looks for

Posture changes

  1. Nov 10, 2026
    • Tools that change things, listed without credentials: 14 to 15

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 added, 7 changed.+1 added~7 changedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 14 -> 15.View diff
    • Tools that change things, listed without credentials: 14 to 15

Install

Pinned to version 0.1.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http companyverify https://api.companyverify.uk/mcp
claude mcp add --transport http companyverify https://api.companyverify.uk/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__companyverify__uk_company_search",
      "mcp__companyverify__lei_lookup",
      "mcp__companyverify__entity_match",
      "mcp__companyverify__cross_registry_resolve",
      "mcp__companyverify__registry_doc_fetch",
      "mcp__companyverify__find_capability"
    ],
    "ask": [
      "mcp__companyverify__uk_company_profile",
      "mcp__companyverify__sanctions_screen",
      "mcp__companyverify__counterparty_evidence",
      "mcp__companyverify__uk_psc_ubo",
      "mcp__companyverify__pep_screen",
      "mcp__companyverify__adverse_media",
      "mcp__companyverify__uk_director_changes",
      "mcp__companyverify__uk_insolvency_notices",
      "mcp__companyverify__fca_register_check",
      "mcp__companyverify__kyb_verdict",
      "mcp__companyverify__vessel_sanctions",
      "mcp__companyverify__uk_procurement_awards",
      "mcp__companyverify__eu_vat_check",
      "mcp__companyverify__charge_register",
      "mcp__companyverify__request_data"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as companyverify. Review it before you use it.

Capability tags behind 1 rule
  • mcp__companyverify__registry_doc_fetch private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.greg-wilko/companyverify/verify?hash=78b7df2279fea9f2810cab384d24d3067ac251a75e103d83a8f04c75b78488af" | jq -e '.changed == false'

Pinned hash 78b7df2279fe, from Nov 16, 2026, 07:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.greg-wilko/companyverify/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.greg-wilko/companyverify
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.greg-wilko/companyverify.svg)](https://radar.anlyon.com/servers/io.github.greg-wilko/companyverify)

Source: MCP Registry. Synced Nov 2, 2026, 23:17 UTC.

CompanyVerify MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the CompanyVerify MCP server safe?

No scan can promise that. What its definitions show: 21 tools, 15 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the CompanyVerify MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the CompanyVerify MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: charge_register.

What tools does the CompanyVerify MCP server have?

21 tools: 1 irreversible, 14 write, 6 read. charge_register, uk_company_profile, sanctions_screen, counterparty_evidence, uk_psc_ubo, pep_screen, adverse_media, uk_director_changes and 13 more.

Does the CompanyVerify MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the CompanyVerify MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the CompanyVerify MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 16, 2026. Every change is on this page and in its Atom feed.