Ext Ops Panel
Open dashboard
Comparison

com.mcparmory/apollo vs Zovo Sanctions Screening

com.mcparmory/apollo is an MCP server published by mcparmory.com. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). Zovo Sanctions Screening is an MCP server published by theluckystrike. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. 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
Marketplacecom.mcparmory/apolloZovo Sanctions Screening
Official MCP Registry Listed
Version: 1.0.4
Downloads/month (PyPI): 886
Downloads/week (PyPI): 165
Forks (GitHub): 4
Stars (GitHub): 32
Not marked · First seen
Listed
Version: 1.0.0
No figure published
Not marked · First seen
PyPI (MCP servers) Listed
Version: 1.0.4
Downloads/month (PyPI): 886
Downloads/week (PyPI): 165
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

com.mcparmory/apollo vs Zovo Sanctions Screening
Factcom.mcparmory/apolloZovo Sanctions Screening
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)32No figure on GitHub
Forks (GitHub) (differs)4No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcparmory-apollo)Remote server (ofac-screening.zovo.one/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)MITNot stated
Repository (differs)github.com/mcparmory/registryNot stated
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-22
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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/apollo

In its own words, on Official MCP Registry:

Search and enrich contact and company data from 210M+ people and 35M+ companies

Zovo Sanctions Screening

In its own words, on Official MCP Registry:

Run an ofac search on business names and get a dated XLSX screening log.

How to run each

com.mcparmory/apollo As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio apollo -- uvx mcparmory-apollo

Zovo Sanctions Screening As a remote MCP server

Claude Code
claude mcp add --transport http ofac-screening https://ofac-screening.zovo.one/mcp

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

Neither one's marketplaces publish the settings it asks for.

What it can do: com.mcparmory/apollo · What it can do: Zovo Sanctions Screening · 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.

Where the data comes from: how the catalog is built