Apollo.io

Connect Claude Code + Cowork to Apollo MCP via this plugin

MCP Servers Listed MIT

Is Apollo.io safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 5.4 / 10
Provenance None
Signed commits 42%
Last push 10d ago

In detail: Apollo.io scores 56.1/100 (Grade C), ranked #750 of 1325 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; last pushed 2026-09-16. Every point is earned from checkable signals — never paid placement. How scoring works →

How Apollo.io compares in MCP Servers

  1. #415 Licinexus MCP 56.1 ±0
  2. #416 Paparats – Local Semantic Code Search MCP 56.1 ±0
  3. #417 Apollo.io 56.1 this agent
  4. #418 Webull OpenAPI 56.1 ±0
  5. #419 Git MCP Server 56.1 ±0

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

Where the 56.1 comes from

HVTrust dimensions vs the MCP Servers average

56.1 / 100 · 100.0% confidence

Apollo.io MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
8.8 / 25
1.5 below avg 10.3
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.6 below avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
13.1 / 17
0.9 above avg 12.2
Maintenance60% last-push freshness · 40% commit activity
12.5 / 20
in line with avg 12.1
AdoptionLog-scaled stars · package downloads
5.2 / 20
2.0 below avg 7.2

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
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
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.
40.8
Activity sub-score · out of 100
#417

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-09-26 06:32 UTC · Repo last pushed 10 days ago

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars
25
Forks
9
Last Push
2026-09-16
10 days ago
Commits (4 wk)
1
Downloads (7d)
23
npm
HN mentions (30d)
—
Open Issues
2
Rank Change
▼5
was #745

Analysis

Activity Inputs

40.8 / 100
StarsRepository reach
8.5 / 30
FreshnessLast push recency
23.6 / 25
ActivityRecent commits
3.8 / 25
CommunityFork signal
4.7 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
5.4 / 10
OpenSSF Scorecard · scanned Sep 21, 2026
Signed Commits
42%
of last 100 commits verified
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 5
Packaging -1
Pinned-Dependencies 0
SAST 0
Security-Policy 10
Signed-Releases -1
Token-Permissions 9
Vulnerabilities 10

Common questions about Apollo.io

Apollo.io has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
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 10 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.

Reputation Timeline

Signal history
Rank 23HVTrust 6Listed 2Surface 2Score 2Grade 2Scorecard 1Delisted 1MCP 1Surface 1
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

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 56.1 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.3 · Raw JSON