Google Search Console MCP (AminForou)

70/100

Capped at 70: core tools not tested (only setup or self-check calls passed); the tests add up to 100. Why scores are capped

Last tested 2026-11-13 UTC (Fresh: tested within 30 days) Connects · tools listedNo tool call tested yet Connects without a key; tool calls need one

Advisories: not yet checked

Security review: not tested

Test points add up to 100; the score is capped at 70 until a tool call passes. Not a quality or security rating. Methodology

Test points before the cap (100/100)

  • Install20/20
  • Handshake30/30
  • Maintenance25/25
  • Docs15/15
  • License10/10

Tested pypi mcp-search-console 0.4.2 (MIT; repo AminForou/mcp-gsc). Installed pinned with scripts off (uv venv, Python 3.13) and launched: initialize and tools/list over stdio succeeded with no credentials and listed 21 tools (no tool annotations). Real calls: 0 of 2 real function calls passed (1 setup/self-check call(s) not counted). Calls need Google Search Console OAuth or service-account credentials. Core tools not tested: 70 cap.
Tool-call test (2026-11-13 UTC, direct MCP stdio client, no LLM): fail. 0 of 2 real function calls passed (1 setup/self-check call(s) not counted). Calls need Google Search Console OAuth or service-account credentials. Evidence: local test run, Nov 13, 2026 UTC.

Transport (tested 2026-11-13 UTC): stdio

Token cost (estimate): approx. 3778 tokens, cl100k estimate (21 tools, measured 2026-11-13 UTC, version 0.4.2). This is an estimate from our testing of the tool names, descriptions and input schemas, counted with cl100k_base.

Permissions: 13 read, 5 write (state-changing), 3 unclassified · Auth: API key · Rate limit: unknown · Pricing unit: unknown

Auth: API key. Rate limit: unknown. Pricing unit: unknown.

  • add_site — write (state-changing)
  • batch_url_inspection — unclassified
  • check_indexing_issues — unclassified
  • compare_search_periods — read
  • delete_site — write (state-changing)
  • delete_sitemap — write (state-changing)
  • get_advanced_search_analytics — read
  • get_capabilities — read
  • get_creator_info — read
  • get_performance_overview — read
  • get_search_analytics — read
  • get_search_by_page_query — read
  • get_site_details — read
  • get_sitemap_details — read
  • get_sitemaps — read
  • inspect_url_enhanced — read
  • list_properties — read
  • list_sitemaps_enhanced — read
  • manage_sitemaps — write (state-changing)
  • reauthenticate — write (state-changing)
  • submit_sitemap — unclassified

listing-flags calls_need_key or auth_kind

Score 70/100 · Tools 21 · Token cost approx. 3,778 tokens · Compare · Last tested 2026-11-13 UTC · Version tested 0.4.2 · Package mcp-search-console · Repo AminForou/mcp-gsc

Summary: Google Search Console MCP (AminForou) completed an MCP handshake without credentials and exposed 21 tools.

Evidence summary

Handshake
pass
Tools listed
21
Context cost
approx. 3778 tokens, cl100k estimate (21 tools, measured 2026-11-13 UTC, version 0.4.2; an estimate) ranking · add up your servers' context cost
API key
Connects without a key; tool calls need one
Tested
2026-11-13 UTC

Test results

TestResultPointsEvidence
installpass20uv pip install mcp-search-console (Python venv, Linux) succeeded in 1s.
handshakepass30MCP initialize + tools/list over stdio succeeded with no credentials; 21 tools listed in 28.4s.
maintenancepass25Repo pushed 7 days before test; 2,190 GitHub stars.
docspass15README over 3,000 chars; install instructions present; mcpServers config example present. Check of the package's own README (PyPI long_description (package README)).
licensepass10MIT (OSI-approved).

Local-model readiness

Token cost (estimate): approx. 3778 tokens, cl100k estimate for 21 tools · about 46% of an 8k context. This is an estimate from our testing (counted with cl100k_base).

Small-model friendly (schema heuristic, not a model result): unknown.

Not tested

Small-model task runs: Not yet tested.

What we tested and what we didn't

Tested on 2026-11-13 UTC

  • Install from the registry
  • We connected with no credentials and asked for its tool list: it listed 21 tools (Method details: MCP initialize then tools/list)
  • Maintenance signals (last push, archived/deprecated status)
  • Docs (README length, install and config example)
  • License (OSI-approved or not)
  • Token cost (estimate)

Not tested

  • Security: not audited (no code review, no permission or data-flow analysis)
  • Real tasks (no functional task runs yet)
  • Behaviour with real credentials or a real account
  • Performance, rate limits or load
  • Correctness of results beyond the listed tasks

Methodology: how we test. A high score means it installs and responds, not that giving it access to your data carries no risk.

Known security issues

Not yet checked.

Monthly roundup: MCP security issues, October 2026.

Tool list changes

Baseline recorded from the 2026-11-13 UTC test run; changes appear after the next test.

Snapshot hash (fingerprint of the tool list)

eb904aaf29bb: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed.

Feeds: RSS · JSON.

Raw test record (JSON)
{
  "name": "mcp-search-console",
  "version": "0.4.2",
  "registry": "pypi",
  "status": "working",
  "tested": "2026-11-13",
  "tools_count": 21,
  "deprecated": false,
  "archived": false,
  "tests": {
    "install": [
      "pass",
      20,
      "`uv pip install mcp-search-console` (Python venv, Linux) succeeded in 1s."
    ],
    "handshake": [
      "pass",
      30,
      "MCP `initialize` + `tools/list` over stdio succeeded with no credentials; 21 tools listed in 28.4s."
    ],
    "maintenance": [
      "pass",
      25,
      "Repo pushed 7 days before test; 2,190 GitHub stars."
    ],
    "docs": [
      "pass",
      15,
      "README over 3,000 chars; install instructions present; `mcpServers` config example present. Check of the package's own README (PyPI long_description (package README))."
    ],
    "license": [
      "pass",
      10,
      "MIT (OSI-approved)."
    ]
  }
}

Install

uvx mcp-search-console

Pin the version we tested

uvx mcp-search-console==0.4.2

pip install mcp-search-console==0.4.2

tested 2026-11-13 UTC. Newer versions may differ and were not tested by us.

{
  "mcpServers": {
    "google-search-console-mcp-aminforou": {
      "command": "uvx",
      "args": [
        "mcp-search-console==0.4.2"
      ]
    }
  }
}

Tools listed

get_capabilities, list_properties, add_site, delete_site, get_search_analytics, get_site_details, get_sitemaps, inspect_url_enhanced, batch_url_inspection, check_indexing_issues, get_performance_overview, get_advanced_search_analytics, compare_search_periods, get_search_by_page_query, list_sitemaps_enhanced, get_sitemap_details, submit_sitemap, delete_sitemap, manage_sitemaps, get_creator_info, reauthenticate

Quick config

{
  "mcpServers": {
    "google-search-console-mcp-aminforou": {
      "command": "uvx",
      "args": [
        "mcp-search-console"
      ]
    }
  }
}

Add to config Opens the config generator with this server selected.

Setup

  1. Install. Run uv pip install mcp-search-console (Python venv). This is the exact command we ran on 2026-11-13 UTC.
  2. Configure. Add the mcpServers entry below to your MCP client config.
  3. Verify. Restart the client and check that tools/list returns tools (21 in our test).
{
  "mcpServers": {
    "google-search-console-mcp-aminforou": {
      "command": "uvx",
      "args": [
        "mcp-search-console"
      ]
    }
  }
}

Test history

Follow this server (RSS) · Monthly changelog

Related: Best data and analytics MCP servers

FAQ

Is Google Search Console MCP (AminForou) deprecated?

No. mcp-search-console was not deprecated or archived when we last tested it on 2026-11-13 UTC.

What replaces Google Search Console MCP (AminForou)?

Nothing; Google Search Console MCP (AminForou) is not deprecated as of 2026-11-13 UTC.

Does Google Search Console MCP (AminForou) need an API key?

It connects and lists 21 tools without a key, but its tool calls need one.

Embed the badge

TestedMCP: 70/100, tested 2026-11-13 UTC

Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.

Claim this listing · Report an issue