updated 2026-10-13 00:08 UTC

Apify MCP Server

Repository Website by apify

The Apify MCP server enables your AI agents to extract data from social media, search engines, maps, e-commerce sites, or any other website using thousands of ready-made scrapers, crawlers, and automation tools available on the Apify Store.

MCP Servers TypeScript Listed MIT

Is Apify MCP Server safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 5.5 / 10
Provenance Attested
Signed commits 100%
Last push yesterday
Advisories None known
Compare Apify MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Apify MCP Server scores 89.3/100 (Grade A), ranked #31 of 1371 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 5.5/10; 100% of recent commits are signed; no published advisory affects its latest release (@apify/actors-mcp-server); last pushed 2026-10-12. Every point is earned from checkable signals — never paid placement. How scoring works →

How Apify MCP Server 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 Apify MCP Server 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 Signed

    github.com/apify/apify-mcp-server, MIT, last pushed 2026-10-12. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Mixed

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

    • Code Review5
    • Branch Protection5
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 5
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 5
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 10
    Signed-Releases 0
    Token-Permissions 0
    Vulnerabilities 10

  3. Published packages Linked and attested

  4. What you install today No known advisories

    Latest release checked: @apify/actors-mcp-server 0.17.4. No published advisory affects it (OSV, checked 2026-10-12).

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Apify MCP Server.

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 Apify MCP Server’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 Apify MCP Server compares in MCP Servers

  1. #3 Codebase Memory MCP 90.0 +0.7
  2. #4 SearXNG Search 89.3 ±0
  3. #5 Apify MCP Server 89.3 this agent
  4. #6 LinkedIn MCP Server 89.1 −0.2
  5. #7 KiCad MCP Pro 89.0 −0.3

Bars show each HVTrust score; the tick marks Apify MCP Server’s 89.3.

Where the 89.3 comes from

HVTrust dimensions vs the MCP Servers average

89.3 / 100 · 100.0% confidence

Apify MCP Server MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
19.4 / 25
9.0 above avg 10.4
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.5 above avg 13.5
Transparency50% declared license · 50% OSSF Scorecard
13.2 / 17
1.0 above avg 12.2
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
7.7 above avg 12.2
AdoptionLog-scaled stars · package downloads
15.7 / 20
8.3 above avg 7.4

Quick Trust Read

What Would Improve It
Improve safety / integrity to lift the weakest part of the trust profile.
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.5/10. Tighten the weakest checks to improve public safety evidence.
Compare with Mobile MCP Get email alerts for Apify MCP Server View MCP Servers Report missing data
85.7
Activity sub-score · out of 100
#5
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 A 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-13 00:08 UTC · Repo last pushed yesterday

Rank Trend

2026-09-29 2026-10-12

Activity & Reach

Stars
10.8k
Forks
322
Last Push
2026-10-12
yesterday
Commits (4 wk)
97
Downloads (7d)
31,361
npm
HN mentions (30d)
—
Open Issues
175
Rank Change
▲1
was #32

Analysis

Activity Inputs

85.7 / 100
StarsRepository reach
24.2 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
24.8 / 25
CommunityFork signal
11.7 / 20

Common questions about Apify MCP Server

Public supply-chain signals for Apify MCP Server are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Apify MCP Server carries less obvious unverified-evidence risk than projects with thin signals.
Does Apify MCP Server publish package provenance?
Yes. Apify MCP Server's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Apify MCP Server have an OpenSSF Scorecard?
Apify MCP Server has an OpenSSF Scorecard score of 5.5/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 Apify MCP Server actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Apify MCP Server use?
Apify MCP Server ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Apify MCP Server's commits signed?
100% of the last 100 commits to Apify MCP Server 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.

Compare Apify MCP Server head-to-head

Apify MCP Server vs Mobile MCP → Apify MCP Server vs Playwright MCP → Apify MCP Server vs Codebase Memory MCP →

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
high confidence
Implemented
Apify MCP Server appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
low confidence
None detected
No clear third-party provider dependency detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool 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 Apify MCP Server'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-08-12
Tool Surface Changed
Detected tool/plugin surface changed: extension-based → none
2026-08-12
Provider Removed
Runtime surface shrank — no longer detected: OpenAI

Maintain Apify MCP Server?

For maintainers

HVTrust scores Apify MCP Server 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 2HVTrust 1Surface 1Surface 1
2026-08-12
Tool Surface Changed
Detected tool/plugin surface changed: extension-based → none
2026-08-12
Provider Removed
Runtime surface shrank — no longer detected: OpenAI
2026-08-08
Rank Moved
Rank rose 30 spots (#55 → #25)
2026-08-08
HVTrust Changed
HVTrust up 3.8pts (83.6 → 87.4)
2026-07-21
Rank Moved
Rank rose 12 spots (#37 → #25)
GitHub → Website → npm: @apify/actors-mcp-server

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 89.3 Grade A
Markdown:
[![HVTrust](https://hvtracker.net/badge/apify-mcp-server.svg)](https://hvtracker.net/agents/apify-mcp-server)
HTML:
<a href="https://hvtracker.net/agents/apify-mcp-server"><img src="https://hvtracker.net/badge/apify-mcp-server.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