SEO Console
NPM · SEO-CONSOLE-MCP · SCANNED SEP 25
Search Console, Google Ads, App Store, Google Play, WordPress.org and Core Web Vitals over MCP
Available components
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 Security98
- No malware found by supply-chain analysis.Pass
- Known CVEs were checked across the 177 of 178 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Dependency health was assessed across the 177 of 178 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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
claude mcp add ibrahimhajjaj-seo-console-mcp -- npx -y seo-console-mcp
{
"mcpServers": {
"ibrahimhajjaj-seo-console-mcp": {
"command": "npx",
"args": [
"-y",
"seo-console-mcp"
]
}
}
} {
"servers": {
"ibrahimhajjaj-seo-console-mcp": {
"command": "npx",
"args": [
"-y",
"seo-console-mcp"
]
}
}
} codex mcp add ibrahimhajjaj-seo-console-mcp -- npx -y seo-console-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ibrahimhajjaj-seo-console-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"seo-console-mcp"
],
"enabled": true
}
}
} openclaw mcp add ibrahimhajjaj-seo-console-mcp --command npx --arg -y --arg seo-console-mcp
mcp_servers:
ibrahimhajjaj-seo-console-mcp:
command: "npx"
args: ["-y", "seo-console-mcp"] {
"McpServers": {
"ibrahimhajjaj-seo-console-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"seo-console-mcp"
]
}
}
} assistant mcp add ibrahimhajjaj-seo-console-mcp -t stdio -c npx -a -y seo-console-mcp
{
"mcpServers": {
"ibrahimhajjaj-seo-console-mcp": {
"command": "npx",
"args": [
"-y",
"seo-console-mcp"
]
}
}
} 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.
- 25 Sept 26 70
First indexed and scored.
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 25 Sept 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 →
Dependencies 177 packages
| Packages resolved | 177 |
|---|---|
| Deprecated | 3 |
| Stale | 46 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
Background: SBOMs and build attestations, explained →
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 →
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.
| Name | Type | Req | Description |
|---|---|---|---|
| installPath | string | yes | Where this build is running from. An npx cache path is what distinguishes the release you expected from whatever npx already had |
| name | string | yes | – |
| nodeVersion | string | yes | – |
| npxCache | boolean | yes | Whether this build is being served out of an npx cache, which reuses a build without re-resolving the version range and without erroring |
| version | string | yes | The 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
| Name | Type | Req | Description |
|---|---|---|---|
| apps | array | – | App Store apps, each a numeric app id or a bundle id |
| outPath | string | – | 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… |
| overwrite | boolean | – | Replace an existing file at outPath; without it an existing file is left alone and reported |
| packages | array | – | Google Play package names |
| platform | string | – | App Store platform for the app surfaces |
| properties | array | – | Search Console properties to capture |
| slugs | array | – | WordPress.org plugin slugs |
| storefronts | array | – | Storefront country codes for App Store ratings |
| windowDays | integer | – | Search Console window in days, ending today |
| Name | Type | Req | Description |
|---|---|---|---|
| apps | array | yes | – |
| packages | array | yes | – |
| properties | array | yes | – |
| slugs | array | yes | – |
| surfacesWithErrors | array | yes | – |
| takenAt | string | yes | – |
| window | object | yes | – |
| windowDays | number | yes | – |
| writtenTo | string | – | – |
No examples provided.
submit_sitemap ~69
Submit a sitemap to Google Search Console and return its current state
| Name | Type | Req | Description |
|---|---|---|---|
| dryRun | boolean | – | If true, report what would be submitted without writing to Search Console |
| feedpath | string | yes | Absolute URL of the sitemap to submit |
| siteUrl | string | yes | Search Console property |
| Name | Type | Req | Description |
|---|---|---|---|
| dryRun | boolean | – | – |
| feedpath | string | yes | – |
| siteUrl | string | yes | – |
| sitemap | – | yes | – |
| stateRefreshError | – | yes | – |
| success | boolean | yes | – |
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
| Name | Type | Req | Description |
|---|---|---|---|
| downloadDays | integer | – | Days of daily download history to fetch; 0 skips it |
| includeVersionDistribution | boolean | – | Also fetch the share of active installs on each plugin version |
| slug | string | yes | WordPress.org plugin slug, e.g. akismet |
| Name | Type | Req | Description |
|---|---|---|---|
| activeInstalls | – | yes | – |
| activeInstallsIsBucketed | boolean | yes | – |
| added | – | yes | – |
| dailyDownloads | – | yes | – |
| downloadLink | – | yes | – |
| downloadSummary | – | yes | – |
| downloaded | – | yes | – |
| lastUpdated | – | yes | – |
| name | – | yes | – |
| notes | array | yes | – |
| numRatings | – | yes | – |
| possiblyLagging | boolean | yes | – |
| rating | – | yes | – |
| ratings | – | yes | – |
| requires | – | yes | – |
| requiresPhp | – | yes | – |
| slug | string | yes | – |
| supportThreads | – | yes | – |
| supportThreadsResolved | – | yes | – |
| tags | array | yes | – |
| tested | – | yes | – |
| version | – | yes | – |
| versionCount | – | yes | – |
| versionDistribution | – | yes | – |
No examples provided.
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 70 out of 100 on VerifyMCP. 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 25 September 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.