Case file No.171 · pypi · stdio

Google Search Console

io.github.acamolese/google-search-console-mcp · v3.0.1

Google Search Console: SEO audits, performance queries, URL inspection, indexing checks.

Package ↗GitHub ↗Website ↗

Security score

93/100

Strong

Normalized over 100 points of available evidence.

Score breakdown

Known advisories40/40

0 affecting current version, 0 historical

Maintenance20/20

last push 7 days ago

Source transparency15/15

public repo, license MIT

Metadata stability15/15

0 risky metadata change(s) without a version bump

Adoption3/10

674 weekly downloads

Known advisories

source: OSV.dev

No advisories found in OSV for this package name. (Not proof of safety.)

Metadata change timeline

rug-pull detection

First snapshot (v3.0.1)Oct 16, 2026

No changes observed yet across 1 snapshot(s).

Tool lists: not published by the registry — unknown.

FAQ

auto-generated from the data above

Is Google Search Console safe?

MCPWatch gives Google Search Console a heuristic security score of 93/100 (strong), based on 100 points of available evidence. This is an automated heuristic, not an audit.

Does Google Search Console have known CVEs or vulnerabilities?

No advisories were found in OSV.dev for the pypi package mcp-google-search-console. That is not proof of safety.

When was Google Search Console last updated?

The latest registry version is 3.0.1, published Aug 22, 2026. The last push to acamolese/google-search-console-mcp was on Oct 13, 2026. MCPWatch last checked it on Oct 20, 2026.

What license does Google Search Console use?

GitHub reports the license of acamolese/google-search-console-mcp as MIT.

Related servers

same publisher / similar score