search-console-mcp-server@0.2.1
Talk to your Google Search Console from Claude, Cursor, or any MCP client — one sign-in, no Google Cloud project required.
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe post-login redirect deliberately reports the flow source and package version to the publisher’s site without a disclosed opt-out, so this is suspicious runtime telemetry. The inspected OAuth and Search Console requests send credentials and data to Google, and the redirect contains no Google token.
Decision evidence
public snapshot- After Google sign-in, the browser is redirected to the publisher’s site with `source=mcp-login` and the package version in the URL.
- The CLI handles login only when invoked with the `login` command; successful authentication triggers the redirect.
- The package sends no Google credentials to Percy in the inspected flow; token exchange and Search Console API requests target Google.
- OAuth uses Google’s authorization and token endpoints, and requests Search Console data from Google.
- The package stores tokens locally in `~/.search-console-mcp/credentials.json`.
- The manifest’s `prepublishOnly` script builds the package; it is not an install hook.
Source & flagged code
4 flaggedA single source file combines environment access, network access, and code or shell execution; review context before blocking.
dist/index.jsView on unpkg · L3Findings
Affected versions and remediation
This report applies to search-console-mcp-server@0.2.1.
See all versions of search-console-mcp-server for other recorded verdicts.
- Review the evidence and your use of search-console-mcp-server@0.2.1 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.