updated 2026-08-12 05:02 UTC

Librecrawl — Technical SEO Audit MCP Server

adityaarsharma/librecrawl-technical-seo-audit-mcp

The AI-native technical SEO crawler. Open-source MCP server for Claude / Cursor / Codex — 37 tools, 50+ checks, unlimite

MCP Servers Python Grade D Listed MIT
19.9/100
Rank #1076 of 1283
Compare Librecrawl — Technical SEO Audit MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade D · 1/5 signals
Last push
2026-07-28 · 15d ago
Recent change
Rank +1

Is Librecrawl — Technical SEO Audit MCP Server safe? Librecrawl — Technical SEO Audit MCP Server scores 19.9/100 (Grade D), ranked #1076 of 1283 tracked open-source AI agent projects, on evidence coverage D (1 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 50% of recent commits are signed; last pushed 2026-07-28. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#592 Danishashko Yahoo Finance — 20.0 (D) → #593 Slack Explorer MCP — 19.9 (D) → #595 Local Memory — 19.9 (D) → #596 Switzerland MCP 🇨🇭 — 19.9 (D) →

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-10
Rank Moved
Rank dropped 66 spots (#1007 → #1073)
2026-08-08
Newly Listed
First tracked at rank #982
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
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
41.5
Activity sub-score · out of 100
#594
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 D is separate — it grades how many independent signal types back the score (1 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-08-12 05:02 UTC · Repo last pushed 15 days ago

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars
34
Forks
4
Last Push
2026-07-28
15 days ago
Commits (4 wk)
2
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
1
Rank Change
▲1
was #1077

Analysis

HVTrust Dimensions vs MCP Servers

19.9 / 100 · 50.0% confidence

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

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
2.5 / 25
2.5 below avg 5.0
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.5 below avg 13.3
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
in line with avg 8.8
Maintenance60% last-push freshness · 40% commit activity
12.9 / 20
in line with avg 12.4
AdoptionLog-scaled stars · package downloads
3.7 / 20
2.1 below avg 5.8

Activity Inputs

41.5 / 100
StarsRepository reach
9.3 / 30
FreshnessLast push recency
22.9 / 25
ActivityRecent commits
6.0 / 25
CommunityFork signal
3.3 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
50%
of last 100 commits verified

Is Librecrawl — Technical SEO Audit MCP Server safe?

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?
No OpenSSF Scorecard data is currently published for Librecrawl — Technical SEO Audit MCP Server. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is Librecrawl — Technical SEO Audit MCP Server actively maintained?
Maintained. Last push was 15 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?
50% 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
medium confidence
Declared
Declared plugin/integration 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

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
Listed 1Rank 1
2026-08-10
Rank Moved
Rank dropped 66 spots (#1007 → #1073)
2026-08-08
Newly Listed
First tracked at rank #982
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 19.9 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)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON