# GA4 SEO MCP (oci · ghcr.io/germaniu/ga4-seo-mcp)

Set up and audit site measurement: GA4, Search Console and PageSpeed. Read-only unless enabled.

- Trust score: 47/100 (low)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- oci · `ghcr.io/germaniu/ga4-seo-mcp`: 47/100 (this document), [markdown](https://verifymcp.io/servers/germaniu-ga4-seo-mcp/ghcr-io-germaniu-ga4-seo-mcp.md), [page](https://verifymcp.io/servers/germaniu-ga4-seo-mcp/ghcr-io-germaniu-ga4-seo-mcp)
- pypi · `ga4-seo-mcp`: 87/100, [markdown](https://verifymcp.io/servers/germaniu-ga4-seo-mcp/ga4-seo-mcp.md), [page](https://verifymcp.io/servers/germaniu-ga4-seo-mcp/ga4-seo-mcp)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/germaniu/ga4-seo-mcp`
- Version: `0.1.2`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-11-05.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 12 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 76/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 2358 tokens (~98/item across 24 items; 24 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 24 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 25 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.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the GA4 SEO MCP server?

GA4 SEO MCP runs locally as a container image, launched with docker run --rm -i -e GOOGLE_APPLICATION_CREDENTIALS -e GA4SEO_TOOLSETS -e GA4SEO_ENABLE_WRITES -e PAGESPEED_API_KEY -e DATAFORSEO_LOGIN -e DATAFORSEO_PASSWORD -e GOOGLE_ADS_DEVELOPER_TOKEN -e GOOGLE_ADS_LOGIN_CUSTOMER_ID ghcr.io/germaniu/ga4-seo-mcp:0.1.2, plus the required --volume, which you supply. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add germaniu-ga4-seo-mcp -- docker run --rm -i -e GOOGLE_APPLICATION_CREDENTIALS -e GA4SEO_TOOLSETS -e GA4SEO_ENABLE_WRITES -e PAGESPEED_API_KEY -e DATAFORSEO_LOGIN -e DATAFORSEO_PASSWORD -e GOOGLE_ADS_DEVELOPER_TOKEN -e GOOGLE_ADS_LOGIN_CUSTOMER_ID ghcr.io/germaniu/ga4-seo-mcp:0.1.2
```

This image reads GOOGLE_APPLICATION_CREDENTIALS, GA4SEO_TOOLSETS, GA4SEO_ENABLE_WRITES, PAGESPEED_API_KEY, DATAFORSEO_LOGIN, DATAFORSEO_PASSWORD, GOOGLE_ADS_DEVELOPER_TOKEN and GOOGLE_ADS_LOGIN_CUSTOMER_ID. Set them in your client's env block for this server; docker run -e passes each one through to the container. Incomplete: the registry marks --volume as required and gives no value we can show, so it is not in this command. Add it before you run it.

### Cursor

```json
{
  "mcpServers": {
    "germaniu-ga4-seo-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "GOOGLE_APPLICATION_CREDENTIALS",
        "-e",
        "GA4SEO_TOOLSETS",
        "-e",
        "GA4SEO_ENABLE_WRITES",
        "-e",
        "PAGESPEED_API_KEY",
        "-e",
        "DATAFORSEO_LOGIN",
        "-e",
        "DATAFORSEO_PASSWORD",
        "-e",
        "GOOGLE_ADS_DEVELOPER_TOKEN",
        "-e",
        "GOOGLE_ADS_LOGIN_CUSTOMER_ID",
        "ghcr.io/germaniu/ga4-seo-mcp:0.1.2"
      ]
    }
  }
}
```

This image reads GOOGLE_APPLICATION_CREDENTIALS, GA4SEO_TOOLSETS, GA4SEO_ENABLE_WRITES, PAGESPEED_API_KEY, DATAFORSEO_LOGIN, DATAFORSEO_PASSWORD, GOOGLE_ADS_DEVELOPER_TOKEN and GOOGLE_ADS_LOGIN_CUSTOMER_ID. Set them in your client's env block for this server; docker run -e passes each one through to the container. Incomplete: the registry marks --volume as required and gives no value we can show, so it is not in this command. Add it before you run it.

### VS Code

```json
{
  "servers": {
    "germaniu-ga4-seo-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "GOOGLE_APPLICATION_CREDENTIALS",
        "-e",
        "GA4SEO_TOOLSETS",
        "-e",
        "GA4SEO_ENABLE_WRITES",
        "-e",
        "PAGESPEED_API_KEY",
        "-e",
        "DATAFORSEO_LOGIN",
        "-e",
        "DATAFORSEO_PASSWORD",
        "-e",
        "GOOGLE_ADS_DEVELOPER_TOKEN",
        "-e",
        "GOOGLE_ADS_LOGIN_CUSTOMER_ID",
        "ghcr.io/germaniu/ga4-seo-mcp:0.1.2"
      ]
    }
  }
}
```

This image reads GOOGLE_APPLICATION_CREDENTIALS, GA4SEO_TOOLSETS, GA4SEO_ENABLE_WRITES, PAGESPEED_API_KEY, DATAFORSEO_LOGIN, DATAFORSEO_PASSWORD, GOOGLE_ADS_DEVELOPER_TOKEN and GOOGLE_ADS_LOGIN_CUSTOMER_ID. Set them in your client's env block for this server; docker run -e passes each one through to the container. Incomplete: the registry marks --volume as required and gives no value we can show, so it is not in this command. Add it before you run it.

### Codex

```bash
codex mcp add germaniu-ga4-seo-mcp -- docker run --rm -i -e GOOGLE_APPLICATION_CREDENTIALS -e GA4SEO_TOOLSETS -e GA4SEO_ENABLE_WRITES -e PAGESPEED_API_KEY -e DATAFORSEO_LOGIN -e DATAFORSEO_PASSWORD -e GOOGLE_ADS_DEVELOPER_TOKEN -e GOOGLE_ADS_LOGIN_CUSTOMER_ID ghcr.io/germaniu/ga4-seo-mcp:0.1.2
```

This image reads GOOGLE_APPLICATION_CREDENTIALS, GA4SEO_TOOLSETS, GA4SEO_ENABLE_WRITES, PAGESPEED_API_KEY, DATAFORSEO_LOGIN, DATAFORSEO_PASSWORD, GOOGLE_ADS_DEVELOPER_TOKEN and GOOGLE_ADS_LOGIN_CUSTOMER_ID. Set them in your client's env block for this server; docker run -e passes each one through to the container. Incomplete: the registry marks --volume as required and gives no value we can show, so it is not in this command. Add it before you run it.

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "germaniu-ga4-seo-mcp": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "-e",
        "GOOGLE_APPLICATION_CREDENTIALS",
        "-e",
        "GA4SEO_TOOLSETS",
        "-e",
        "GA4SEO_ENABLE_WRITES",
        "-e",
        "PAGESPEED_API_KEY",
        "-e",
        "DATAFORSEO_LOGIN",
        "-e",
        "DATAFORSEO_PASSWORD",
        "-e",
        "GOOGLE_ADS_DEVELOPER_TOKEN",
        "-e",
        "GOOGLE_ADS_LOGIN_CUSTOMER_ID",
        "ghcr.io/germaniu/ga4-seo-mcp:0.1.2"
      ],
      "enabled": true
    }
  }
}
```

This image reads GOOGLE_APPLICATION_CREDENTIALS, GA4SEO_TOOLSETS, GA4SEO_ENABLE_WRITES, PAGESPEED_API_KEY, DATAFORSEO_LOGIN, DATAFORSEO_PASSWORD, GOOGLE_ADS_DEVELOPER_TOKEN and GOOGLE_ADS_LOGIN_CUSTOMER_ID. Set them in your client's env block for this server; docker run -e passes each one through to the container. Incomplete: the registry marks --volume as required and gives no value we can show, so it is not in this command. Add it before you run it.

### Hermes

```yaml
mcp_servers:
  germaniu-ga4-seo-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "-e", "GOOGLE_APPLICATION_CREDENTIALS", "-e", "GA4SEO_TOOLSETS", "-e", "GA4SEO_ENABLE_WRITES", "-e", "PAGESPEED_API_KEY", "-e", "DATAFORSEO_LOGIN", "-e", "DATAFORSEO_PASSWORD", "-e", "GOOGLE_ADS_DEVELOPER_TOKEN", "-e", "GOOGLE_ADS_LOGIN_CUSTOMER_ID", "ghcr.io/germaniu/ga4-seo-mcp:0.1.2"]
```

This image reads GOOGLE_APPLICATION_CREDENTIALS, GA4SEO_TOOLSETS, GA4SEO_ENABLE_WRITES, PAGESPEED_API_KEY, DATAFORSEO_LOGIN, DATAFORSEO_PASSWORD, GOOGLE_ADS_DEVELOPER_TOKEN and GOOGLE_ADS_LOGIN_CUSTOMER_ID. Set them in your client's env block for this server; docker run -e passes each one through to the container. Incomplete: the registry marks --volume as required and gives no value we can show, so it is not in this command. Add it before you run it.

### Netclaw

```json
{
  "McpServers": {
    "germaniu-ga4-seo-mcp": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "-e",
        "GOOGLE_APPLICATION_CREDENTIALS",
        "-e",
        "GA4SEO_TOOLSETS",
        "-e",
        "GA4SEO_ENABLE_WRITES",
        "-e",
        "PAGESPEED_API_KEY",
        "-e",
        "DATAFORSEO_LOGIN",
        "-e",
        "DATAFORSEO_PASSWORD",
        "-e",
        "GOOGLE_ADS_DEVELOPER_TOKEN",
        "-e",
        "GOOGLE_ADS_LOGIN_CUSTOMER_ID",
        "ghcr.io/germaniu/ga4-seo-mcp:0.1.2"
      ]
    }
  }
}
```

This image reads GOOGLE_APPLICATION_CREDENTIALS, GA4SEO_TOOLSETS, GA4SEO_ENABLE_WRITES, PAGESPEED_API_KEY, DATAFORSEO_LOGIN, DATAFORSEO_PASSWORD, GOOGLE_ADS_DEVELOPER_TOKEN and GOOGLE_ADS_LOGIN_CUSTOMER_ID. Set them in your client's env block for this server; docker run -e passes each one through to the container. Incomplete: the registry marks --volume as required and gives no value we can show, so it is not in this command. Add it before you run it.

### Other

```json
{
  "mcpServers": {
    "germaniu-ga4-seo-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "GOOGLE_APPLICATION_CREDENTIALS",
        "-e",
        "GA4SEO_TOOLSETS",
        "-e",
        "GA4SEO_ENABLE_WRITES",
        "-e",
        "PAGESPEED_API_KEY",
        "-e",
        "DATAFORSEO_LOGIN",
        "-e",
        "DATAFORSEO_PASSWORD",
        "-e",
        "GOOGLE_ADS_DEVELOPER_TOKEN",
        "-e",
        "GOOGLE_ADS_LOGIN_CUSTOMER_ID",
        "ghcr.io/germaniu/ga4-seo-mcp:0.1.2"
      ]
    }
  }
}
```

This image reads GOOGLE_APPLICATION_CREDENTIALS, GA4SEO_TOOLSETS, GA4SEO_ENABLE_WRITES, PAGESPEED_API_KEY, DATAFORSEO_LOGIN, DATAFORSEO_PASSWORD, GOOGLE_ADS_DEVELOPER_TOKEN and GOOGLE_ADS_LOGIN_CUSTOMER_ID. Set them in your client's env block for this server; docker run -e passes each one through to the container. Incomplete: the registry marks --volume as required and gives no value we can show, so it is not in this command. Add it before you run it.

## 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-11-05 (score 47, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 46, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 45, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 44, 0)

- [security regression] Provenance: unverified → fail

### 2026-10-29 (score 44, +1)

- [security regression] Provenance: fail → unverified

### 2026-10-27 (score 43, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-25 (score 42, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 41, 0)

- [functional] Package version: 0.1.0 → 0.1.2

## MCP tools (24)

### `list_account_summaries` (~44 tokens)

List every GA4 account you can access, with a summary of its properties.

    Start here to find the account_id and property_id the other tools need.

Output parameters:

- `result` (array)

### `list_properties` (~72 tokens)

List the GA4 properties under an account.

    Args:
        account_id: numeric account ID or 'accounts/123456789'.
        include_deleted: also return properties in the trash (soft-deleted, kept 35 days).

Input parameters:

- `account_id` (string, required)
- `include_deleted` (boolean)

Output parameters:

- `result` (array)

### `get_property` (~35 tokens)

Get the full settings of a GA4 property (time zone, currency, industry, type).

Input parameters:

- `property_id` (string, required)

### `list_data_streams` (~54 tokens)

List the data streams (web, iOS, Android) of a GA4 property.

    Web streams include their measurement ID (G-XXXXXXX) and default URI.

Input parameters:

- `property_id` (string, required)

Output parameters:

- `result` (array)

### `get_data_stream` (~39 tokens)

Get one data stream, including the measurement ID of a web stream.

Input parameters:

- `property_id` (string, required)
- `stream_id` (string, required)

### `list_key_events` (~32 tokens)

List the key events (formerly conversions) declared on a GA4 property.

Input parameters:

- `property_id` (string, required)

Output parameters:

- `result` (array)

### `list_custom_dimensions` (~32 tokens)

List the custom dimensions declared on a GA4 property, with their scope.

Input parameters:

- `property_id` (string, required)

Output parameters:

- `result` (array)

### `list_google_ads_links` (~31 tokens)

List the links between a GA4 property and Google Ads accounts.

Input parameters:

- `property_id` (string, required)

Output parameters:

- `result` (array)

### `bootstrap_site_measurement` (~410 tokens)

Plan, and optionally apply, the full measurement setup of a website.

        With apply=False (default) nothing is changed: it detects what already exists for the
        site (GA4 property and web stream matched by the site's domain, key events, custom
        dimensions, Search Console domain property) and returns the steps that would run.
        Show this plan to the user and get explicit confirmation before calling apply=True.

        With apply=True (requires the server to run with --enable-writes) it creates only the
        missing pieces, skipping what exists, so it is safe to re-run. It returns a step-by-step
        report with the GA4 measurement ID (G-...) and the DNS TXT token for Search Console.
        DNS verification and sitemap submission stay manual follow-up steps
        (sc_verify_site_dns, sc_submit_sitemap) because the TXT record must be published first.

        Args:
            site_url: the site, e.g. 'https://example.com'.
            account_id: GA4 account that owns (or will own) the property; see
                list_account_summaries.
            property_display_name: name for a new property; also used to find an existing one.
            time_zone: IANA time zone for a new property, e.g. 'America/Mexico_City'.
            currency_code: ISO 4217 currency for a new property, e.g. 'USD'.
            key_events: event names to mark as key events, e.g. ['generate_lead'].
            custom_dimensions: parameters to register as custom dimensions.
            apply: False = plan only (default); True = execute the plan.

Input parameters:

- `account_id` (string, required)
- `apply` (boolean)
- `currency_code` (string, required)
- `custom_dimensions`
- `key_events`
- `property_display_name` (string, required)
- `site_url` (string, required)
- `time_zone` (string, required)

### `run_report` (~268 tokens)

Run a flexible GA4 report.

    Args:
        property_id: numeric ID or 'properties/123456789'.
        metrics: e.g. ['sessions', 'activeUsers', 'keyEvents']. Catalog:
            https://developers.google.com/analytics/devguides/reporting/data/v1/api-schema#metrics
        dimensions: optional, e.g. ['date', 'sessionSource', 'pagePath']. Catalog:
            https://developers.google.com/analytics/devguides/reporting/data/v1/api-schema#dimensions
        date_start: 'YYYY-MM-DD', 'today', 'yesterday' or 'NdaysAgo' (e.g. '28daysAgo').
        date_end: same formats as date_start.
        limit: maximum rows (default 25).
        order_by_metric: sort by this metric, e.g. 'sessions'.
        order_desc: sort descending (default True).

    Returns the dimension and metric names, the date range, row_count and the rows.

Input parameters:

- `date_end` (string)
- `date_start` (string)
- `dimensions`
- `limit` (integer)
- `metrics` (array, required)
- `order_by_metric`
- `order_desc` (boolean)
- `property_id` (string, required)

### `run_realtime_report` (~102 tokens)

Realtime report for the last 30 minutes.

    Useful to confirm that a new event fires in production right after a deploy.

    Args:
        metrics: default ['activeUsers']; 'eventCount' also works.
        dimensions: default ['eventName']; also 'unifiedScreenName', 'country', 'deviceCategory'.

Input parameters:

- `dimensions`
- `limit` (integer)
- `metrics`
- `property_id` (string, required)

### `top_pages` (~55 tokens)

Top pages by sessions, with active users, bounce rate and average session duration.

Input parameters:

- `date_end` (string)
- `date_start` (string)
- `limit` (integer)
- `property_id` (string, required)

### `events_summary` (~70 tokens)

Count of every event that fired, to audit what is actually being measured.

    Compare it with list_key_events to find key events that never fire.

Input parameters:

- `date_end` (string)
- `date_start` (string)
- `limit` (integer)
- `property_id` (string, required)

### `traffic_sources` (~55 tokens)

Top traffic sources (source / medium) with sessions, active users and conversions.

Input parameters:

- `date_end` (string)
- `date_start` (string)
- `limit` (integer)
- `property_id` (string, required)

### `conversions_summary` (~49 tokens)

Conversions and total users per event name: a summary of the active key events.

Input parameters:

- `date_end` (string)
- `date_start` (string)
- `property_id` (string, required)

### `web_vitals_summary` (~98 tokens)

Core Web Vitals reported by your own site as GA4 events.

    Requires the site to send web-vitals events with the parameters `web_vital_metric` and
    `web_vital_rating`, both registered as event-scoped custom dimensions.
    For Google's field data use psi_field_data_only instead.

Input parameters:

- `date_end` (string)
- `date_start` (string)
- `property_id` (string, required)

### `audit_portfolio` (~94 tokens)

Summary metrics for several GA4 properties in one call.

    Returns sessions, active users, conversions, bounce rate and average session duration per
    property, plus the properties that failed and why.

    Args:
        property_ids: e.g. ['123456789', '987654321'].

Input parameters:

- `date_end` (string)
- `date_start` (string)
- `property_ids` (array, required)

### `sc_list_sites` (~77 tokens)

List the Search Console sites you can access.

    Each entry has `siteUrl` ('sc-domain:example.com' for domain properties or a URL prefix
    like 'https://example.com/') and `permissionLevel` ('siteOwner', 'siteFullUser',
    'siteRestrictedUser' or 'siteUnverifiedUser').

Output parameters:

- `result` (array)

### `sc_top_queries` (~157 tokens)

Top search queries with clicks, impressions, CTR (%) and average position.

    Args:
        site_url: 'sc-domain:example.com' or 'https://example.com/', exactly as in sc_list_sites.
        date_start: 'YYYY-MM-DD'.
        date_end: 'YYYY-MM-DD'. Search Console data lags 2-3 days.
        limit: rows to return (max 25000).
        country: optional ISO 3166-1 alpha-3 code to filter by, e.g. 'mex' or 'usa'.

Input parameters:

- `country`
- `date_end` (string, required)
- `date_start` (string, required)
- `limit` (integer)
- `site_url` (string, required)

### `sc_page_performance` (~58 tokens)

Top pages in Google Search by clicks, with impressions, CTR (%) and average position.

Input parameters:

- `date_end` (string, required)
- `date_start` (string, required)
- `limit` (integer)
- `site_url` (string, required)

### `sc_query_breakdown_by_page` (~76 tokens)

Which search queries bring traffic to one specific page.

    Useful to decide which keywords to strengthen in that page's content.

Input parameters:

- `date_end` (string, required)
- `date_start` (string, required)
- `limit` (integer)
- `page_url` (string, required)
- `site_url` (string, required)

### `sc_list_sitemaps` (~36 tokens)

List the sitemaps submitted for a Search Console site, with errors and warnings.

Input parameters:

- `site_url` (string, required)

Output parameters:

- `result` (array)

### `psi_audit` (~203 tokens)

Run a PageSpeed Insights audit (Lighthouse lab test + CrUX field data) on a public URL.

    Takes 30-90 seconds. Without PAGESPEED_API_KEY the anonymous quota is small and Google
    may answer 429; set the key for regular use.

    Args:
        url: absolute public URL, e.g. 'https://example.com/'.
        strategy: 'mobile' (default) or 'desktop'.
        categories: subset of ['performance', 'accessibility', 'best-practices', 'seo'].
            Default: all four.

    Returns 0-100 category scores, lab Core Web Vitals (LCP, FCP, CLS, TBT, SI, TTFB) and,
    when Chrome has enough real-user traffic, CrUX p75 field data for the URL and its origin.

Input parameters:

- `categories`
- `strategy` (string)
- `url` (string, required)

### `psi_field_data_only` (~96 tokens)

Only the CrUX field data (real Chrome users, p75 over 28 days) for a URL and its origin.

    PageSpeed Insights still runs a performance-only Lighthouse pass, so expect 15-40 seconds.
    `overall_category` is FAST, AVERAGE or SLOW; it is null when the page has too little traffic.

Input parameters:

- `strategy` (string)
- `url` (string, required)

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/germaniu-ga4-seo-mcp/ghcr-io-germaniu-ga4-seo-mcp#diagnostics

## Score history

- 2026-11-05: 47
- 2026-11-04: 46
- 2026-11-03: 46
- 2026-11-02: 46
- 2026-11-01: 45
- 2026-10-31: 45
- 2026-10-30: 44
- 2026-10-29: 44
- 2026-10-28: 43
- 2026-10-27: 43
- 2026-10-26: 42
- 2026-10-25: 42
- 2026-10-24: 41
- 2026-10-23: 41
- 2026-10-22: 40
- 2026-10-21: 40
- 2026-10-20: 39
- 2026-10-19: 39

## Common questions

### What is the GA4 SEO MCP server?

GA4 SEO MCP is listed in the public MCP registry as io.github.GermaniU/ga4-seo-mcp. Set up and audit site measurement: GA4, Search Console and PageSpeed. Read-only unless enabled. This page covers its container image (ghcr.io/germaniu/ga4-seo-mcp).

### Is the GA4 SEO MCP server safe to use?

GA4 SEO MCP scores 47 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 GA4 SEO MCP server expose?

GA4 SEO MCP exposes 24 tools: list_account_summaries, list_properties, get_property, list_data_streams, get_data_stream, and 19 more. Their descriptions and schemas cost roughly 2,243 tokens of context every time the server is loaded.

### Is the GA4 SEO MCP server still maintained?

GA4 SEO MCP is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the GA4 SEO MCP server under?

GA4 SEO MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the GA4 SEO MCP server?

VerifyMCP ran 12 checks on GA4 SEO MCP, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about GA4 SEO MCP: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- GitHub Container Registry: https://ghcr.io/germaniu/ga4-seo-mcp
- Repository: https://github.com/GermaniU/ga4-seo-mcp
- Changelog RSS feed: https://verifymcp.io/servers/germaniu-ga4-seo-mcp/ghcr-io-germaniu-ga4-seo-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/germaniu-ga4-seo-mcp/ghcr-io-germaniu-ga4-seo-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/germaniu-ga4-seo-mcp/ghcr-io-germaniu-ga4-seo-mcp.json
- HTML version of this page: https://verifymcp.io/servers/germaniu-ga4-seo-mcp/ghcr-io-germaniu-ga4-seo-mcp