Is Apify MCP Server safe to use?

Apify MCP Server has an HVTrust score of 87.4/100 (Grade A), ranked #26 of 1308 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Apify MCP Server?

Apify MCP Server scores 87.4/100 on HVTracker's evidence-weighted HVTrust scale. It has 4.2k GitHub stars and is categorized under MCP Servers.

Apify MCP Server

apify/apify-mcp-server

The Apify MCP server enables your AI agents to extract data from social media, search engines, maps, e-commerce sites, o

MCP Servers TypeScript Grade A Listed MIT

87.4/100

Rank #26 of 1308

Compare Apify MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Strong public trust posture, backed by multiple independent signals.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-08-18 · 1d ago

Recent change

Tool Surface Changed +1

Is Apify MCP Server safe? Apify MCP Server scores 87.4/100 (Grade A), ranked #26 of 1308 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.0/10; 100% of recent commits are signed; last pushed 2026-08-18. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#1 Codebase Memory MCP — 91.6 (A) → #2 Playwright MCP — 89.5 (A) → #4 Stripe Agent Toolkit — 85.4 (A) → #5 XcodeBuildMCP — 84.9 (A) →

Quick Trust Read

What Would Improve It

Improve adoption to lift the weakest part of the trust profile.

Recent Changes

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)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.0/10. Tighten the weakest checks to improve public safety evidence.

Compare with Codebase Memory MCP Get email alerts for Apify MCP Server View MCP Servers Report missing data

81.7

Activity sub-score · out of 100

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 →

Rank Trend

2026-08-11 2026-08-19

Activity & Reach

Stars

4.2k

Forks

230

Last Push

2026-08-18

yesterday

Commits (4 wk)

Downloads (7d)

14,351

npm

HN mentions (30d)

—

Open Issues

122

Rank Change

was #26

Analysis

HVTrust Dimensions vs MCP Servers

87.4 / 100 · 100.0% confidence

Apify MCP Server MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

18.8 / 25

13.8 above avg 5.0

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.7 above avg 13.3

Transparency50% declared license · 50% OSSF Scorecard

12.8 / 17

4.0 above avg 8.8

Maintenance60% last-push freshness · 40% commit activity

19.6 / 20

7.2 above avg 12.4

AdoptionLog-scaled stars · package downloads

14.2 / 20

8.4 above avg 5.8

Activity Inputs

81.7 / 100

StarsRepository reach

21.7 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

24.0 / 25

CommunityFork signal

11.0 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

5.0 / 10

OpenSSF Scorecard · scanned Aug 18, 2026

Signed Commits

100%

of last 100 commits verified

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 0

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 10

Is Apify MCP Server safe?

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.0/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 Codebase Memory MCP → Apify MCP Server vs Playwright MCP → Apify MCP Server vs Stripe Agent Toolkit →

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

2026-07-13

Tool Surface Changed

Detected tool/plugin surface changed: none → extension-based

2026-07-13

Provider Added

Runtime surface grew — new detected provider dependency: OpenAI

2026-07-13

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-07-13

Provenance Added

Package provenance attestation detected

2026-07-13

Activity Resumed

Activity resumed

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

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)

2026-07-13

Tool Surface Changed

Detected tool/plugin surface changed: none → extension-based

2026-07-13

Provider Added

Runtime surface grew — new detected provider dependency: OpenAI

2026-07-13

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-07-13

Provenance Added

Package provenance attestation detected

2026-07-13

Activity Resumed

Activity resumed

2026-07-13

Grade Changed

Trust grade D → A

2026-07-13

Rank Moved

Rank rose 312 spots (#341 → #29)

2026-07-13

HVTrust Changed

HVTrust up 76.5pts (8.4 → 84.9)

2026-07-13

Activity Score Changed

Activity score up 79pts (0 → 79)

2026-07-12

Newly Listed

First tracked at rank #341

GitHub → npm: @apify/actors-mcp-server

Embed Badge Badge guide for maintainers →

For maintainers

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.3 · Raw JSON