Skip to main content
Glama

Google_search_console

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

Google Search Console MCP Pack

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
30.4% over 39 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-google_search_console
GitHub Stars
0
Server Listing
mcp-google_search_console

TDQS

A3.7/5.0

Scored across 35 tools

Disambiguation3/5

The ask_pipeworx family is a real problem: ask_pipeworx, ask_pipeworx_beta (which the description admits 'currently matches ask_pipeworx exactly'), and ask_pipeworx_grounded have heavily overlapping routing behavior, and deep_research overlaps too. The five polymarket_* tools and the entity_profile/recent_changes/compare_entities cluster are more distinguishable, but the redundant router variants keep this from being clean.

Naming Consistency3/5

All names are snake_case, which is good, but the conventions are mixed: verb_noun (resolve_entity, compare_entities, validate_claim), bare verbs (remember, recall, forget, subscribe), and noun phrases (entity_profile, bet_research). Multiple prefixes (gsc_, polymarket_, pipeworx_) coexist, so while readable it is not a predictable pattern.

Tool Count2/5

35 tools is very heavy, and the surface is a scattershot mix: 4 Google Search Console tools, ~15 Pipeworx meta-tools, 5 Polymarket betting tools, AI-visibility tools, npm/llms.txt utilities. For a server titled Google_search_console this is a severe scope mismatch.

Completeness2/5

If judged by the GSC domain, only four read-only tools exist (list_sites, search_analytics, inspect_url, list_sitemaps) with no sitemap submission, indexing request, or property management — notable gaps. The broader bundled surface is broad but incoherent, so no single stated purpose is well covered.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • Changedentity_profile3 fields changed
      • changedInput schema / properties / type / description
        Previous value: -"Entity type. Only \"company\" supported today; person/place coming soon."New value: +"\"company\" or \"ticker\" — both are accepted and behave identically; `value` can be a ticker, CIK, or company name either way. person/place coming soon."
      • changedInput schema / properties / type / enum
        Previous value: -[
-  "company"
-]New value: +[
+  "company",
+  "ticker"
+]
      • changedInput schema / properties / value / description
        Previous value: -"Ticker (e.g., \"AAPL\") or zero-padded CIK (e.g., \"0000320193\"). Names not supported — use resolve_entity first if you only have a name."New value: +"Ticker (e.g., \"AAPL\"), zero-padded CIK (e.g., \"0000320193\"), or company name (e.g., \"Moderna\") — names resolve via SEC EDGAR company-name match."
  2. 1 tool update
    • Changedresolve_entity1 field changed
      • changedInput schema / properties / value / description
        Previous value: -"For company: ticker (AAPL), CIK (0000320193), or name. For drug: brand or generic name (e.g., \"ozempic\", \"metformin\")."New value: +"For company: ticker (AAPL), CIK (0000320193), or name. For drug: brand or generic name (e.g., \"ozempic\", \"metformin\"). Pass the ENTITY NAME ONLY — for a bond that is the ISSUER exactly as printed (\"NEW YORK ST DORM AUTH\"), never the question's full noun phrase (\"NEW YORK ST DORM AUTH revenue bonds\"): the FIGI lookup matches instrument names, so trailing security-class words match nothing."

Related MCP Connectors

Related MCP Servers

  • gsc-mcp

    mikusnuz
    A
    license
    A
    quality
    B
    maintenance
    MCP server for Google Search Console, URL Inspection & Indexing API — search analytics, sitemap management, and batch indexing
    13
    83 npm
    7
    MIT

  • mcp-gsc-multi-account

    MattiooFR
    F
    license
    Not graded
    quality
    D
    maintenance
    Enables managing multiple Google Search Console accounts through a single MCP server, providing tools for search analytics, quick win detection, period comparison, URL inspection and indexing, and sitemap management.
    -

  • @lomi./gsc-mcp

    lomiafrica
    A
    license
    B
    quality
    B
    maintenance
    Enables Google Search Console data queries via MCP, including search analytics, performance comparisons, URL inspection, and sitemap management.
    12
    1
    MIT
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources