updated 2026-11-10 04:07 UTC

Screaming Frog SEO Spider MCP Server

Repository

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 4.8 / 10
Provenance Attested
Signed commits 14%
Last push 24d ago
Advisories None known
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 73.0/100 (Grade B), ranked #308 of 1374 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 4.8/10; 14% of recent commits are signed; no published advisory affects its latest release (screaming-frog-mcp); last pushed 2026-10-17. Every point is earned from checkable signals — never paid placement. How scoring works →

How Screaming Frog SEO Spider 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 Screaming Frog SEO Spider 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 Partly signed

    github.com/bzsasson/screaming-frog-mcp, MIT, last pushed 2026-10-17. 14% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

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

    • Code Review0
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies1
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 0
    Contributors 0
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 1
    SAST 0
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 9

  3. Published packages Linked and attested

  4. What you install today No known advisories

    Latest release checked: screaming-frog-mcp 0.4.3. No published advisory affects it (OSV, checked 2026-11-09).

Changes to this chain

  • 2026-09-23 Package provenance attestation detected
  • 2026-09-01 OSSF Scorecard: 4.1/10

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 Screaming Frog SEO Spider 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 Screaming Frog SEO Spider MCP Server compares in MCP Servers

  1. #180 Tavily MCP 73.0 ±0
  2. #181 Yantrikdb MCP 73.0 ±0
  3. #182 Screaming Frog SEO Spider MCP Server 73.0 this agent
  4. #183 build123d MCP 72.9 −0.1
  5. #184 Arm MCP Server 72.8 −0.2

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

Where the 73.0 comes from

HVTrust dimensions vs the MCP Servers average

73.0 / 100 · 100.0% confidence

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

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
14.2 / 25
3.4 above avg 10.8
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.3 above avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
12.6 / 17
in line with avg 12.3
Maintenance60% last-push freshness · 40% commit activity
14.0 / 20
1.8 above avg 12.2
AdoptionLog-scaled stars · package downloads
8.2 / 20
0.6 above avg 7.6

Quick Trust Read

What Would Improve It
Increase the share of verified signed commits for clearer maintainer identity.
Recent Changes
2026-10-25
Rank Moved
Rank rose 34 spots (#301 → #267)
2026-10-21
Rank Moved
Rank rose 55 spots (#353 → #298)
2026-10-18
Rank Moved
Rank rose 11 spots (#365 → #354)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.8/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
View MCP Servers Report missing data
51.0
Activity sub-score · out of 100
#182
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 →

Signals refreshed 2026-11-10 04:07 UTC · Repo last pushed 24 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
95
Forks
19
Last Push
2026-10-17
24 days ago
Commits (4 wk)
7
Downloads (7d)
385
pypi
HN mentions (30d)
—
Open Issues
0
Rank Change
▼3
was #305

Analysis

Activity Inputs

51.0 / 100
StarsRepository reach
11.9 / 30
FreshnessLast push recency
21.7 / 25
ActivityRecent commits
11.3 / 25
CommunityFork signal
6.0 / 20

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 4.8/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 24 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?
14% 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

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
Rank 25Grade 6HVTrust 5Score 3Scorecard 1Delisted 1Listed 1Provenance 1MCP 1
2026-10-25
Rank Moved
Rank rose 34 spots (#301 → #267)
2026-10-21
Rank Moved
Rank rose 55 spots (#353 → #298)
2026-10-18
Rank Moved
Rank rose 11 spots (#365 → #354)
2026-10-17
Grade Changed
Trust grade C → B
2026-10-17
Rank Moved
Rank rose 159 spots (#524 → #365)
2026-10-17
HVTrust Changed
HVTrust up 4.8pts (64.7 → 69.5)
2026-10-17
Activity Score Changed
Activity score up 18pts (36 → 54)
2026-10-12
Grade Changed
Trust grade B → C
2026-10-11
Grade Changed
Trust grade C → B
2026-10-09
Grade Changed
Trust grade B → C
2026-10-09
Rank Moved
Rank dropped 12 spots (#492 → #504)
2026-10-07
Rank Moved
Rank dropped 12 spots (#478 → #490)
2026-09-30
Rank Moved
Rank dropped 96 spots (#365 → #461)
2026-09-30
HVTrust Changed
HVTrust down 3.2pts (68.7 → 65.5)
2026-09-30
Activity Score Changed
Activity score down 10pts (48 → 38)
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)
GitHub → PyPI: screaming-frog-mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 73.0 Grade B
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.4 · Raw JSON