Ext Ops Panel
Open dashboard
Comparison

US Business Verify vs io.github.aicayzer/companies-house

US Business Verify is an MCP server published by sourcewire.dev. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.aicayzer/companies-house is an MCP server published by aicayzer. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-10. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceUS Business Verifyio.github.aicayzer/companies-house
Official MCP Registry Listed
Version: 0.2.3
No figure published
Not marked · First seen
Listed
Version: 4.0.1
Downloads/month (npm): 994
Downloads/week (npm): 311
Forks (GitHub): 11
Stars (GitHub): 39
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 4.0.1
Downloads/month (npm): 994
Downloads/week (npm): 311
Forks (GitHub): 11
Stars (GitHub): 39
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

US Business Verify vs io.github.aicayzer/companies-house
FactUS Business Verifyio.github.aicayzer/companies-house
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub39
Forks (GitHub) (differs)No figure on GitHub11
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.apify.com)On your machine (companies-house-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 0
Licence (differs)Not statedMIT
Repository (differs)Not statedgithub.com/aicayzer/companies-house-mcp
Changes in the last 7 days00
First seen (differs)2026-10-302026-10-11
Endpoint at the last check (differs)Status out of date: last check 43 h ago returned HTTP 401no remote endpoint we check

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

US Business Verify

In its own words, on Official MCP Registry:

Verify US businesses: TX/NY/CO/CT/OR registry status + OFAC sanctions. PASS/REVIEW/FAIL/INCOMPLETE.

io.github.aicayzer/companies-house

In its own words, on Official MCP Registry:

UK Companies House public register: search companies, officers, ownership, filings and documents.

How to run each

US Business Verify

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

io.github.aicayzer/companies-house As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio companies-house -- npx -y companies-house-mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only US Business Verify has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of US Business Verify publish no settings it asks for, so we do not compare settings.

What it can do: US Business Verify · What it can do: io.github.aicayzer/companies-house · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built