updated 2026-09-26 06:32 UTC

Scrapegraph MCP

ScrapeGraphAI/scrapegraph-mcp

ScapeGraph MCP Server

MCP Servers Python Listed MIT

Is Scrapegraph MCP safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 3.0 / 10
Provenance None
Signed commits 27%
Last push 71d ago
Compare Scrapegraph MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Scrapegraph MCP scores 46.8/100 (Grade D), ranked #1027 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 3.0/10; 27% of recent commits are signed; last pushed 2026-07-17. Every point is earned from checkable signals — never paid placement. How scoring works →

How Scrapegraph MCP compares in MCP Servers

  1. #601 Browserbase MCP Server 46.8 ±0
  2. #602 Funplay Godot MCP 46.8 ±0
  3. #603 Scrapegraph MCP 46.8 this agent
  4. #604 Agrobr MCP 46.5 −0.3
  5. #605 Devcontainer MCP 46.4 −0.4

Bars show each HVTrust score; the tick marks Scrapegraph MCP’s 46.8.

Where the 46.8 comes from

HVTrust dimensions vs the MCP Servers average

46.8 / 100 · 100.0% confidence

Scrapegraph MCP MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.1 / 25
5.2 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
11.1 / 17
1.1 below avg 12.2
Maintenance60% last-push freshness · 40% commit activity
7.3 / 20
4.8 below avg 12.1
AdoptionLog-scaled stars · package downloads
7.5 / 20
in line with 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-25
Rank Moved
Rank dropped 11 spots (#1012 → #1023)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank rose 173 spots (#1185 → #1012)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.0/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.
Refresh maintenance signals The repo was last pushed 71 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent Get email alerts for Scrapegraph MCP View MCP Servers Report missing data
34.8
Activity sub-score · out of 100
#603
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 D 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 71 days ago

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars
113
Forks
34
Last Push
2026-07-17
71 days ago
Commits (4 wk)
0
Downloads (7d)
83
pypi
HN mentions (30d)
—
Open Issues
2
Rank Change
▼4
was #1023

Analysis

Activity Inputs

34.8 / 100
StarsRepository reach
12.3 / 30
FreshnessLast push recency
15.1 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
7.2 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
3.0 / 10
OpenSSF Scorecard · scanned Sep 19, 2026
Signed Commits
27%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests 8
CII-Best-Practices 0
Code-Review 0
Contributors 6
Dangerous-Workflow 10
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 6
Packaging -1
Pinned-Dependencies 0
SAST 0
Security-Policy 0
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 0

Common questions about Scrapegraph MCP

Public trust evidence for Scrapegraph MCP 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 Scrapegraph MCP publish package provenance?
No published build provenance is currently detected for Scrapegraph MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Scrapegraph MCP have an OpenSSF Scorecard?
Scrapegraph MCP has an OpenSSF Scorecard score of 3.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 Scrapegraph MCP actively maintained?
Slowing down. Last push was 71 days ago — keep an eye on whether activity resumes.
What license does Scrapegraph MCP use?
Scrapegraph MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Scrapegraph MCP's commits signed?
27% of the last 100 commits to Scrapegraph MCP 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
high confidence
Implemented
Scrapegraph MCP 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 Scrapegraph MCP'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
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain Scrapegraph MCP?

For maintainers

HVTrust scores Scrapegraph MCP 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 24HVTrust 3Listed 2Score 1Scorecard 1Delisted 1MCP 1
2026-09-25
Rank Moved
Rank dropped 11 spots (#1012 → #1023)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank rose 173 spots (#1185 → #1012)
2026-09-23
HVTrust Changed
HVTrust up 27.4pts (19.7 → 47.1)
2026-09-22
Newly Listed
First tracked at rank #1185
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-16
Rank Moved
Rank rose 10 spots (#1004 → #994)
2026-09-12
Rank Moved
Rank dropped 11 spots (#985 → #996)
2026-09-11
Rank Moved
Rank dropped 13 spots (#972 → #985)
2026-09-09
Rank Moved
Rank dropped 17 spots (#955 → #972)
2026-09-08
Rank Moved
Rank dropped 15 spots (#940 → #955)
2026-09-07
Rank Moved
Rank dropped 41 spots (#899 → #940)
2026-09-06
Rank Moved
Rank dropped 15 spots (#884 → #899)
2026-09-05
Rank Moved
Rank dropped 51 spots (#833 → #884)
2026-09-04
Rank Moved
Rank dropped 38 spots (#795 → #833)
2026-09-03
Rank Moved
Rank rose 340 spots (#1135 → #795)
2026-09-03
HVTrust Changed
HVTrust up 16.3pts (32.1 → 48.4)
2026-09-02
Rank Moved
Rank dropped 40 spots (#1095 → #1135)
2026-09-01
Rank Moved
Rank dropped 42 spots (#1053 → #1095)
2026-08-31
Scorecard Added
OSSF Scorecard: 3.0/10
2026-08-31
Rank Moved
Rank rose 192 spots (#1245 → #1053)
2026-08-31
HVTrust Changed
HVTrust up 13.4pts (18.8 → 32.2)
2026-08-30
Rank Moved
Rank dropped 14 spots (#1231 → #1245)
2026-08-29
Rank Moved
Rank dropped 18 spots (#1213 → #1231)
2026-08-28
Rank Moved
Rank dropped 16 spots (#1197 → #1213)
2026-08-27
Rank Moved
Rank dropped 13 spots (#1184 → #1197)
2026-08-26
Rank Moved
Rank dropped 52 spots (#1132 → #1184)
2026-08-16
Rank Moved
Rank dropped 69 spots (#1060 → #1129)
2026-08-16
Activity Score Changed
Activity score down 6pts (46 → 39)
2026-08-15
Rank Moved
Rank dropped 18 spots (#1042 → #1060)
2026-08-13
Rank Moved
Rank dropped 10 spots (#1026 → #1036)
2026-08-10
Rank Moved
Rank dropped 60 spots (#966 → #1026)
2026-08-08
Newly Listed
First tracked at rank #961
GitHub → PyPI: scrapegraph-mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 46.8 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/scrapegraph-mcp.svg)](https://hvtracker.net/agents/scrapegraph-mcp)
HTML:
<a href="https://hvtracker.net/agents/scrapegraph-mcp"><img src="https://hvtracker.net/badge/scrapegraph-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

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