regdata-company-lookup vs Entity-ID Resolver
regdata-company-lookup is a plugin bundle for AI coding tools published by nolpak14. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Entity-ID Resolver is an MCP server published by entityresolver.xyz. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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
| Marketplace |  regdata-company-lookup | |
|---|---|---|
| Community marketplace nolpak14/getregdata | Listed Version: not stated Forks (GitHub): 0 Stars (GitHub): 6 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.2.0 Downloads/month (npm): 152 Downloads/week (npm): 37 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
| Fact | regdata-company-lookup | Entity-ID Resolver |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 6 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (getregdata-mcp) | On your machine (entityresolver-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 2, secrets among them: 1 |
| Parts of the bundle (differs) | 29 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/nolpak14/getregdata | Not stated |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
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
regdata-company-lookup
Free company lookups straight from official public APIs across 28 jurisdictions plus global LEI resolution - no Apify token and no per-result cost. Resolve and verify a company by name or national identifier.
Entity-ID Resolver
Ambiguous name/ticker to verified IDs: SEC CIK, GLEIF LEI, ISIN, Wikidata, CoinGecko. Non-US too.
How to run each
regdata-company-lookup As a Claude Code plugin
/plugin marketplace add nolpak14/getregdata
/plugin install regdata-company-lookup@getregdataEntity-ID Resolver As a local MCP server: npm package
claude mcp add --env "BUYER_PRIVATE_KEY=<YOUR_BUYER_PRIVATE_KEY>" --transport stdio resolver -- npx -y entityresolver-mcpRequires: BUYER_PRIVATE_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only regdata-company-lookup asks for
APIFY_TOKEN (secret)
Only Entity-ID Resolver asks for
BUYER_PRIVATE_KEY (secret)ENTITYRESOLVER_URL
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: regdata-company-lookup · What it can do: Entity-ID Resolver · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.