Search Console MCP

Search & analytics data as infrastructure — MCP server for Google Search Console, Bing Webmaster Tools, Google Adsense a

MCP Servers TypeScript Grade C Listed MIT
50.4/100
Rank #765 of 1320
Compare Search Console MCP

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-09-02 · 2d ago
Recent change
Rank +9

Is Search Console MCP safe? Search Console MCP scores 50.4/100 (Grade C), ranked #765 of 1320 tracked open-source AI agent projects, on evidence coverage C (2 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 →

Ranked neighbours in MCP Servers

Quick Trust Read

What Would Improve It
Increase the share of verified signed commits for clearer maintainer identity.
Recent Changes
2026-09-04
Rank Moved
Rank dropped 21 spots (#744 → #765)
2026-09-03
Grade Changed
Trust grade B → C
2026-09-03
Rank Moved
Rank dropped 627 spots (#117 → #744)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.6/10. Tighten the weakest checks to improve public safety evidence.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
61.2
Activity sub-score · out of 100
#397

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-09-04 22:15 UTC · Repo last pushed 2 days ago

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars
287
Forks
27
Last Push
2026-09-02
2 days ago
Commits (4 wk)
15
Downloads (7d)
HN mentions (30d)
Open Issues
0
Rank Change
▼21
was #744

Analysis

HVTrust Dimensions vs MCP Servers

50.4 / 100 · 67.0% confidence

Search Console MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
15.1 / 25
5.5 above avg 9.6
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.6 above avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
12.4 / 17
0.6 above avg 11.8
Maintenance60% last-push freshness · 40% commit activity
16.7 / 20
4.5 above avg 12.2
AdoptionLog-scaled stars · package downloads
5.9 / 20
in line with avg 6.3

Activity Inputs

61.2 / 100
StarsRepository reach
14.8 / 30
FreshnessLast push recency
24.7 / 25
ActivityRecent commits
15.0 / 25
CommunityFork signal
6.7 / 20

Supply Chain Trust

Package Provenance
Verified
npm attestation
OSSF Scorecard
4.6 / 10
OpenSSF Scorecard · scanned Sep 1, 2026
Signed Commits
37%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 3
CI-Tests 7
CII-Best-Practices 0
Code-Review 0
Contributors 0
Dangerous-Workflow 10
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 0
SAST 0
Security-Policy 10
Signed-Releases 0
Token-Permissions 9
Vulnerabilities 0

Is Search Console MCP safe?

Public trust evidence for Search Console MCP is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does Search Console MCP publish package provenance?
Yes. Search Console MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Search Console MCP have an OpenSSF Scorecard?
Search Console MCP has an OpenSSF Scorecard score of 4.6/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Search Console MCP actively maintained?
Actively maintained. The repository was pushed to within the last 2 day(s).
What license does Search Console MCP use?
Search Console MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Search Console MCP's commits signed?
37% of the last 100 commits to Search Console MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

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
Scored in HVTrust

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 Server Support
high confidence
Implemented
Search Console MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
low confidence
None detected
No clear third-party provider dependency detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

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
Rank 12HVTrust 2Listed 1Score 1Scorecard 1Grade 1
2026-09-04
Rank Moved
Rank dropped 21 spots (#744 → #765)
2026-09-03
Grade Changed
Trust grade B → C
2026-09-03
Rank Moved
Rank dropped 627 spots (#117 → #744)
2026-09-03
HVTrust Changed
HVTrust down 27.3pts (77.7 → 50.4)
2026-09-01
Scorecard Added
OSSF Scorecard: 4.6/10
2026-09-01
Rank Moved
Rank rose 121 spots (#242 → #121)
2026-09-01
HVTrust Changed
HVTrust up 9.6pts (67.4 → 77.0)
2026-08-31
Rank Moved
Rank dropped 50 spots (#192 → #242)
2026-08-31
Activity Score Changed
Activity score down 5pts (65 → 60)
2026-08-29
Rank Moved
Rank dropped 10 spots (#183 → #193)
2026-08-26
Rank Moved
Rank dropped 17 spots (#158 → #175)
2026-08-24
Rank Moved
Rank dropped 11 spots (#149 → #160)
2026-08-21
Rank Moved
Rank rose 15 spots (#173 → #158)
2026-08-19
Rank Moved
Rank dropped 13 spots (#158 → #171)
2026-08-17
Rank Moved
Rank rose 13 spots (#167 → #154)
2026-08-13
Rank Moved
Rank dropped 14 spots (#141 → #155)
2026-08-10
Rank Moved
Rank dropped 12 spots (#136 → #148)
2026-08-08
Newly Listed
First tracked at rank #141

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 50.4 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/search-console-mcp.svg)](https://hvtracker.net/agents/search-console-mcp)
HTML:
<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

Data sources
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