com.mcparmory/apollo
OCI · GHCR.IO/MCPARMORY/APOLLO:1.0.4 · 2 COMPONENTS · SCANNED SEP 20
Search and enrich contact and company data from 210M+ people and 35M+ companies
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- Malware scan not yet available for this package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 131 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 9186 tokens (~176/item across 52 items; 52 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 52 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 52 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the com.mcparmory/apollo MCP server?
com.mcparmory/apollo runs locally as a container image, launched with docker run --rm -i ghcr.io/mcparmory/apollo:1.0.4. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/mcparmory/apollo:1.0.4
claude mcp add com-mcparmory-apollo -- docker run --rm -i ghcr.io/mcparmory/apollo:1.0.4
{
"mcpServers": {
"com-mcparmory-apollo": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/apollo:1.0.4"
]
}
}
} {
"servers": {
"com-mcparmory-apollo": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/apollo:1.0.4"
]
}
}
} codex mcp add com-mcparmory-apollo -- docker run --rm -i ghcr.io/mcparmory/apollo:1.0.4
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mcparmory-apollo": {
"type": "local",
"command": [
"docker",
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/apollo:1.0.4"
],
"enabled": true
}
}
} mcp_servers:
com-mcparmory-apollo:
command: "docker"
args: ["run", "--rm", "-i", "ghcr.io/mcparmory/apollo:1.0.4"] {
"McpServers": {
"com-mcparmory-apollo": {
"Transport": "stdio",
"Command": "docker",
"Arguments": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/apollo:1.0.4"
]
}
}
} {
"mcpServers": {
"com-mcparmory-apollo": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/apollo:1.0.4"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 −3
- Stability: pass → 0.83 functional
- 18 Sept 26 +1
- Stability: 0.97 → pass security
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 −3
- Stability: pass → 0.80 functional
- 11 Sept 26 +1
- Stability: 0.97 → pass security
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed oci/ghcr.io/mcparmory/apollo:1.0.4
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
update_opportunity Update Opportunity ~222
Update an existing deal in your Apollo account. Modify deal details such as name, monetary value, owner, stage, and close date to keep your pipeline current.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | – | The monetary value of the deal as a numeric string without commas or currency symbols. The currency is determined by your Apollo account settings. |
| closed_date | string | – | The estimated close date for the deal in YYYY-MM-DD format. |
| name | string | – | A human-readable name for the deal. |
| opportunity_id | string | yes | The unique identifier of the deal to update. |
| opportunity_stage_id | string | – | The ID of the deal stage for this opportunity. Retrieve available stage IDs from the List Deal Stages endpoint. |
| owner_id | string | – | The user ID of the deal owner within your team. Retrieve available user IDs from the Get a List of Users endpoint. |
| typed_custom_fields | object | – | Custom field values specific to your team's Apollo account. Use the Get a List of All Custom Fields endpoint to identify field IDs and their required data types. |
No output schema declared.
No examples provided.
update_sequence_contact_status Update Sequence Contact Status ~139
Update the status of contacts within email sequences by marking them as finished, removing them entirely, or stopping their progress. Requires a master API key.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_ids | array | yes | One or more Apollo contact IDs whose sequence status should be updated. These contacts must exist within the specified sequences. |
| emailer_campaign_ids | array | yes | One or more Apollo sequence IDs to update. When multiple sequences are specified, the contact status change applies across all selected sequences. |
| mode | string | yes | The action to perform on the contacts: mark_as_finished to indicate sequence completion, remove to delete contacts from the sequence, or stop to pause their progress. |
No output schema declared.
No examples provided.
What is the com.mcparmory/apollo MCP server?
com.mcparmory/apollo is an MCP server listed in the public MCP registry as com.mcparmory/apollo. Search and enrich contact and company data from 210M+ people and 35M+ companies. This page covers its container image (ghcr.io/mcparmory/apollo:1.0.4).
Is the com.mcparmory/apollo MCP server safe to use?
com.mcparmory/apollo scores 49 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.mcparmory/apollo MCP server expose?
com.mcparmory/apollo exposes 52 tools: enrich_person, enrich_people_bulk, enrich_organization, enrich_organizations, search_people, and 47 more. Their descriptions and schemas cost roughly 9,186 tokens of context every time the server is loaded.
Is the com.mcparmory/apollo MCP server still maintained?
com.mcparmory/apollo is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.