Search Console MCP
Search & analytics data as infrastructure — MCP server for Google Search Console, Bing Webmaster Tools, Google Adsense and GA4, designed for AI agents and automation.
Is Search Console MCP safe? Promising trust profile, but some evidence still deserves review.
Compare Search Console MCP
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: Search Console MCP scores 73.8/100 (Grade B), ranked #248 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 4.6/10; 37% of recent commits are signed; last pushed 2026-09-02. Every point is earned from checkable signals — never paid placement. How scoring works →
How Search Console MCP compares in MCP Servers
- #146 Yantrikdb MCP 73.9 +0.1
- #147 Freshcontext MCP 73.9 +0.1
- #148 Search Console MCP 73.8 this agent
- #149 Storybook MCP Addon 73.5 −0.3
- #150 Marlinjai Email MCP 73.5 −0.3
Bars show each HVTrust score; the tick marks Search Console MCP’s 73.8.
Where the 73.8 comes from
HVTrust dimensions vs the MCP Servers average
73.8 / 100 · 100.0% confidenceSearch Console MCP MCP Servers average (775 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
53.1 / 100Supply Chain Trust
Common questions about Search Console MCP
Does Search Console MCP publish package provenance?
Does Search Console MCP have an OpenSSF Scorecard?
Is Search Console MCP actively maintained?
What license does Search Console MCP use?
Are Search Console MCP's commits signed?
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
AI agent surface
MCP, providers, tool surface
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Search Console MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.
Maintain Search Console MCP?
For maintainers
HVTrust scores Search Console MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/search-console-mcp)
<a href="https://hvtracker.net/agents/search-console-mcp"><img src="https://hvtracker.net/badge/search-console-mcp.svg" alt="HVTrust"></a>
Other agents in MCP Servers
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON