com.mcparmory/perigon vs Company Data
com.mcparmory/perigon is an MCP server published by mcparmory.com. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). Company Data is an MCP server published by projectworks007. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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 |  com.mcparmory/perigon |  Company Data |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.3 Downloads/month (PyPI): 823 Downloads/week (PyPI): 148 Forks (GitHub): 4 Stars (GitHub): 32 Not marked · First seen |
Listed Version: 1.0.1 Forks (GitHub): 1 Stars (GitHub): 0 Not marked · First seen |
| PyPI (MCP servers) | Listed Version: 1.0.3 Downloads/month (PyPI): 823 Downloads/week (PyPI): 148 Forks (GitHub): 4 Stars (GitHub): 32 Not marked · First seen |
Not listed |
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 | com.mcparmory/perigon | Company Data |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 32 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 4 (better) | 1 (worse) |
| Last release (differs) | Not published | 2026-10-24 |
| Where it runs (differs) | On your machine (mcparmory-perigon) | Remote server (mcp.apify.com) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/mcparmory/registry | github.com/projectworks007/apify-data-mcp |
| Changes in the last 7 days (differs) | 0 | 3 |
| First seen (differs) | 2026-10-11 | 2026-10-20 |
| Endpoint at the last check (differs) | no remote endpoint we check | Not responding since 2026-10-24 |
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
com.mcparmory/perigon
Search real-time news articles, companies, journalists, and trending topics
Company Data
Company data for AI agents: enrich a domain, UK Companies House records, Y Combinator companies.
How to run each
com.mcparmory/perigon As a local MCP server: PyPI package
claude mcp add --transport stdio perigon -- uvx mcparmory-perigonCompany Data
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Company Data 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
Neither one's marketplaces publish the settings it asks for.
What it can do: com.mcparmory/perigon · What it can do: Company Data · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.