gsc-mcp (scalably-io/gsc-mcp) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 5 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100

gsc-mcp

Read-only MCP server for Google Search Console: Search Analytics, sitemaps, URL inspection. Runs in production at Scalably.

→ scalably-io/gsc-mcp· listed on github_repo_search

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. 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

scalably-io

Source: github_repo_search

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 →

⚡ Connect GitHub for Live Monitored

Install from

GitHub

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
✅
5 tools verified — handlers match their declared behaviour
5 read-only tools verified — handlers contain no write/delete/exec
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 1 credential: GSC_TEST_ACCESS_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// 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_WEBMASTERS_BASEOverride the two Google API base URLs (used by the test suite to point at a local fake; leave unset in normal use)
configGSC_SEARCHCONSOLE_BASEOverride the two Google API base URLs (used by the test suite to point at a local fake; leave unset in normal use)
configGOOGLE_APPLICATION_CREDENTIALSPath to a Google service-account JSON file with the Search Console read-only scope; share each property with the service account email
🔐 secretGSC_TEST_ACCESS_TOKENTest-suite only: a literal bearer token that bypasses the service account. Never set it in normal use
configGSC_RETRY_BASE_SECONDSBase delay in seconds for the retry backoff on transient API errors (default 1)
configGSC_LOG_LEVELINFO (default) or DEBUG
// quality suggestions

All four hints declared on every tool

5/5 tools missing one or more hints — gsc_list_sites (missing: destructiveHint, idempotentHint); gsc_query_search_analytics (missing: destructiveHint, idempotentHint); gsc_list_sitemaps (missing: destructiveHint, idempotentHint), +2 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.

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 1 concrete improvement 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 Score](https://m8ven.ai/badge/mcp/scalably-io/gsc-mcp)](https://m8ven.ai/mcp/scalably-io/gsc-mcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 357b2eb090872c4e5ae9a83f4842eb0ea040cd48
code hash: 4221ee2a63df6d44240ba8f3beef97d08796b666dc94bb023ce24ca5acb6855d
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