AskWatch Google Search Console MCP
REMOTE · MCP.ASKWATCH.AI · SCANNED SEP 25
Ask Google Search Console in plain language. Hosted, free, no Google Cloud project.
Available components
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. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 98% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 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
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.
remote · mcp.askwatch.ai
claude mcp add --transport http ai-askwatch-gsc 'https://mcp.askwatch.ai/gsc'
{
"mcpServers": {
"ai-askwatch-gsc": {
"url": "https://mcp.askwatch.ai/gsc"
}
}
} {
"servers": {
"ai-askwatch-gsc": {
"type": "http",
"url": "https://mcp.askwatch.ai/gsc"
}
}
} [mcp_servers.ai-askwatch-gsc] url = "https://mcp.askwatch.ai/gsc"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-askwatch-gsc": {
"type": "remote",
"url": "https://mcp.askwatch.ai/gsc",
"enabled": true
}
}
} openclaw mcp add ai-askwatch-gsc --url 'https://mcp.askwatch.ai/gsc' --transport streamable-http
mcp_servers:
ai-askwatch-gsc:
url: "https://mcp.askwatch.ai/gsc" {
"McpServers": {
"ai-askwatch-gsc": {
"Transport": "http",
"Url": "https://mcp.askwatch.ai/gsc"
}
}
} assistant mcp add ai-askwatch-gsc -t streamable-http -u 'https://mcp.askwatch.ai/gsc'
{
"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.
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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
- 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 security
- 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 cosmetic
- 23 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 22 Sept 26 74
First indexed and scored.
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 25 Sept 2026 · Probed https://mcp.askwatch.ai/gsc
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.askwatch.ai | CN=YE1,O=Let's Encrypt,C=US | 21 Sept 2026 | 20 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 66c4c56b1f224f2897cda6aa811eae3bac0 |
| SANs: mcp.askwatch.ai | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.askwatch.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| askwatch.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="askwatch-gsc", error="invalid_token"
Bearer realm="askwatch-gsc", error="invalid_token"Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.askwatch.ai/gsc | Verified | 200 | |
| http (plaintext) | http://mcp.askwatch.ai/gsc | HTTPS enforced | 301 | https://mcp.askwatch.ai/gsc |
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 →
brand_split Branded vs non-branded ~168
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.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_terms | array | yes | 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`. |
No output schema declared.
No examples provided.
changes What gained and what lost ~189
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'.
| Name | Type | Req | Description |
|---|---|---|---|
| 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`. |
No output schema declared.
No examples provided.
find_cannibalization Pages competing for one query ~171
Queries where more than one page of the site is being shown, with how each page does on them.
| Name | Type | Req | Description |
|---|---|---|---|
| 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`. |
No output schema declared.
No examples provided.
find_opportunities Click-through opportunities ~180
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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`. |
No output schema declared.
No examples provided.
inspect_url Index status of a URL ~91
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The exact URL to inspect. |
No output schema declared.
No examples provided.
list_sitemaps Submitted sitemaps ~77
Sitemaps submitted for the property and their status, from Google's Sitemaps API. Read-only: submitting is not possible with read access.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
list_sites Search Console properties ~31
Search Console properties this connection can read, from Google's Sites API. These are the exact strings the site argument takes.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
page_queries Queries for a page ~162
What searches a specific page is shown for.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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`. |
No output schema declared.
No examples provided.
query Raw Search Analytics query ~205
Direct query against Google's Search Analytics API, with the same dates, dimensions and filters it takes, passed through unchanged.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
site_overview Site overview ~143
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'.
| Name | Type | Req | Description |
|---|---|---|---|
| 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`. |
No output schema declared.
No examples provided.
top Top queries and pages ~223
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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`. |
No output schema declared.
No examples provided.
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.