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 Console

NPM · SEO-CONSOLE-MCP

Search Console, Google Ads, App Store, Google Play, WordPress.org and Core Web Vitals over MCP

Available components

0 this week 79 Trust /100

Last scanned (13 hours ago)

Scores higher than 63% of npm servers

Category Marketing and SEO

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 1.29.0, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • Dependency health was assessed across the 174 of 175 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability83
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 6420 tokens (~145/item across 44 items; 43 tools + 1 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_sitemap" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 44 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 (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

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.

  • 19 Nov 26 +1
    • Stability: 0.97 → pass security
    • Security disclosure: unverified → fail ▼ functional
  • 18 Nov 26 −1
    • Security disclosure: fail → unverified ▼ functional
    • Stability: pass → 0.97 functional
  • 12 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Nov 26 +5
    • Source repository: unverified → pass ▲ security
  • 8 Nov 26 −4
    • Provenance: pass → unverified ▼ security
  • 7 Nov 26 −3
    • Stability: pass → 0.83 functional
  • 6 Nov 26 0
    • Security disclosure: unverified → fail ▼ functional
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 · Analysed npm/seo-console-mcp@0.18.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 28 findings
ID CVE Severity Vector Fix available
GHSA-rmxm-3fg6-px4f CVE-2026-118663 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N yes
GHSA-22jm-h49p-29qw CVE-2026-111767 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L yes
GHSA-46jr-4wx8-v453 CVE-2026-111768 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-6prh-2h8m-c8cw CVE-2026-111769 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N yes
GHSA-6qxp-vccf-f47h CVE-2026-104850 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N yes
GHSA-f897-62hf-6gxq high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-rvq5-wwqv-78pq CVE-2026-111771 medium CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N yes
GHSA-3g3m-2fjr-6pw4 CVE-2026-118773 medium yes
GHSA-g3hv-75wg-m249 CVE-2026-118764 medium yes
GHSA-2gqq-gqf2-x968 CVE-2026-84947 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-2jfj-6hjv-fm6j CVE-2026-84933 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N yes
GHSA-2m5v-pch6-74hx CVE-2026-109383 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N yes
GHSA-3wwx-pv8p-q78v CVE-2026-85024 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-3xpg-4rpp-hhhm CVE-2026-84890 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-4qv8-2p9j-2685 CVE-2026-109924 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-4w7w-5xrc-9h26 CVE-2026-109829 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N yes
GHSA-55wc-3pg8-jfw6 CVE-2026-87029 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-8436-99hf-9mmv CVE-2026-85008 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-9fm3-97px-rjf6 CVE-2026-109932 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-f72v-6w45-q472 CVE-2026-109841 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N yes
GHSA-pmjh-fq2x-6v4x CVE-2026-18149 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-qrxm-fqhp-jwvm CVE-2026-87018 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-r53p-7pc4-xj5r CVE-2026-18540 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-rfgv-xxqx-mfg5 CVE-2026-19534 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-rx4f-c7p8-82vq CVE-2026-85014 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-w293-vg96-wgc3 CVE-2026-84961 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N yes
GHSA-xjj6-f33q-929c CVE-2026-109869 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 174 packages
Packages resolved 174
Deprecated 3
Stale 47
Tree resolution Partial

The dependency tree was only partially resolved, so these counts may be incomplete.

Background: SBOMs and build attestations, explained →

MCP tools · 43 exposed · ~6,403 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
server_version ~94

Report which build of this server is answering, where it is running from, and whether it came out of an npx cache. Four values look like this one and are not: what npm calls latest, what the version range resolves to, what the plugin manifest declares, and what is actually running. Checking the command-line tool is not a substitute, since it is a separate process resolved separately. No credentials needed; read-only

Input schema present but exposes no named parameters.

NameTypeReqDescription
installPathstringyesWhere this build is running from. An npx cache path is what distinguishes the release you expected from whatever npx already had
namestringyes–
nodeVersionstringyes–
npxCachebooleanyesWhether this build is being served out of an npx cache, which reuses a build without re-resolving the version range and without erroring
versionstringyesThe version of the build answering this call, which is not necessarily what npm calls latest, what the version range resolves to, or what the plugin manifest declares

No examples provided.

snapshot ~292

Capture four surfaces in one timestamped document: Search Console totals and top rows per property, App Store listings, Google Play installs and traffic, and WordPress.org stats. Core Web Vitals field data, Android vitals, App Store sales and App Store reviews are not captured. A surface that cannot be read is recorded as an error in place rather than omitted; list_snapshots names the documents already on disk to compare an earlier one against; read-only

NameTypeReqDescription
appsarray–App Store apps, each a numeric app id or a bundle id
outPathstring–File name or path inside the snapshot directory (SEO_MCP_SNAPSHOT_DIR, default ~/.config/seo-mcp/snapshots); must end in .json, or pass auto to name the file after the moment it was taken. An existin…
overwriteboolean–Replace an existing file at outPath; without it an existing file is left alone and reported
packagesarray–Google Play package names
platformstring–App Store platform for the app surfaces
propertiesarray–Search Console properties to capture
slugsarray–WordPress.org plugin slugs
storefrontsarray–Storefront country codes for App Store ratings
windowDaysinteger–Search Console window in days, ending today
NameTypeReqDescription
appsarrayyes–
packagesarrayyes–
propertiesarrayyes–
slugsarrayyes–
surfacesWithErrorsarrayyes–
takenAtstringyes–
windowobjectyes–
windowDaysnumberyes–
writtenTostring––

No examples provided.

submit_sitemap ~69

Submit a sitemap to Google Search Console and return its current state

NameTypeReqDescription
dryRunboolean–If true, report what would be submitted without writing to Search Console
feedpathstringyesAbsolute URL of the sitemap to submit
siteUrlstringyesSearch Console property
NameTypeReqDescription
dryRunboolean––
feedpathstringyes–
siteUrlstringyes–
sitemap–yes–
stateRefreshError–yes–
successbooleanyes–

No examples provided.

wporg_plugin ~98

Look up a WordPress.org plugin's install base, downloads, ratings, and support stats by slug; public API, no credentials or API key needed

NameTypeReqDescription
downloadDaysinteger–Days of daily download history to fetch; 0 skips it
includeVersionDistributionboolean–Also fetch the share of active installs on each plugin version
slugstringyesWordPress.org plugin slug, e.g. akismet
NameTypeReqDescription
activeInstalls–yes–
activeInstallsIsBucketedbooleanyes–
added–yes–
dailyDownloads–yes–
downloadLink–yes–
downloadSummary–yes–
downloaded–yes–
lastUpdated–yes–
name–yes–
notesarrayyes–
numRatings–yes–
possiblyLaggingbooleanyes–
rating–yes–
ratings–yes–
requires–yes–
requiresPhp–yes–
slugstringyes–
supportThreads–yes–
supportThreadsResolved–yes–
tagsarrayyes–
tested–yes–
version–yes–
versionCount–yes–
versionDistribution–yes–

No examples provided.

Install

How do I install the SEO Console MCP server?

SEO Console runs locally as an npm package, launched with npx -y seo-console-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · seo-console-mcp

# add to Claude Code
claude mcp add ibrahimhajjaj-seo-console-mcp -- npx -y seo-console-mcp
Common questions

What is the SEO Console MCP server?

SEO Console is an MCP server listed in the public MCP registry as io.github.ibrahimhajjaj/seo-console-mcp. Search Console, Google Ads, App Store, Google Play, WordPress.org and Core Web Vitals over MCP. This page covers its npm package (seo-console-mcp).

Is the SEO Console MCP server safe to use?

SEO Console scores 79 out of 100 on VerifyMCP. We recorded 28 known advisories against it as of 21 November 2026. It declares no install or post-install scripts. 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 Console MCP server expose?

SEO Console exposes 43 tools: search_analytics, keyword_ideas, search_opportunities, compare_search_periods, ctr_gaps, and 38 more. Their descriptions and schemas cost roughly 6,403 tokens of context every time the server is loaded.

Is the SEO Console MCP server still maintained?

SEO Console 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 licence is the SEO Console MCP server under?

SEO Console declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the SEO Console MCP server?

VerifyMCP ran 16 checks on SEO Console, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.