Is Open SEO MCP safe to use?

Open SEO MCP has an HVTrust score of 48.9/100 (Grade D), ranked #1043 of 1387 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Open SEO MCP?

Open SEO MCP scores 48.9/100 on HVTracker's evidence-weighted HVTrust scale. It has 9.8k GitHub stars and is categorized under MCP Servers.

Open SEO MCP

Repository

Website

Free SEO MCP server + open-source SEO and GEO skills for Claude: keyword research, rank tracking, audits, backlinks, AI visibility on your real GSC/GA4/ads data. claude mcp add ryze --transport http https://connector.get-ryze.ai/mcp

MCP Servers Shell Listed MIT

Is Open SEO MCP safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 2.7 / 10

Provenance None

Signed commits 0%

Last push 19d ago

Compare Open SEO MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Open SEO MCP scores 48.9/100 (Grade D), ranked #1043 of 1387 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 2.7/10; recent commits are unsigned; last pushed 2026-10-27. Every point is earned from checkable signals — never paid placement. How scoring works →

How Open SEO 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.

Raise the OSSF Scorecard from 2.7 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Code-Review 0 +13.1 → 62.0 C · #357 of 779
Sign every commit0% signed today +5.0 → 53.9 C · #483 of 779

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Open SEO MCP 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.

Source Unsigned

github.com/Ryze-AI-Adgent/open-seo-mcp-skills, MIT, last pushed 2026-10-27. None of the last 100 commits carry a verified signature, so no change traces to a verified identity.
Review and release Weak

OpenSSF Scorecard rates the repository's practices 2.7/10 (scanned Nov 14, 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 Dependenciesn/a
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 0

CI-Tests -1

CII-Best-Practices 0

Code-Review 0

Contributors 3

Dangerous-Workflow -1

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging -1

Pinned-Dependencies -1

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions -1

Vulnerabilities 10
Published packages None

No registry package. Open SEO MCP 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-09-30 OSSF Scorecard: 2.7/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 Open SEO 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 Open SEO MCP compares in MCP Servers

Bars show each HVTrust score; the tick marks Open SEO MCP’s 48.9.

Where the 48.9 comes from

HVTrust dimensions vs the MCP Servers average

48.9 / 100 · 100.0% confidence

Open SEO MCP MCP Servers average (779 agents)

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

3.4 / 25

7.5 below avg 10.9

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.9 below avg 13.7

Transparency50% declared license · 50% OSSF Scorecard

10.8 / 17

1.5 below avg 12.3

Maintenance60% last-push freshness · 40% commit activity

12.6 / 20

in line with avg 12.2

AdoptionLog-scaled stars · package downloads

9.6 / 20

2.0 above avg 7.6

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-11-12

Rank Moved

Rank dropped 19 spots (#1021 → #1040)

2026-11-06

Grade Changed

Trust grade C → D

2026-11-05

Grade Changed

Trust grade D → C

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 2.7/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.

Compare with another agent View MCP Servers Report missing data

64.5

Activity sub-score · out of 100

#586

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 →

Rank Trend

2026-09-29 2026-11-15

Activity & Reach

Stars

9.8k

Forks

399

Last Push

2026-10-27

19 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼3

was #1040

Analysis

Activity Inputs

64.5 / 100

StarsRepository reach

23.9 / 30

FreshnessLast push recency

22.4 / 25

ActivityRecent commits

6.0 / 25

CommunityFork signal

12.1 / 20

Common questions about Open SEO MCP

Public trust evidence for Open SEO 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 Open SEO MCP publish package provenance?

No published build provenance is currently detected for Open SEO 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 Open SEO MCP have an OpenSSF Scorecard?

Open SEO MCP has an OpenSSF Scorecard score of 2.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 Open SEO MCP actively maintained?

Maintained. Last push was 19 days ago.

What license does Open SEO MCP use?

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

Are Open SEO MCP's commits signed?

0% of the last 100 commits to Open SEO 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

Implemented

Open SEO MCP appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

medium confidence

1 detected

Public provider/service dependencies detected.

Anthropic

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

Tool / Plugin Surface

high 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 Open SEO MCP?

For maintainers

HVTrust scores Open SEO 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

2026-11-12

Rank Moved

Rank dropped 19 spots (#1021 → #1040)

2026-11-06

Grade Changed

Trust grade C → D

2026-11-05

Grade Changed

Trust grade D → C

2026-11-05

Rank Moved

Rank rose 34 spots (#1048 → #1014)

2026-10-21

Rank Moved

Rank rose 22 spots (#1056 → #1034)

2026-10-15

Rank Moved

Rank dropped 11 spots (#1038 → #1049)

2026-10-13

Rank Moved

Rank rose 19 spots (#1051 → #1032)

2026-10-09

Rank Moved

Rank dropped 49 spots (#988 → #1037)

2026-10-02

Rank Moved

Rank rose 33 spots (#1004 → #971)

2026-09-30

Scorecard Added

OSSF Scorecard: 2.7/10

2026-09-30

Rank Moved

Rank rose 328 spots (#1330 → #1002)

2026-09-30

HVTrust Changed

HVTrust up 24.4pts (23.6 → 48.0)

2026-09-30

Activity Score Changed

Activity score down 5pts (71 → 66)

2026-09-29

Newly Listed

First tracked at rank #1330

GitHub → Website →

Embed Badge Badge guide for maintainers →

For maintainers

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

Open SEO MCP

How Open SEO MCP could raise its score

Chain of custody

Source Unsigned

Review and release Weak

Published packages None

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How Open SEO MCP compares in MCP Servers

Where the 48.9 comes from

HVTrust dimensions vs the MCP Servers average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about Open SEO MCP

AI agent surface

Maintain Open SEO MCP?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in MCP Servers