@mrfentmen/apollo-mcp

MCPcommunity
v1.1.1UnknownMITUpdated 8d agonpmGitHub

Query Apollo.io (free key; set APOLLO_API_KEY, X-Api-Key header): account health, person match, people search.

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
8Downloads/wk
8d agoLast update
Package
AuthorUnknown
LicenseMIT
Version1.1.1
Sourcenpm+mcp-registry
npm@mrfentmen/apollo-mcp
GitHubmrfentmen/premium-mcps
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface10 tools · none privileged
Security scan✓ Cleanv1.1.1 · 5d agoHow well does this scan work?
EvalsNone
IndexedOct 19, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

10 tools · none privileged
Statically extracted from the published packagev1.1.1 · 5d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

healthCheck that the Apollo API key still works.

Check that the Apollo API key still works.

No input schema was published for this tool.

match_personMatch one person by email, name or company.

Match one person by email, name or company.

No input schema was published for this tool.

search_peopleProspect search by title, location and company size.

Prospect search by title, location and company size.

No input schema was published for this tool.

people_searchProspects by keywords.

Prospects by keywords.

No input schema was published for this tool.

company_searchCompanies by name.

Companies by name.

No input schema was published for this tool.

org_enrichCompany by domain.

Company by domain.

No input schema was published for this tool.

bulk_matchUp to 10 emails.

Up to 10 emails.

No input schema was published for this tool.

get_contactContact by ID.

Contact by ID.

No input schema was published for this tool.

account_searchAccounts by name.

Accounts by name.

No input schema was published for this tool.

people_search_v1Prospects by job title.

Prospects by job title.

No input schema was published for this tool.

10 of 10 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Query Apollo.io (free key; set APOLLO_API_KEY, X-Api-Key header): account health, person match, people search.

Keywords
mcpapollosalesleadsenrichment
Alternatives
Comparing tool surfaces…

Tools exposed

10 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-10-19 — observed resolution, not a publisher declaration.

60 packages resolved · 2 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

55 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+43 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.