seo-tools-mcp-gsc

Name: seo-tools-mcp-gsc
Author: io.github.antohins

MCPcommunity

v1.8.0io.github.antohinsUnknownUpdated 8d agonpm GitHub

Google Search Console: Search Analytics, URL Inspection, sitemaps (read-only, OAuth/service acct).

Works in

ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

8d agoLast update

Reads these credentials

GOOGLE_CLIENT_SECRETOAuth appoptional
Google OAuth client secret.
GSC_REFRESH_TOKENOAuth appoptional
Google OAuth refresh token (or obtain via gsc_oauth_start).

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package

Authorio.github.antohins

LicenseUnknown

Version1.8.0

Sourcenpm+mcp-registry

npmseo-tools-mcp-gsc

GitHubantohins/seo-tools-mcp

SBOMCycloneDX 1.6 ↓

Trust Status

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/20

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/5

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

—npm Trusted Publishing (Sigstore)+0/5

→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo

—npm maintainer match+0/5

→ Earned once your identity is verified above and that login is an npm maintainer of this package

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusCommunity-indexed

PublisherUnverified

SignatureUnsigned

Domain—

Provenance—

Dependencies60 resolved · 1 with advisories

Tool surface6 tools · none privileged

Security scan✓ Cleanv1.7.0 · 18d agoHow well does this scan work?

MODERATEuuid@9.0.1uuid: Missing buffer bounds check in v3/v5/v6 when buf is provided · transitive

EvalsNone

IndexedJul 18, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

6 tools · none privileged

Statically extracted from the published packagev1.7.0 · 18d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

gsc_queryNo description published