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.

MCP Search Console

PYPI · MCP-SEARCH-CONSOLE-MULTI · SCANNED SEP 20

Multi-account Google Search Console MCP: analytics, URL inspection, sitemaps across named accounts.

+1 this week 79 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 Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
  • 2 of 39 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 972 tokens (~57/item across 17 items; 17 tools + 0 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 Coverage74
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 11% of tool parameters carry a description.Partial
  • 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 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the MCP Search Console server?

MCP Search Console runs locally as a PyPI package, launched with uvx mcp-search-console-multi. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · mcp-search-console-multi

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

  • 20 Sept 26 +1

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

  • 18 Sept 26 −2
    • Stability: pass → 0.83 functional
  • 17 Sept 26 0
    • Stability: 0.97 → pass security
  • 16 Sept 26 +1

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

  • 15 Sept 26 +15
    • Malware scan: unverified → pass security
  • 14 Sept 26 −14
    • Malware scan: pass → unverified security
  • 12 Sept 26 +1

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

  • 11 Sept 26 −3
    • Stability: pass → 0.80 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 20 Sept 2026 · Analysed pypi/mcp-search-console-multi@0.1.3

Provenance No attestation

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

Result No attestation
Ecosystem pypi

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 39 packages
Packages resolved 39
Stale 2
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 17 exposed · ~972 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
batch_inspect_urls ~55

Inspect multiple URLs at once. Returns one result per URL. Maximum 10 URLs per call (GSC API limit).

NameTypeReqDescription
account
page_urlsarrayyes
site_urlstringyes
NameTypeReqDescription
resultarrayyes

No examples provided.

check_indexing_issues ~58

Check a list of URLs for indexing problems. Returns a prioritised summary of issues — more actionable than raw inspect_url output.

NameTypeReqDescription
account
page_urlsarrayyes
site_urlstringyes
NameTypeReqDescription
resultarrayyes

No examples provided.

compare_periods ~91

Compare search performance between two date ranges. Returns rows for both periods side-by-side with delta calculations.

NameTypeReqDescription
account
dimensions
period1_endstringyes
period1_startstringyes
period2_endstringyes
period2_startstringyes
row_limitinteger
site_urlstringyes

Structured output declared, but exposes no named fields.

No examples provided.

delete_sitemap ~47

Delete a sitemap from Google Search Console. Requires GSC_ALLOW_DESTRUCTIVE=true.

NameTypeReqDescription
account
site_urlstringyes
sitemap_urlstringyes

Structured output declared, but exposes no named fields.

No examples provided.

get_advanced_search_analytics ~106

Advanced search analytics with dimension filters. filters format: [{"dimension": "country", "operator": "equals", "expression": "usa"}] operators: equals, notEquals, contains, notContains, includingRegex, excludingRegex

NameTypeReqDescription
account
dimensions
end_datestringyes
filters
row_limitinteger
site_urlstringyes
start_datestringyes

Structured output declared, but exposes no named fields.

No examples provided.

get_performance_overview ~69

Get a high-level performance summary: total clicks, impressions, CTR, average position. No dimension breakdown — use get_search_analytics for that.

NameTypeReqDescription
account
end_datestringyes
site_urlstringyes
start_datestringyes

Structured output declared, but exposes no named fields.

No examples provided.

get_search_analytics ~144

Fetch search analytics data (clicks, impressions, CTR, position).

NameTypeReqDescription
accountAccount name from config (uses default if omitted)
dimensionsList of dimensions — any of ['query', 'page', 'country', 'device', 'date']
end_datestringyesEnd date in YYYY-MM-DD format
row_limitintegerNumber of rows to return (default 25, max 1000)
site_urlstringyesGSC property URL (e.g. 'https://example.com' or 'sc-domain:example.com')
start_datestringyesStart date in YYYY-MM-DD format

Structured output declared, but exposes no named fields.

No examples provided.

get_search_by_page ~66

Get search queries driving traffic to a specific page URL.

NameTypeReqDescription
account
end_datestringyes
page_urlstringyes
row_limitinteger
site_urlstringyes
start_datestringyes

Structured output declared, but exposes no named fields.

No examples provided.

get_site_details ~34

Get verification and permission details for a specific GSC property.

NameTypeReqDescription
account
site_urlstringyes

Structured output declared, but exposes no named fields.

No examples provided.

get_sitemap ~39

Get details and status of a specific sitemap.

NameTypeReqDescription
account
site_urlstringyes
sitemap_urlstringyes

Structured output declared, but exposes no named fields.

No examples provided.

inspect_url ~48

Inspect a URL's indexing status, last crawl date, mobile usability, and rich result eligibility.

NameTypeReqDescription
account
page_urlstringyes
site_urlstringyes

Structured output declared, but exposes no named fields.

No examples provided.

list_accounts ~21

List all configured GSC accounts and which is the current default.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes

No examples provided.

list_properties ~24

List all Google Search Console properties for the specified account.

NameTypeReqDescription
account
NameTypeReqDescription
resultarrayyes

No examples provided.

list_sitemaps ~36

List all sitemaps submitted to GSC for this property.

NameTypeReqDescription
account
site_urlstringyes
NameTypeReqDescription
resultarrayyes

No examples provided.

reauthenticate ~57

Force re-authentication for an account. Clears the cached token and re-runs the OAuth flow (or reloads service account credentials). Useful when a token has been revoked or you need to switch Google accounts.

NameTypeReqDescription
account

Structured output declared, but exposes no named fields.

No examples provided.

set_default_account ~30

Set the default account used when no account is specified in other tools.

NameTypeReqDescription
accountstringyes

Structured output declared, but exposes no named fields.

No examples provided.

submit_sitemap ~47

Submit a sitemap to Google Search Console. Requires GSC_ALLOW_DESTRUCTIVE=true.

NameTypeReqDescription
account
site_urlstringyes
sitemap_urlstringyes

Structured output declared, but exposes no named fields.

No examples provided.

Common questions

What is the MCP Search Console server?

MCP Search Console is listed in the public MCP registry as io.github.Ayo-Fam/mcp-search-console. Multi-account Google Search Console MCP: analytics, URL inspection, sitemaps across named accounts. This page covers its PyPI package (mcp-search-console-multi).

Is the MCP Search Console server safe to use?

MCP Search Console scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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 MCP Search Console server expose?

MCP Search Console exposes 17 tools: list_accounts, set_default_account, reauthenticate, list_properties, get_site_details, and 12 more. Their descriptions and schemas cost roughly 972 tokens of context every time the server is loaded.

Is the MCP Search Console server still maintained?

MCP Search Console 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 MCP Search Console server under?

MCP Search 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.