updated 2026-10-18 00:07 UTC

Librecrawl — Technical SEO Audit MCP Server

Repository Website

Sitewalk: Technical SEO Site Audit. Open-source technical SEO crawler and MCP server for Claude, Cursor and Codex. 50+ checks, PDF and CSV reports, self-hosted. Built on LibreCrawl. MIT.

MCP Servers Python Listed MIT

Is Librecrawl — Technical SEO Audit MCP Server safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 3.2 / 10
Provenance None
Signed commits 62%
Last push 8d ago
Compare Librecrawl — Technical SEO Audit MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Librecrawl — Technical SEO Audit MCP Server scores 49.8/100 (Grade D), ranked #1020 of 1378 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.2/10; 62% of recent commits are signed; last pushed 2026-10-10. Every point is earned from checkable signals — never paid placement. How scoring works →

How Librecrawl — Technical SEO Audit 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 Librecrawl — Technical SEO Audit MCP Server and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/adityaarsharma/librecrawl-technical-seo-audit-mcp, MIT, last pushed 2026-10-10. 62% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

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

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

  3. Published packages None

    No registry package. Librecrawl — Technical SEO Audit MCP Server is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

  • 2026-08-30 OSSF Scorecard: 2.5/10

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads (missing)
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Librecrawl — Technical SEO Audit 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 Librecrawl — Technical SEO Audit MCP Server compares in MCP Servers

  1. #575 Memory Journal MCP 49.8 ±0
  2. #576 MCPSpend 49.8 ±0
  3. #577 Librecrawl — Technical SEO Audit MCP Server 49.8 this agent
  4. #578 Fanout MCP 49.8 ±0
  5. #579 Codex MCP Tool 49.7 −0.1

Bars show each HVTrust score; the tick marks Librecrawl — Technical SEO Audit MCP Server’s 49.8.

Where the 49.8 comes from

HVTrust dimensions vs the MCP Servers average

49.8 / 100 · 100.0% confidence

Librecrawl — Technical SEO Audit MCP Server MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.1 / 25
3.5 below avg 10.6
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.8 below avg 13.6
Transparency50% declared license · 50% OSSF Scorecard
11.2 / 17
1.1 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
15.8 / 20
3.6 above avg 12.2
AdoptionLog-scaled stars · package downloads
3.9 / 20
3.5 below avg 7.4

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-16
Grade Changed
Trust grade C → D
2026-10-14
Rank Moved
Rank dropped 14 spots (#993 → #1007)
2026-10-11
Rank Moved
Rank dropped 24 spots (#959 → #983)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.2/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.
Compare with another agent Get email alerts for Librecrawl — Technical SEO Audit MCP Server View MCP Servers Report missing data
51.6
Activity sub-score · out of 100
#577
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 C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-10-18 00:07 UTC · Repo last pushed 8 days ago

Rank Trend

2026-09-29 2026-10-17

Activity & Reach

Stars
43
Forks
7
Last Push
2026-10-10
8 days ago
Commits (4 wk)
11
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
4
Rank Change
▲3
was #1023

Analysis

Activity Inputs

51.6 / 100
StarsRepository reach
9.9 / 30
FreshnessLast push recency
23.9 / 25
ActivityRecent commits
13.5 / 25
CommunityFork signal
4.2 / 20

Common questions about Librecrawl — Technical SEO Audit MCP Server

Public trust evidence for Librecrawl — Technical SEO Audit MCP Server 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 Librecrawl — Technical SEO Audit MCP Server publish package provenance?
No published build provenance is currently detected for Librecrawl — Technical SEO Audit MCP Server. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Librecrawl — Technical SEO Audit MCP Server have an OpenSSF Scorecard?
Librecrawl — Technical SEO Audit MCP Server has an OpenSSF Scorecard score of 3.2/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 Librecrawl — Technical SEO Audit MCP Server actively maintained?
Maintained. Last push was 8 days ago.
What license does Librecrawl — Technical SEO Audit MCP Server use?
Librecrawl — Technical SEO Audit MCP Server ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Librecrawl — Technical SEO Audit MCP Server's commits signed?
61% of the last 100 commits to Librecrawl — Technical SEO Audit 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
Librecrawl — Technical SEO Audit 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
N/A
No package source configured
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 Librecrawl — Technical SEO Audit 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-08-12
Tool Surface Changed
Detected tool/plugin surface changed: declared → none

Maintain Librecrawl — Technical SEO Audit MCP Server?

For maintainers

HVTrust scores Librecrawl — Technical SEO Audit 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 28Grade 4HVTrust 3Listed 2Surface 1Scorecard 1Delisted 1MCP 1Score 1
2026-10-16
Grade Changed
Trust grade C → D
2026-10-14
Rank Moved
Rank dropped 14 spots (#993 → #1007)
2026-10-11
Rank Moved
Rank dropped 24 spots (#959 → #983)
2026-10-10
Grade Changed
Trust grade D → C
2026-10-10
Rank Moved
Rank rose 60 spots (#1019 → #959)
2026-10-07
Rank Moved
Rank dropped 22 spots (#989 → #1011)
2026-10-06
Rank Moved
Rank dropped 23 spots (#966 → #989)
2026-10-05
Grade Changed
Trust grade C → D
2026-10-04
Grade Changed
Trust grade D → C
2026-10-04
Rank Moved
Rank rose 35 spots (#994 → #959)
2026-09-26
Rank Moved
Rank rose 28 spots (#1004 → #976)
2026-09-25
Rank Moved
Rank rose 162 spots (#1166 → #1004)
2026-09-25
HVTrust Changed
HVTrust up 7.7pts (40.0 → 47.7)
2026-09-25
Activity Score Changed
Activity score up 19pts (31 → 50)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank dropped 333 spots (#832 → #1165)
2026-09-23
HVTrust Changed
HVTrust up 11.9pts (28.2 → 40.1)
2026-09-22
Newly Listed
First tracked at rank #832
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-12
Rank Moved
Rank dropped 12 spots (#1136 → #1148)
2026-09-09
Rank Moved
Rank dropped 14 spots (#1118 → #1132)
2026-09-07
Rank Moved
Rank dropped 20 spots (#1090 → #1110)
2026-09-06
Rank Moved
Rank dropped 19 spots (#1071 → #1090)
2026-09-05
Rank Moved
Rank dropped 46 spots (#1025 → #1071)
2026-09-04
Rank Moved
Rank dropped 23 spots (#1002 → #1025)
2026-09-03
Rank Moved
Rank dropped 57 spots (#945 → #1002)
2026-09-02
Rank Moved
Rank dropped 51 spots (#894 → #945)
2026-09-01
Rank Moved
Rank dropped 34 spots (#860 → #894)
2026-08-31
Rank Moved
Rank dropped 31 spots (#829 → #860)
2026-08-30
Scorecard Added
OSSF Scorecard: 2.5/10
2026-08-30
Rank Moved
Rank rose 397 spots (#1226 → #829)
2026-08-30
HVTrust Changed
HVTrust up 22.8pts (18.8 → 41.6)
2026-08-29
Rank Moved
Rank dropped 11 spots (#1215 → #1226)
2026-08-28
Rank Moved
Rank dropped 17 spots (#1198 → #1215)
2026-08-27
Rank Moved
Rank dropped 31 spots (#1167 → #1198)
2026-08-26
Rank Moved
Rank dropped 52 spots (#1115 → #1167)
2026-08-16
Rank Moved
Rank dropped 33 spots (#1071 → #1104)
2026-08-13
Rank Moved
Rank dropped 28 spots (#1046 → #1074)
2026-08-12
Tool Surface Changed
Detected tool/plugin surface changed: declared → none
2026-08-12
Rank Moved
Rank rose 31 spots (#1077 → #1046)
2026-08-10
Rank Moved
Rank dropped 66 spots (#1007 → #1073)
2026-08-08
Newly Listed
First tracked at rank #982
GitHub → Website →

Embed Badge Badge guide for maintainers →

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

Other agents in MCP Servers

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