Is Screaming Frog SEO Spider MCP Server safe to use?

Screaming Frog SEO Spider MCP Server has an HVTrust score of 68.8/100 (Grade B), ranked #358 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Screaming Frog SEO Spider MCP Server?

Screaming Frog SEO Spider MCP Server scores 68.8/100 on HVTracker's evidence-weighted HVTrust scale. It has 88 GitHub stars and is categorized under MCP Servers.

Screaming Frog SEO Spider MCP Server

bzsasson/screaming-frog-mcp

Headless MCP server for Screaming Frog SEO Spider – run crawls, export and analyze crawl data via the CLI. Small locked-down tool surface for scheduled audits, CI, and unattended AI agents.

MCP Servers Python Listed MIT

Is Screaming Frog SEO Spider MCP Server safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 3.7 / 10

Provenance Attested

Signed commits 10%

Last push 26d ago

Compare Screaming Frog SEO Spider MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Screaming Frog SEO Spider MCP Server scores 68.8/100 (Grade B), ranked #358 of 1325 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 3.7/10; 10% of recent commits are signed; last pushed 2026-08-31. Every point is earned from checkable signals — never paid placement. How scoring works →

How Screaming Frog SEO Spider MCP Server compares in MCP Servers

#212 Federal Compass MCP 68.9 +0.1
#213 MCP Probe Kit 68.8 ±0
#214 Screaming Frog SEO Spider MCP Server 68.8 this agent
#215 Whoop MCP 68.7 −0.1
#216 MCP Local Rag 68.7 −0.1

Bars show each HVTrust score; the tick marks Screaming Frog SEO Spider MCP Server’s 68.8.

Where the 68.8 comes from

HVTrust dimensions vs the MCP Servers average

68.8 / 100 · 100.0% confidence

Screaming Frog SEO Spider MCP Server MCP Servers average (775 agents)

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

12.6 / 25

2.3 above avg 10.3

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.6 above avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

11.6 / 17

0.6 below avg 12.2

Maintenance60% last-push freshness · 40% commit activity

13.4 / 20

1.3 above avg 12.1

AdoptionLog-scaled stars · package downloads

7.2 / 20

in line with avg 7.2

Quick Trust Read

What Would Improve It

Increase the share of verified signed commits for clearer maintainer identity.

Recent Changes

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → B

Maintainer Checklist

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

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Compare with another agent Get email alerts for Screaming Frog SEO Spider MCP Server View MCP Servers Report missing data

48.7

Activity sub-score · out of 100

#214

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 B 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-09-26

Activity & Reach

Stars

Forks

Last Push

2026-08-31

26 days ago

Commits (4 wk)

Downloads (7d)

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▲2

was #360

Analysis

Activity Inputs

48.7 / 100

StarsRepository reach

11.7 / 30

FreshnessLast push recency

21.4 / 25

ActivityRecent commits

9.7 / 25

CommunityFork signal

5.8 / 20

Supply Chain Trust

Package Provenance

Verified

pypi attestation

OSSF Scorecard

3.7 / 10

OpenSSF Scorecard · scanned Sep 19, 2026

Signed Commits

10%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests -1

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 5

Packaging 10

Pinned-Dependencies 2

SAST 0

Security-Policy 10

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Common questions about Screaming Frog SEO Spider MCP Server

Screaming Frog SEO Spider MCP Server 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 Screaming Frog SEO Spider MCP Server publish package provenance?

Yes. Screaming Frog SEO Spider MCP Server's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does Screaming Frog SEO Spider MCP Server have an OpenSSF Scorecard?

Screaming Frog SEO Spider MCP Server has an OpenSSF Scorecard score of 3.7/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 Screaming Frog SEO Spider MCP Server actively maintained?

Maintained. Last push was 26 days ago.

What license does Screaming Frog SEO Spider MCP Server use?

Screaming Frog SEO Spider MCP Server ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Screaming Frog SEO Spider MCP Server's commits signed?

10% of the last 100 commits to Screaming Frog SEO Spider 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.

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

Screaming Frog SEO Spider MCP Server appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

None detected

No clear third-party provider dependency detected.

Credential signal: No explicit API-key/config marker detected.

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 Screaming Frog SEO Spider 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-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-08-12

Tool Surface Changed

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

Maintain Screaming Frog SEO Spider MCP Server?

For maintainers

HVTrust scores Screaming Frog SEO Spider 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-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → B

2026-09-23

Rank Moved

Rank rose 671 spots (#1018 → #347)

2026-09-23

HVTrust Changed

HVTrust up 44.6pts (24.5 → 69.1)

2026-09-22

Newly Listed

First tracked at rank #1018

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-14

Rank Moved

Rank dropped 14 spots (#314 → #328)

2026-09-13

Rank Moved

Rank dropped 11 spots (#303 → #314)

2026-09-08

Rank Moved

Rank rose 13 spots (#295 → #282)

2026-09-07

Rank Moved

Rank dropped 18 spots (#277 → #295)

2026-09-05

Rank Moved

Rank dropped 58 spots (#216 → #274)

2026-09-04

Rank Moved

Rank dropped 10 spots (#206 → #216)

2026-09-03

Rank Moved

Rank dropped 10 spots (#196 → #206)

2026-09-01

Scorecard Added

OSSF Scorecard: 4.1/10

2026-09-01

Grade Changed

Trust grade C → B

2026-09-01

Rank Moved

Rank rose 170 spots (#368 → #198)

2026-09-01

HVTrust Changed

HVTrust up 9.2pts (61.5 → 70.7)

2026-08-31

Rank Moved

Rank rose 145 spots (#513 → #368)

2026-08-31

HVTrust Changed

HVTrust up 6.9pts (54.6 → 61.5)

2026-08-31

Activity Score Changed

Activity score up 21pts (31 → 52)

2026-08-29

Rank Moved

Rank dropped 27 spots (#488 → #515)

2026-08-27

Rank Moved

Rank dropped 13 spots (#467 → #480)

2026-08-26

Rank Moved

Rank dropped 52 spots (#415 → #467)

2026-08-24

Rank Moved

Rank dropped 19 spots (#397 → #416)

2026-08-22

Rank Moved

Rank rose 16 spots (#413 → #397)

2026-08-19

Rank Moved

Rank dropped 13 spots (#396 → #409)

2026-08-17

Rank Moved

Rank rose 14 spots (#408 → #394)

2026-08-13

Rank Moved

Rank dropped 15 spots (#385 → #400)

2026-08-12

Tool Surface Changed

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

2026-08-12

Rank Moved

Rank rose 19 spots (#404 → #385)

2026-08-10

Rank Moved

Rank dropped 18 spots (#383 → #401)

2026-08-08

Newly Listed

First tracked at rank #372

GitHub → PyPI: screaming-frog-mcp

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/screaming-frog-seo-spider-mcp-server.svg)](https://hvtracker.net/agents/screaming-frog-seo-spider-mcp-server)
            
HTML:
            <a href="https://hvtracker.net/agents/screaming-frog-seo-spider-mcp-server"><img src="https://hvtracker.net/badge/screaming-frog-seo-spider-mcp-server.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