updated 2026-10-11 12:08 UTC

Seo Crawler MCP

Repository by houtini-ai

MOVED to SEO Audit Console: github.com/houtini-ai/seo-audit - archived. The crawler now ships there, merged with Google Search Console data and ranked by recoverable clicks.

MCP Servers TypeScript Needs review Apache-2.0

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

OSSF Scorecard 2.8 / 10
Provenance None
Signed commits 11%
Last push 64d ago
Advisories None known
Compare Seo Crawler MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Seo Crawler MCP scores 42.6/100 (Grade D), ranked #1147 of 1371 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 2.8/10; 11% of recent commits are signed; no published advisory affects its latest release (@houtini/seo-crawler-mcp); last pushed 2026-08-08. Every point is earned from checkable signals — never paid placement. How scoring works →

How Seo Crawler MCP 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
Active listing, but review is needed
  • [5.1] repository is archived

Chain of custody

Scanners check what the code says. This traces who ships Seo Crawler MCP 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/houtini-ai/seo-crawler-mcp, Apache-2.0, last pushed 2026-08-08. 11% 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 2.8/10 (scanned Oct 8, 2026). The checks that decide who can get a change released:

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

  3. Published packages Linked, not attested

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: @houtini/seo-crawler-mcp 2.1.5. No published advisory affects it (OSV, checked 2026-10-10).

Changes to this chain

  • 2026-09-08 OSSF Scorecard: 2.8/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 Seo Crawler MCP’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 Seo Crawler MCP compares in MCP Servers

  1. #665 Apple Docs MCP 42.8 +0.2
  2. #666 Kolada MCP Server 42.6 ±0
  3. #667 Seo Crawler MCP 42.6 this agent
  4. #668 Devcontainer MCP 42.4 −0.2
  5. #669 Propresenter MCP 42.3 −0.3

Bars show each HVTrust score; the tick marks Seo Crawler MCP’s 42.6.

Where the 42.6 comes from

HVTrust dimensions vs the MCP Servers average

42.6 / 100 · 100.0% confidence

Seo Crawler MCP MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
4.1 / 25
6.3 below avg 10.4
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.7 below avg 13.5
Transparency50% declared license · 50% OSSF Scorecard
10.9 / 17
1.3 below avg 12.2
Maintenance60% last-push freshness · 40% commit activity
7.7 / 20
4.5 below avg 12.2
AdoptionLog-scaled stars · package downloads
5.1 / 20
2.3 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-09
Rank Moved
Rank dropped 13 spots (#1128 → #1141)
2026-10-05
Warning Issued
Warning: eligibility issues detected
2026-10-03
Warning Cleared
Warning cleared: eligibility issues resolved
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 2.8/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 64 days ago. Fresh activity helps separate stable projects from stale ones.
Review Flags
[5.1] repository is archived
Compare with another agent Get email alerts for Seo Crawler MCP View MCP Servers Report missing data
26.4
Activity sub-score · out of 100
#667
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-10-11 12:08 UTC · Repo last pushed 64 days ago

Rank Trend

2026-09-29 2026-10-11

Activity & Reach

Stars
16
Forks
3
Last Push
2026-08-08
64 days ago
Commits (4 wk)
0
Downloads (7d)
37
npm
HN mentions (30d)
—
Open Issues
0
Rank Change
▼3
was #1144

Analysis

Activity Inputs

26.4 / 100
StarsRepository reach
7.4 / 30
FreshnessLast push recency
16.1 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
2.8 / 20

Common questions about Seo Crawler MCP

Public trust evidence for Seo Crawler 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 Seo Crawler MCP publish package provenance?
No published build provenance is currently detected for Seo Crawler 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 Seo Crawler MCP have an OpenSSF Scorecard?
Seo Crawler MCP has an OpenSSF Scorecard score of 2.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 Seo Crawler MCP actively maintained?
Slowing down. Last push was 64 days ago — keep an eye on whether activity resumes.
What license does Seo Crawler MCP use?
Seo Crawler MCP ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Seo Crawler MCP's commits signed?
11% of the last 100 commits to Seo Crawler 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
medium confidence
Declared
MCP support appears present, but direct server implementation is less certain.
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 Seo Crawler 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 → declared
2026-09-02
Mcp Status Changed
Detected MCP server support changed: implemented → declared

Maintain Seo Crawler MCP?

For maintainers

HVTrust scores Seo Crawler 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 22Warning Issued 4Warning Cleared 3HVTrust 3Listed 2MCP 2Scorecard 1Delisted 1
2026-10-09
Rank Moved
Rank dropped 13 spots (#1128 → #1141)
2026-10-05
Warning Issued
Warning: eligibility issues detected
2026-10-03
Warning Cleared
Warning cleared: eligibility issues resolved
2026-09-30
Warning Issued
Warning: eligibility issues detected
2026-09-29
Warning Cleared
Warning cleared: eligibility issues resolved
2026-09-28
Warning Issued
Warning: eligibility issues detected
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → declared
2026-09-23
Rank Moved
Rank rose 114 spots (#1201 → #1087)
2026-09-23
HVTrust Changed
HVTrust up 24.6pts (19.1 → 43.7)
2026-09-22
Newly Listed
First tracked at rank #1201
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-12
Rank Moved
Rank dropped 12 spots (#1061 → #1073)
2026-09-11
Rank Moved
Rank dropped 10 spots (#1051 → #1061)
2026-09-09
Rank Moved
Rank dropped 15 spots (#1037 → #1052)
2026-09-08
Scorecard Added
OSSF Scorecard: 2.8/10
2026-09-08
Rank Moved
Rank rose 246 spots (#1283 → #1037)
2026-09-08
HVTrust Changed
HVTrust up 17.4pts (27.1 → 44.5)
2026-09-07
Rank Moved
Rank dropped 13 spots (#1270 → #1283)
2026-09-06
Rank Moved
Rank dropped 12 spots (#1258 → #1270)
2026-09-05
Rank Moved
Rank dropped 17 spots (#1241 → #1258)
2026-09-04
Rank Moved
Rank dropped 17 spots (#1224 → #1241)
2026-09-03
Rank Moved
Rank dropped 43 spots (#1181 → #1224)
2026-09-02
Mcp Status Changed
Detected MCP server support changed: implemented → declared
2026-09-02
Rank Moved
Rank rose 74 spots (#1255 → #1181)
2026-09-02
HVTrust Changed
HVTrust up 8.7pts (19.8 → 28.5)
2026-09-01
Rank Moved
Rank dropped 18 spots (#1237 → #1255)
2026-08-31
Rank Moved
Rank dropped 20 spots (#1217 → #1237)
2026-08-30
Rank Moved
Rank dropped 19 spots (#1198 → #1217)
2026-08-29
Rank Moved
Rank dropped 22 spots (#1176 → #1198)
2026-08-28
Rank Moved
Rank dropped 18 spots (#1158 → #1176)
2026-08-27
Rank Moved
Rank dropped 18 spots (#1140 → #1158)
2026-08-26
Rank Moved
Rank dropped 53 spots (#1087 → #1140)
2026-08-17
Rank Moved
Rank rose 12 spots (#1081 → #1069)
2026-08-16
Rank Moved
Rank dropped 29 spots (#1052 → #1081)
2026-08-10
Warning Issued
Warning: eligibility issues detected
2026-08-10
Rank Moved
Rank dropped 56 spots (#995 → #1051)
2026-08-09
Warning Cleared
Warning cleared: eligibility issues resolved
2026-08-08
Newly Listed
First tracked at rank #985
GitHub → npm: @houtini/seo-crawler-mcp

Embed Badge Badge guide for maintainers →

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

Other agents in MCP Servers

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