# AskWatch Google Search Console MCP (remote · mcp.askwatch.ai)

Ask Google Search Console in plain language. Hosted, free, no Google Cloud project.

- Trust score: 75/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- remote · `mcp.askwatch.ai`: 75/100 (this document), [markdown](https://verifymcp.io/servers/ai-askwatch-gsc/gsc.md), [page](https://verifymcp.io/servers/ai-askwatch-gsc/gsc)

## Channel facts

- Endpoint: `https://mcp.askwatch.ai/gsc`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-25.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1799 tokens (~163/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 99/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 98% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the AskWatch Google Search Console MCP server?

AskWatch Google Search Console MCP is a hosted endpoint at https://mcp.askwatch.ai/gsc, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http ai-askwatch-gsc 'https://mcp.askwatch.ai/gsc'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-askwatch-gsc": {
      "url": "https://mcp.askwatch.ai/gsc"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-askwatch-gsc": {
      "type": "http",
      "url": "https://mcp.askwatch.ai/gsc"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-askwatch-gsc]
url = "https://mcp.askwatch.ai/gsc"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-askwatch-gsc": {
      "type": "remote",
      "url": "https://mcp.askwatch.ai/gsc",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-askwatch-gsc --url 'https://mcp.askwatch.ai/gsc' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-askwatch-gsc:
    url: "https://mcp.askwatch.ai/gsc"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-askwatch-gsc": {
      "Transport": "http",
      "Url": "https://mcp.askwatch.ai/gsc"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-askwatch-gsc -t streamable-http -u 'https://mcp.askwatch.ai/gsc'
```

### Other

```json
{
  "mcpServers": {
    "ai-askwatch-gsc": {
      "type": "http",
      "url": "https://mcp.askwatch.ai/gsc"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-25 (score 75, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 75, +1)

- [security] Tool “brand_split” rewrote its description, which is the text the model reads
- [security] Tool “inspect_url” rewrote its description, which is the text the model reads
- [security] Tool “list_sitemaps” rewrote its description, which is the text the model reads
- [security] Tool “list_sites” rewrote its description, which is the text the model reads
- [security] Tool “query” rewrote its description, which is the text the model reads
- [security] Tool “site_overview” rewrote its description, which is the text the model reads
- [cosmetic] Tool “brand_split” changed its title: Branded vs non-branded
- [cosmetic] Tool “changes” changed its title: What gained and what lost
- [cosmetic] Tool “find_cannibalization” changed its title: Pages competing for one query
- [cosmetic] Tool “find_opportunities” changed its title: Click-through opportunities
- [cosmetic] Tool “inspect_url” changed its title: Index status of a URL
- [cosmetic] Tool “list_sitemaps” changed its title: Submitted sitemaps
- [cosmetic] Tool “list_sites” changed its title: Search Console properties
- [cosmetic] Tool “page_queries” changed its title: Queries for a page
- [cosmetic] Tool “query” changed its title: Raw Search Analytics query
- [cosmetic] Tool “site_overview” changed its title: Site overview
- [cosmetic] Tool “top” changed its title: Top queries and pages

### 2026-09-23 (score 74, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-22 (score 74)

First indexed and scored.

## MCP tools (11)

### `site_overview` (~143 tokens)

Site overview

How the site did over a period compared with the one before it: clicks, impressions, CTR, average position and the change in each. Covers the question 'how is my site doing'.

Input parameters:

- `days` (integer): Length of the window, counted back from the last day with data. Default 28.
- `end_date` (string): YYYY-MM-DD. Defaults to the last day with data.
- `site` (string): Search Console property, exactly as list_sites reports it (sc-domain:example.com or https://example.com/). Optional when the account has only one property.
- `start_date` (string): YYYY-MM-DD. Overrides `days`.

### `top` (~223 tokens)

Top queries and pages

Top queries, pages, countries or devices for a period. Optionally narrowed to one country or device — 'top pages in Germany on mobile' is one call.

Input parameters:

- `country` (string): ISO-3166-1 alpha-3, e.g. deu, usa. Filters rather than groups.
- `days` (integer): Length of the window, counted back from the last day with data. Default 28.
- `device` (string)
- `dimension` (string): What to group by. Default query.
- `end_date` (string): YYYY-MM-DD. Defaults to the last day with data.
- `limit` (integer): Rows to return. Default 25, maximum 100; `has_more` says whether there were more.
- `order_by` (string): Default clicks.
- `site` (string): Search Console property, exactly as list_sites reports it (sc-domain:example.com or https://example.com/). Optional when the account has only one property.
- `start_date` (string): YYYY-MM-DD. Overrides `days`.

### `changes` (~189 tokens)

What gained and what lost

What gained and what lost between this period and the one before it, with small rows filtered out. Answers 'what dropped in the last 28 days'.

Input parameters:

- `days` (integer): Length of the window, counted back from the last day with data. Default 28.
- `dimension` (string): Default query.
- `end_date` (string): YYYY-MM-DD. Defaults to the last day with data.
- `limit` (integer): Rows to return. Default 25, maximum 100; `has_more` says whether there were more.
- `min_impressions` (integer): Noise floor. Default 30 in either window.
- `site` (string): Search Console property, exactly as list_sites reports it (sc-domain:example.com or https://example.com/). Optional when the account has only one property.
- `start_date` (string): YYYY-MM-DD. Overrides `days`.

### `find_opportunities` (~180 tokens)

Click-through opportunities

Queries ranking 5-20 with plenty of impressions but a click-through rate below what is typical at their position — where a title or snippet rewrite is worth the most clicks.

Input parameters:

- `days` (integer): Length of the window, counted back from the last day with data. Default 28.
- `end_date` (string): YYYY-MM-DD. Defaults to the last day with data.
- `limit` (integer): Rows to return. Default 25, maximum 100; `has_more` says whether there were more.
- `min_impressions` (integer): Default 60.
- `site` (string): Search Console property, exactly as list_sites reports it (sc-domain:example.com or https://example.com/). Optional when the account has only one property.
- `start_date` (string): YYYY-MM-DD. Overrides `days`.

### `find_cannibalization` (~171 tokens)

Pages competing for one query

Queries where more than one page of the site is being shown, with how each page does on them.

Input parameters:

- `days` (integer): Length of the window, counted back from the last day with data. Default 28.
- `end_date` (string): YYYY-MM-DD. Defaults to the last day with data.
- `limit` (integer): Rows to return. Default 25, maximum 100; `has_more` says whether there were more.
- `min_impressions` (integer): Per page. Default 30.
- `site` (string): Search Console property, exactly as list_sites reports it (sc-domain:example.com or https://example.com/). Optional when the account has only one property.
- `start_date` (string): YYYY-MM-DD. Overrides `days`.

### `page_queries` (~162 tokens)

Queries for a page

What searches a specific page is shown for.

Input parameters:

- `days` (integer): Length of the window, counted back from the last day with data. Default 28.
- `end_date` (string): YYYY-MM-DD. Defaults to the last day with data.
- `limit` (integer): Rows to return. Default 25, maximum 100; `has_more` says whether there were more.
- `match` (string): Default equals.
- `page` (string, required): Full URL of the page.
- `site` (string): Search Console property, exactly as list_sites reports it (sc-domain:example.com or https://example.com/). Optional when the account has only one property.
- `start_date` (string): YYYY-MM-DD. Overrides `days`.

### `brand_split` (~168 tokens)

Branded vs non-branded

Branded versus non-branded search, split on the words supplied. The split is only as good as those terms: misspellings and the domain name catch more of what people type.

Input parameters:

- `brand_terms` (array, required): Words that make a search branded, e.g. ['askwatch', 'ask watch'].
- `days` (integer): Length of the window, counted back from the last day with data. Default 28.
- `end_date` (string): YYYY-MM-DD. Defaults to the last day with data.
- `site` (string): Search Console property, exactly as list_sites reports it (sc-domain:example.com or https://example.com/). Optional when the account has only one property.
- `start_date` (string): YYYY-MM-DD. Overrides `days`.

### `query` (~205 tokens)

Raw Search Analytics query

Direct query against Google's Search Analytics API, with the same dates, dimensions and filters it takes, passed through unchanged.

Input parameters:

- `days` (integer): Length of the window, counted back from the last day with data. Default 28.
- `dimensions` (array): Group by these. Omit for totals.
- `end_date` (string): YYYY-MM-DD. Defaults to the last day with data.
- `filters` (array): Google's dimensionFilterGroups, passed through unchanged.
- `limit` (integer): Rows to return. Default 25, maximum 100; `has_more` says whether there were more.
- `site` (string): Search Console property, exactly as list_sites reports it (sc-domain:example.com or https://example.com/). Optional when the account has only one property.
- `start_date` (string): YYYY-MM-DD. Overrides `days`.
- `start_row` (integer): Paging offset; `next_start_row` comes back in the answer.

### `list_sites` (~31 tokens)

Search Console properties

Search Console properties this connection can read, from Google's Sites API. These are the exact strings the site argument takes.

### `inspect_url` (~91 tokens)

Index status of a URL

Google's index status for one URL, as the URL Inspection API reports it: whether it is indexed, when it was last crawled, and which canonical Google chose.

Input parameters:

- `site` (string): Search Console property, exactly as list_sites reports it (sc-domain:example.com or https://example.com/). Optional when the account has only one property.
- `url` (string, required): The exact URL to inspect.

### `list_sitemaps` (~77 tokens)

Submitted sitemaps

Sitemaps submitted for the property and their status, from Google's Sitemaps API. Read-only: submitting is not possible with read access.

Input parameters:

- `site` (string): Search Console property, exactly as list_sites reports it (sc-domain:example.com or https://example.com/). Optional when the account has only one property.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-askwatch-gsc/gsc#diagnostics

## Score history

- 2026-09-25: 75
- 2026-09-24: 75
- 2026-09-23: 74
- 2026-09-22: 74

## Common questions

### What is the AskWatch Google Search Console MCP server?

AskWatch Google Search Console MCP is listed in the public MCP registry as ai.askwatch/gsc. Ask Google Search Console in plain language. Hosted, free, no Google Cloud project. This page covers its hosted endpoint (https://mcp.askwatch.ai/gsc).

### Is the AskWatch Google Search Console MCP server safe to use?

AskWatch Google Search Console MCP scores 75 out of 100 on VerifyMCP. 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 AskWatch Google Search Console MCP server expose?

AskWatch Google Search Console MCP exposes 11 tools: site_overview, top, changes, find_opportunities, find_cannibalization, and 6 more. Their descriptions and schemas cost roughly 1,640 tokens of context every time the server is loaded.

### Does the AskWatch Google Search Console MCP server require authentication?

Yes. AskWatch Google Search Console MCP asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the AskWatch Google Search Console MCP server still maintained?

AskWatch Google Search Console MCP 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.

## Links

- Remote endpoint: https://mcp.askwatch.ai/gsc
- Authorisation metadata: https://mcp.askwatch.ai/.well-known/oauth-protected-resource/gsc
- Website: https://askwatch.ai/free-tools/google-search-console-mcp
- Changelog RSS feed: https://verifymcp.io/servers/ai-askwatch-gsc/gsc.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-askwatch-gsc/gsc.json
- HTML version of this page: https://verifymcp.io/servers/ai-askwatch-gsc/gsc