Read-only MCP server for Google Search Console performance and URL inspection.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"flin-google-search-console-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# flin-google-search-console-mcp Read-only MCP server for Google Search Console, built to work well in Claude Desktop with a browser-based OAuth flow and local token storage. ## Claude Desktop Quickstart If your goal is simply "make this work in Claude Desktop", follow these steps in order. ### 1) Make sure the Google account has Search Console access The Google account you use during login must already have access to at least one Search Console property. Accepted access levels for the API include owner, full, and read access. ### 2) Create or choose a Google Cloud project In Google Cloud: 1. Create a new project or select an existing one. 2. Enable the **Google Search Console API** for that project. Official references: - [Search Console API overview](https://developers.google.com/webmaster-tools/about) - [Search Console API quickstart](https://developers.google.com/webmaster-tools/v1/quickstart/quickstart-python) ### 3) Configure the OAuth consent screen In Google Cloud, configure the OAuth consent screen for the same project. For most personal or team setups: - choose `External` - keep the app in `Testing` while you validate the integration - add your own Google account as a **test user** Important: - If the app is `External` and still in `Testing`, users must be listed as test users - Google documents that test-user authorizations in testing mode can expire after 7 days This MCP only requests one read-only scope: - `https://www.googleapis.com/auth/webmasters.readonly` Official references: - [OAuth 2.0 for Desktop Apps](https://developers.google.com/identity/protocols/oauth2/native-app) - [OAuth consent screen configuration](https://support.google.com/cloud/answer/13461325?hl=en) - [Publishing status and test users](https://support.google.com/cloud/answer/15549945?hl=en) ### 4) Create OAuth credentials of type `Desktop app` Create an OAuth client in the same Google Cloud project: 1. Go to **Credentials** 2. Click **Create client** 3. Choo…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.