F
Warning
35/100
3 days ago

mcp-gsc

Google Search Console Insights with Claude AI for SEOs

Warning. Serious findings were identified. Review the full report before connecting. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

AminForou

Source: github_code · also listed on mcp.so, PulseMCP, modelscope, github_topic

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
🚨
Reads files from sensitive locations
Touches: service_account_credentials.json, service_account_credentials.json
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configGSC_CREDENTIALS_PATH"": "/full/path/to/service_account.json",
configGSC_OAUTH_CLIENT_SECRETS_FILE"": "/full/path/to/client_secrets.json"
configGSC_CONFIG_DIR
configGSC_SKIP_OAUTH"": "true"
configGSC_ALLOW_DESTRUCTIVENo false Set to "true" to enable add/delete site and delete sitemap tools
configGSC_DATA_STATENo "all" "all" matches the GSC dashboard. "final" returns only confirmed data (2–3 day lag).
configMCP_TRANSPORTsse MCP_HOST=0.0.0.0 MCP_PORT=3001 python gsc_server.py
configMCP_HOSTMCP_TRANSPORT=sse =0.0.0.0 MCP_PORT=3001 python gsc_server.py
configMCP_PORTMCP_TRANSPORT=sse MCP_HOST=0.0.0.0 =3001 python gsc_server.py
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

21/21 tools missing one or more hints — get_capabilities (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_properties (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); add_site (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +18 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Destructive tools are labelled

1 tool perform destructive updates without destructiveHint — reauthenticate deletes at line 1640 (os.remove(TOKEN_FILE))

Add destructiveHint:true to any tool whose handler calls .delete(), .upsert(), .update(), unlink, rm, DELETE, DROP, REPLACE INTO, or any operation that overwrites existing data.

No access to sensitive paths

Reads sensitive paths: service_account_credentials.json, service_account_credentials.json

Remove reads of sensitive system paths. If you genuinely need them, document why in the README.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 4 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/aminforou-mcp-gsc-1n3e3u?variant=verified)](https://m8ven.ai/mcp/aminforou-mcp-gsc-1n3e3u)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: b3f2ab829ebc8f8294440821b4d476d75b5edadd
code hash: c3506b2186e4a8b344acb1f335380dc8dcd52a3f1450a2d32b227639e220b4d7
verified: 8/16/2026, 9:05:01 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client