updated 2026-10-16 16:07 UTC

Apollo.io

Repository

Connect Claude Code + Cowork to Apollo MCP via this plugin

MCP Servers Listed MIT

Is Apollo.io safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 5.4 / 10
Provenance None
Signed commits 42%
Last push 30d ago
Advisories None known
Compare Apollo.io

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Apollo.io scores 54.9/100 (Grade C), ranked #844 of 1378 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.4/10; 42% of recent commits are signed; no published advisory affects its latest release (@apolloio/mcp); last pushed 2026-09-16. Every point is earned from checkable signals — never paid placement. How scoring works →

How Apollo.io could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Apollo.io and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/apolloio/apollo-mcp-plugin, MIT, last pushed 2026-09-16. 42% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 5.4/10 (scanned Oct 16, 2026). The checks that decide who can get a change released:

    • Code Review2
    • Branch Protection6
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions9
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 6
    CI-Tests 2
    CII-Best-Practices 0
    Code-Review 2
    Contributors 3
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 4
    Packaging -1
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions 9
    Vulnerabilities 10

  3. Published packages Linked, not attested

    • npm @apolloio/mcp Source link points back to this repo No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: @apolloio/mcp 0.1.1. No published advisory affects it (OSV, checked 2026-10-16).

Changes to this chain

  • 2026-09-02 OSSF Scorecard: 5.4/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Apollo.io’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Apollo.io compares in MCP Servers

  1. #455 Local Memory 55.0 +0.1
  2. #456 Agent Search MCP 55.0 +0.1
  3. #457 Apollo.io 54.9 this agent
  4. #458 DMontgomery40 DeepSeek MCP Server 54.9 ±0
  5. #459 Paper Distill MCP 54.8 −0.1

Bars show each HVTrust score; the tick marks Apollo.io’s 54.9.

Where the 54.9 comes from

HVTrust dimensions vs the MCP Servers average

54.9 / 100 · 100.0% confidence

Apollo.io MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
8.8 / 25
1.7 below avg 10.5
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.7 below avg 13.5
Transparency50% declared license · 50% OSSF Scorecard
13.1 / 17
0.8 above avg 12.3
Maintenance60% last-push freshness · 40% commit activity
11.2 / 20
1.1 below avg 12.3
AdoptionLog-scaled stars · package downloads
5.3 / 20
2.1 below avg 7.4

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-13
Rank Moved
Rank dropped 24 spots (#808 → #832)
2026-10-04
Rank Moved
Rank dropped 10 spots (#765 → #775)
2026-10-02
Rank Moved
Rank dropped 11 spots (#758 → #769)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.4/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with another agent Get email alerts for Apollo.io View MCP Servers Report missing data
38.5
Activity sub-score · out of 100
#457
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-10-16 16:07 UTC · Repo last pushed 30 days ago

Rank Trend

2026-09-29 2026-10-16

Activity & Reach

Stars
29
Forks
10
Last Push
2026-09-16
30 days ago
Commits (4 wk)
1
Downloads (7d)
20
npm
HN mentions (30d)
—
Open Issues
4
Rank Change
▼3
was #841

Analysis

Activity Inputs

38.5 / 100
StarsRepository reach
8.9 / 30
FreshnessLast push recency
20.8 / 25
ActivityRecent commits
3.8 / 25
CommunityFork signal
4.8 / 20

Common questions about Apollo.io

Public trust evidence for Apollo.io is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does Apollo.io publish package provenance?
No published build provenance is currently detected for Apollo.io. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Apollo.io have an OpenSSF Scorecard?
Apollo.io has an OpenSSF Scorecard score of 5.4/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Apollo.io actively maintained?
Maintained. Last push was 30 days ago.
What license does Apollo.io use?
Apollo.io ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Apollo.io's commits signed?
41% of the last 100 commits to Apollo.io are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
medium confidence
Implemented
Apollo.io appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
medium confidence
1 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Apollo.io's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-08-12
Tool Surface Changed
Detected tool/plugin surface changed: marketplace → declared

Maintain Apollo.io?

For maintainers

HVTrust scores Apollo.io from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 26HVTrust 6Listed 2Surface 2Score 2Grade 2Scorecard 1Delisted 1MCP 1Surface 1
2026-10-13
Rank Moved
Rank dropped 24 spots (#808 → #832)
2026-10-04
Rank Moved
Rank dropped 10 spots (#765 → #775)
2026-10-02
Rank Moved
Rank dropped 11 spots (#758 → #769)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank rose 203 spots (#960 → #757)
2026-09-23
HVTrust Changed
HVTrust up 30.1pts (25.6 → 55.7)
2026-09-22
Newly Listed
First tracked at rank #960
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-16
Rank Moved
Rank rose 39 spots (#777 → #738)
2026-09-12
Rank Moved
Rank dropped 13 spots (#756 → #769)
2026-09-11
Rank Moved
Rank rose 99 spots (#855 → #756)
2026-09-11
HVTrust Changed
HVTrust up 3.5pts (51.7 → 55.2)
2026-09-11
Activity Score Changed
Activity score up 7pts (30 → 37)
2026-09-09
Rank Moved
Rank dropped 16 spots (#835 → #851)
2026-09-08
Rank Moved
Rank dropped 13 spots (#822 → #835)
2026-09-07
Rank Moved
Rank dropped 40 spots (#782 → #822)
2026-09-06
Rank Moved
Rank dropped 14 spots (#768 → #782)
2026-09-05
Grade Changed
Trust grade D → C
2026-09-05
Rank Moved
Rank rose 369 spots (#1137 → #768)
2026-09-05
HVTrust Changed
HVTrust up 17.1pts (35.5 → 52.6)
2026-09-04
Rank Moved
Rank dropped 17 spots (#1120 → #1137)
2026-09-03
Rank Moved
Rank dropped 51 spots (#1069 → #1120)
2026-09-02
Scorecard Added
OSSF Scorecard: 5.4/10
2026-09-02
Rank Moved
Rank rose 60 spots (#1129 → #1069)
2026-09-02
HVTrust Changed
HVTrust up 6.0pts (29.6 → 35.6)
2026-09-01
Rank Moved
Rank dropped 41 spots (#1088 → #1129)
2026-08-31
Rank Moved
Rank rose 147 spots (#1235 → #1088)
2026-08-31
HVTrust Changed
HVTrust up 10.4pts (19.2 → 29.6)
2026-08-30
Rank Moved
Rank dropped 230 spots (#1005 → #1235)
2026-08-30
HVTrust Changed
HVTrust down 10.5pts (29.7 → 19.2)
2026-08-29
Rank Moved
Rank dropped 50 spots (#955 → #1005)
2026-08-28
Rank Moved
Rank dropped 35 spots (#920 → #955)
2026-08-27
Rank Moved
Rank dropped 27 spots (#893 → #920)
2026-08-26
Rank Moved
Rank dropped 109 spots (#784 → #893)
2026-08-19
Rank Moved
Rank dropped 34 spots (#749 → #783)
2026-08-19
Activity Score Changed
Activity score down 9pts (42 → 33)
2026-08-16
Rank Moved
Rank dropped 15 spots (#737 → #752)
2026-08-12
Tool Surface Changed
Detected tool/plugin surface changed: marketplace → declared
2026-08-12
Rank Moved
Rank rose 13 spots (#748 → #735)
2026-08-10
Rank Moved
Rank dropped 41 spots (#707 → #748)
2026-08-08
Newly Listed
First tracked at rank #697
GitHub → npm: @apolloio/mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 54.9 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/apollo-io.svg)](https://hvtracker.net/agents/apollo-io)
HTML:
<a href="https://hvtracker.net/agents/apollo-io"><img src="https://hvtracker.net/badge/apollo-io.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON