Awesome Gsc MCP Server

awesome-gsc-mcp npm v1.0.0

Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

Trust grade
A
98/100
Last scanned get badge →
Trust
A · 98/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Minimal
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
A Why this grade threat 100 − adoption risk = 98/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 2 = 98. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 27

Each tool and what it can reach — statically extracted from the published source.

  • add_propertyno sensitive capability
  • analyze_query_landscapeno sensitive capability
  • batch_inspect_urlsno sensitive capability
  • check_indexing_issuesno sensitive capability
  • compare_periodsno sensitive capability
  • delete_propertyno sensitive capability
  • delete_sitemapno sensitive capability
  • find_cannibalizationno sensitive capability
  • find_content_gapsno sensitive capability
  • find_ctr_opportunitiesno sensitive capability
Show 17 more tools ↓
  • find_declining_contentno sensitive capability
  • find_new_queriesno sensitive capability
  • find_quick_winsno sensitive capability
  • find_what_to_build_nextno sensitive capability
  • get_performance_summaryno sensitive capability
  • get_property_detailsno sensitive capability
  • get_search_analyticsno sensitive capability
  • get_sitemap_detailsno sensitive capability
  • get_top_pagesno sensitive capability
  • get_top_queriesno sensitive capability
  • get_traffic_by_deviceno sensitive capability
  • inspect_urlno sensitive capability
  • list_propertiesno sensitive capability
  • list_sitemapsno sensitive capability
  • seo_health_checkno sensitive capability
  • submit_sitemapno sensitive capability
  • weekly_seo_reportno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.0.0 latest A 98/100 0 1.9.0 2026-07-24

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 98/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/awesome-gsc-mcp/badge.svg)](https://mcptrustchecker.com/registry/awesome-gsc-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/awesome-gsc-mcp"><img src="https://mcptrustchecker.com/registry/awesome-gsc-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/awesome-gsc-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan awesome-gsc-mcp --online

Use the free API → How scoring works

More in Developer Tools