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.

io.github.mikusnuz/gsc

NPM · @MIKUSNUZ/GSC-MCP · SCANNED SEP 20

MCP server for Google Search Console & Indexing API — search analytics, sitemaps, URL inspection

Available components

0 this week 80 Trust /100
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 Security89
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects uuid 9.0.1, reached via google-auth-library > gaxios > uuid. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 40 of 118 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability85
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 945 tokens (~63/item across 15 items; 13 tools + 2 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
  • Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "sites_delete" 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 14 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
Install

How do I install the io.github.mikusnuz/gsc MCP server?

io.github.mikusnuz/gsc runs locally as an npm package, launched with npx -y @mikusnuz/gsc-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 · @mikusnuz/gsc-mcp

# add to Claude Code
claude mcp add mikusnuz-gsc -- npx -y @mikusnuz/gsc-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "mikusnuz-gsc": {
      "command": "npx",
      "args": [
        "-y",
        "@mikusnuz/gsc-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "mikusnuz-gsc": {
      "command": "npx",
      "args": [
        "-y",
        "@mikusnuz/gsc-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add mikusnuz-gsc -- npx -y @mikusnuz/gsc-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mikusnuz-gsc": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@mikusnuz/gsc-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add mikusnuz-gsc --command npx --arg -y --arg @mikusnuz/gsc-mcp
# ~/.hermes/config.yaml
mcp_servers:
  mikusnuz-gsc:
    command: "npx"
    args: ["-y", "@mikusnuz/gsc-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "mikusnuz-gsc": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@mikusnuz/gsc-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add mikusnuz-gsc -t stdio -c npx -a -y @mikusnuz/gsc-mcp
// mcp.json
{
  "mcpServers": {
    "mikusnuz-gsc": {
      "command": "npx",
      "args": [
        "-y",
        "@mikusnuz/gsc-mcp"
      ]
    }
  }
}
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 Sept 26 +1

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

  • 17 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 16 Sept 26 +1
    • Stability: 0.97 → pass security
  • 14 Sept 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.

  • 12 Sept 26 +1

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

  • 10 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 9 Sept 26 +1
    • Stability: 0.97 → pass security
  • 7 Sept 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.

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 20 Sept 2026 · Analysed npm/@mikusnuz/gsc-mcp@1.3.1

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 1 finding
ID CVE Severity Vector Fix available
GHSA-w5hq-g745-h8pq CVE-2026-41907 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 118 packages
Packages resolved 118
Deprecated 1
Stale 39
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 13 exposed · ~911 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
indexing_batch_publish ~64

Batch notify Google about multiple URL updates or removals via the Indexing API. Combines up to 100 notifications into a single HTTP request for efficiency.

NameTypeReqDescription
notificationsarrayyesArray of URL notifications (1-100 items). Each item has a url and type.

No output schema declared.

No examples provided.

indexing_get_metadata ~47

Get the latest indexing notification metadata for a URL. Returns the latest URL_UPDATED and URL_DELETED notification timestamps.

NameTypeReqDescription
urlstringyesThe fully-qualified URL to check notification status for

No output schema declared.

No examples provided.

indexing_publish ~72

Notify Google about a URL update or removal via the Indexing API. Use URL_UPDATED when a page is created or updated, URL_DELETED when a page is removed.

NameTypeReqDescription
typestringyesNotification type: URL_UPDATED or URL_DELETED
urlstringyesThe fully-qualified URL to notify about

No output schema declared.

No examples provided.

search_analytics_query ~247

Query search traffic data from Google Search Console. Returns clicks, impressions, CTR, and position data with flexible filtering and grouping.

NameTypeReqDescription
aggregationTypestringHow data is aggregated (default: auto)
dataStatestring'all' includes fresh (possibly incomplete) data, 'final' only finalized data, 'hourly_all' required when using 'hour' dimension
dimensionFilterGroupsarrayFilter groups to apply to the query
dimensionsarrayDimensions to group by: country, device, page, query, searchAppearance, date, hour (hour requires dataState='hourly_all')
endDatestringyesEnd date in YYYY-MM-DD format
rowLimitnumberMaximum number of rows to return (1-25000, default: 1000)
siteUrlstringyesThe site URL
startDatestringyesStart date in YYYY-MM-DD format
startRownumberZero-based row offset for pagination
typestringSearch type filter: web, image, video, news, discover, googleNews (default: web)

No output schema declared.

No examples provided.

sitemaps_delete ~44

Delete a sitemap from Google Search Console.

NameTypeReqDescription
feedpathstringyesThe URL of the sitemap to delete
siteUrlstringyesThe site URL

No output schema declared.

No examples provided.

sitemaps_get ~53

Retrieve information about a specific sitemap.

NameTypeReqDescription
feedpathstringyesThe URL of the sitemap (e.g. 'https://example.com/sitemap.xml')
siteUrlstringyesThe site URL

No output schema declared.

No examples provided.

sitemaps_list ~59

List all sitemaps submitted for a site in Google Search Console.

NameTypeReqDescription
siteUrlstringyesThe site URL
sitemapIndexstringOptional: URL of a sitemap index to list only sitemaps in that index

No output schema declared.

No examples provided.

sitemaps_submit ~59

Submit a sitemap for a site to Google Search Console.

NameTypeReqDescription
feedpathstringyesThe URL of the sitemap to submit (e.g. 'https://example.com/sitemap.xml')
siteUrlstringyesThe site URL

No output schema declared.

No examples provided.

sites_add ~55

Add a site (property) to Google Search Console. Verification may still be required.

NameTypeReqDescription
siteUrlstringyesThe site URL to add (e.g. 'https://example.com/' or 'sc-domain:example.com')

No output schema declared.

No examples provided.

sites_delete ~32

Remove a site (property) from Google Search Console.

NameTypeReqDescription
siteUrlstringyesThe site URL to remove

No output schema declared.

No examples provided.

sites_get ~50

Retrieve information about a specific site (property) in Google Search Console.

NameTypeReqDescription
siteUrlstringyesThe site URL (e.g. 'https://example.com/' or 'sc-domain:example.com')

No output schema declared.

No examples provided.

sites_list ~23

List all sites (properties) you have access to in Google Search Console.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

url_inspection_inspect ~106

Inspect a URL in Google's index. Returns indexing status, crawl info, rich results, AMP status, and mobile usability for a specific URL.

NameTypeReqDescription
inspectionUrlstringyesThe fully-qualified URL to inspect (must be under the site)
languageCodestringOptional BCP-47 language code for localized results (e.g. 'en-US', 'ko')
siteUrlstringyesThe site URL (property) the inspected URL belongs to

No output schema declared.

No examples provided.

Common questions

What is the io.github.mikusnuz/gsc MCP server?

io.github.mikusnuz/gsc is an MCP server listed in the public MCP registry as io.github.mikusnuz/gsc. MCP server for Google Search Console & Indexing API, search analytics, sitemaps, URL inspection. This page covers its npm package (@mikusnuz/gsc-mcp).

Is the io.github.mikusnuz/gsc MCP server safe to use?

io.github.mikusnuz/gsc scores 80 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 20 September 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 io.github.mikusnuz/gsc MCP server expose?

io.github.mikusnuz/gsc exposes 13 tools: sites_list, sites_get, sites_add, sites_delete, sitemaps_list, and 8 more. Their descriptions and schemas cost roughly 911 tokens of context every time the server is loaded.

Is the io.github.mikusnuz/gsc MCP server still maintained?

io.github.mikusnuz/gsc is still listed as active in the MCP registry. We last reached this channel on 20 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 io.github.mikusnuz/gsc MCP server under?

io.github.mikusnuz/gsc declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.