Is Open SEO MCP safe to use?

Open SEO MCP has an HVTrust score of 23.6/100 (Grade D), ranked #1329 of 1343 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 23.6/100 on HVTracker's evidence-weighted HVTrust scale. It has 2.9k 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 No result

Provenance None

Signed commits 0%

Last push 5d 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 23.6/100 (Grade D), ranked #1329 of 1343 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; recent commits are unsigned; last pushed 2026-09-24. 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 to 9.0no OSSF Scorecard result yet +40.6 → 64.2 C · #292 of 778
Sign every commit0% signed today +2.5 → 26.1 D · #777 of 778

Already done? Suggest a correction Add the trust badge

How Open SEO MCP compares in MCP Servers

#774 MCP Toolbox for Databases 27.5 +3.9
#775 Chat on Steroids 26.8 +3.2
#776 MCP Apple Notes 26.7 +3.1
#777 Open SEO MCP 23.6 this agent
#778 Prometheus MCP Server 22.2 −1.4

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

Where the 23.6 comes from

HVTrust dimensions vs the MCP Servers average

23.6 / 100 · 50.0% confidence

Open SEO MCP MCP Servers average (778 agents)

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

0 / 25

10.3 below avg 10.3

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

8.5 / 17

3.7 below avg 12.2

Maintenance60% last-push freshness · 40% commit activity

16.1 / 20

4.0 above avg 12.1

AdoptionLog-scaled stars · package downloads

8.3 / 20

1.0 above avg 7.3

Quick Trust Read

What Would Improve It

Add or improve OSSF Scorecard coverage so safety checks are easier to verify.

Recent Changes

2026-09-29

Newly Listed

First tracked at rank #1329

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.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Compare with another agent Get email alerts for Open SEO MCP View MCP Servers Report missing data

70.9

Activity sub-score · out of 100

#777

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 →

Activity & Reach

Stars

2.9k

Forks

358

Last Push

2026-09-24

5 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

NEW

Analysis

Activity Inputs

70.9 / 100

StarsRepository reach

20.8 / 30

FreshnessLast push recency

24.3 / 25

ActivityRecent commits

13.9 / 25

CommunityFork signal

11.9 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

—

Not available

Signed Commits

of last 100 commits verified

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?

No OpenSSF Scorecard data is currently published for Open SEO MCP. 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 Open SEO MCP actively maintained?

Actively maintained. The repository was pushed to within the last 5 day(s).

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-09-29

Newly Listed

First tracked at rank #1329

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