Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

SEO Data MCP (SteadyScrape)

REMOTE · MCP.STEADYSCRAPE.DEV

Keyword volume, live SERP ranks, domain traffic, ranked keywords, backlinks, Google Trends, YouTube.

65 Trust /100

Last scanned (19 hours ago)

Scores higher than 46% of remote servers

Reachable. Last reached 21 Nov 2026.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability64
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1296 tokens (~144/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
  • Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 92% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 20 Nov 26 64

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://mcp.steadyscrape.dev/seo/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=steadyscrape.dev CN=WE1,O=Google Trust Services,C=US 19 Nov 2026 17 Feb 2027 ECDSA 256 ECDSA-SHA256 388fb515dbb97ed40e2fd1e1532975d6
SANs: steadyscrape.dev, mcp.steadyscrape.dev, *.mcp.steadyscrape.dev
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.steadyscrape.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
steadyscrape.dev. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.steadyscrape.dev/seo/mcp Verified 200
http (plaintext) http://mcp.steadyscrape.dev/seo/mcp Inconclusive 405
MCP tools · 9 exposed · ~1,223 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
backlinks ~120

Backlinks or referring domains pointing to a domain or page URL, strongest first: linking page/domain, anchor, dofollow, first/last seen and rank. Up to 100 rows per call, plus the target's totals. Billed per call with data.

NameTypeReqDescription
dofollow_onlyboolean–Backlinks mode only: return only dofollow links (default false).
limitinteger–Rows to return (default 20).
modestring–Default backlinks.
targetstringyesDomain (example.com) or page URL.

No output schema declared.

No examples provided.

domain_overview ~123

For up to 100 domains: estimated monthly organic traffic and number of ranking keywords in one country (Google), paid keywords, plus backlink profile: domain rank (0-1000), backlinks, referring domains, spam score, first seen. Billed per started block of 10 domains that have data.

NameTypeReqDescription
countrystring–2-letter country code (US, GB, DE...) or English name. Default US.
domainsarrayyes–
languagestring–Language code, e.g. en, es, de. Default en.

No output schema declared.

No examples provided.

google_serp ~193

Live Google organic results for one keyword: position, title, URL, domain and snippet, plus which SERP features appear (AI Overview, People Also Ask, local pack, video...) and the AI Overview text. Optionally give target_domain to get that domain's best position (rank check). Billed per 10 results of depth.

NameTypeReqDescription
countrystring–2-letter country code (US, GB, DE...) or English name. Default US.
depthinteger–Results to fetch: 10-100 (default 10). Deeper is slower (100 takes ~15 s).
devicestring–Default desktop.
keywordstringyesThe search query.
languagestring–Language code, e.g. en, es, de. Default en.
target_domainstring–Optional domain to find in the results, e.g. example.com.

No output schema declared.

No examples provided.

google_trends ~114

Google Trends interest over time (0-100) for up to 5 keywords compared, in a country or worldwide, for web, YouTube, news, images or shopping search, plus each keyword's average. Billed per call with data.

NameTypeReqDescription
countrystring–2-letter country code or 'worldwide'. Default US.
keywordsarrayyes–
search_typestring–Default web (froogle = shopping).
time_rangestring–Default past_12_months.

No output schema declared.

No examples provided.

keyword_metrics ~126

Google search volume, CPC, competition, keyword difficulty (0-100), search intent and the last 12 months of volume for up to 100 keywords in one country. Keywords without data are listed in noData and not charged. Billed per started block of 10 keywords that have data.

NameTypeReqDescription
countrystring–2-letter country code (US, GB, DE...) or English name. Default US.
keywordsarrayyes1-100 keywords.
languagestring–Language code, e.g. en, es, de. Default en.

No output schema declared.

No examples provided.

rank_check ~177

Where one domain ranks on live Google for up to 10 keywords in one country: best position, ranking URL and the top 3 domains for each keyword, plus SERP features. Same data and price as google_serp, billed per 10 results of depth for each keyword that returns results.

NameTypeReqDescription
countrystring–2-letter country code (US, GB, DE...) or English name. Default US.
depthinteger–Results checked per keyword: 10-100 (default 10).
devicestring–Default desktop.
keywordsarrayyes1-10 search queries.
languagestring–Language code, e.g. en, es, de. Default en.
target_domainstringyesDomain to find, e.g. example.com (subdomains count).

No output schema declared.

No examples provided.

ranked_keywords ~138

The Google keywords a domain (or URL) ranks for in one country, sorted by estimated traffic: keyword, position, ranking URL, search volume, CPC and estimated visits. Up to 100 keywords per call, plus position distribution totals. Billed per call with data.

NameTypeReqDescription
countrystring–2-letter country code (US, GB, DE...) or English name. Default US.
domainstringyesDomain (example.com) or page URL.
languagestring–Language code, e.g. en, es, de. Default en.
limitinteger–Keywords to return (default 20).

No output schema declared.

No examples provided.

youtube_search ~118

YouTube search results for a query in ranked order: video ID, title, channel, views, publish date, duration and whether it is a Short. Up to 40 results. Billed per 20 results of depth.

NameTypeReqDescription
countrystring–2-letter country code (US, GB, DE...) or English name. Default US.
languagestring–Language code, e.g. en, es, de. Default en.
max_resultsinteger–Default 20.
querystringyes–

No output schema declared.

No examples provided.

youtube_video ~114

Public stats for one YouTube video (views, likes, comment count, channel subscribers, tags, category, description, duration, publish date) and optionally its transcript. Billed per video; the transcript is billed separately and only if the video has captions.

NameTypeReqDescription
include_transcriptboolean–Also return the captions text (default false).
languagestring–Language code, e.g. en, es, de. Default en.
videostringyesYouTube URL or 11-character video ID.

No output schema declared.

No examples provided.

Install

How do I install the SEO Data MCP (SteadyScrape) server?

SEO Data MCP (SteadyScrape) is a hosted endpoint at https://mcp.steadyscrape.dev/seo/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.steadyscrape.dev

# add to Claude Code
claude mcp add --transport http steadyscrape-seo-data-mcp 'https://mcp.steadyscrape.dev/seo/mcp'
Common questions

What is the SEO Data MCP (SteadyScrape) server?

SEO Data MCP (SteadyScrape) is listed in the public MCP registry as io.github.steadyscrape/seo-data-mcp. Keyword volume, live SERP ranks, domain traffic, ranked keywords, backlinks, Google Trends, YouTube. This page covers its hosted endpoint (https://mcp.steadyscrape.dev/seo/mcp).

Is the SEO Data MCP (SteadyScrape) server safe to use?

SEO Data MCP (SteadyScrape) scores 65 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the SEO Data MCP (SteadyScrape) server expose?

SEO Data MCP (SteadyScrape) exposes 9 tools: keyword_metrics, google_serp, rank_check, domain_overview, ranked_keywords, and 4 more. Their descriptions and schemas cost roughly 1,223 tokens of context every time the server is loaded.

Does the SEO Data MCP (SteadyScrape) server require authentication?

No. We connected to SEO Data MCP (SteadyScrape) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the SEO Data MCP (SteadyScrape) server still maintained?

SEO Data MCP (SteadyScrape) is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the SEO Data MCP (SteadyScrape) server?

VerifyMCP ran 12 checks on SEO Data MCP (SteadyScrape), covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about SEO Data MCP (SteadyScrape): HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.