Google Surf MCP

Turn Google Search, Papers, and Codebases into an Automatic Local Knowledge Graph for AI Agents.

MCP Servers TypeScript Listed MIT

Is Google Surf MCP safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 3.8 / 10
Provenance None
Signed commits 32%
Last push 17d ago
Compare Google Surf MCP
Suggest a correction

In detail: Google Surf MCP scores 59.1/100 (Grade C), ranked #655 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.8/10; 32% of recent commits are signed; last pushed 2026-09-10. Every point is earned from checkable signals — never paid placement. How scoring works →

How Google Surf MCP compares in MCP Servers

  1. #361 MCP Imagenate 59.2 +0.1
  2. #362 Drawio MCP 59.1 ±0
  3. #363 Google Surf MCP 59.1 this agent
  4. #364 MCP Klever Vm 59.1 ±0
  5. #365 JS Reverse MCP 59.0 −0.1

Bars show each HVTrust score; the tick marks Google Surf MCP’s 59.1.

Where the 59.1 comes from

HVTrust dimensions vs the MCP Servers average

59.1 / 100 · 100.0% confidence

Google Surf MCP MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
6.3 / 25
4.0 below avg 10.3
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.6 below avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
11.7 / 17
0.5 below avg 12.2
Maintenance60% last-push freshness · 40% commit activity
16.0 / 20
4.0 above avg 12.0
AdoptionLog-scaled stars · package downloads
9.6 / 20
2.4 above avg 7.2

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → C
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.8/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
60.7
Activity sub-score · out of 100
#363

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 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 →

Signals refreshed 2026-09-27 00:32 UTC · Repo last pushed 17 days ago

Rank Trend

2026-08-11 2026-09-27

Activity & Reach

Stars
290
Forks
34
Last Push
2026-09-10
17 days ago
Commits (4 wk)
18
Downloads (7d)
548
npm
HN mentions (30d)
—
Open Issues
0
Rank Change
▲4
was #659

Analysis

Activity Inputs

60.7 / 100
StarsRepository reach
14.8 / 30
FreshnessLast push recency
22.6 / 25
ActivityRecent commits
15.9 / 25
CommunityFork signal
7.2 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
3.8 / 10
OpenSSF Scorecard · scanned Sep 25, 2026
Signed Commits
32%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests 0
CII-Best-Practices 0
Code-Review 0
Contributors 3
Dangerous-Workflow 10
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 10
Packaging -1
Pinned-Dependencies 3
SAST 0
Security-Policy 0
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 7

Common questions about Google Surf MCP

Google Surf MCP has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does Google Surf MCP publish package provenance?
No published build provenance is currently detected for Google Surf MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Google Surf MCP have an OpenSSF Scorecard?
Google Surf MCP has an OpenSSF Scorecard score of 3.8/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 Google Surf MCP actively maintained?
Maintained. Last push was 17 days ago.
What license does Google Surf MCP use?
Google Surf MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Google Surf MCP's commits signed?
32% of the last 100 commits to Google Surf 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
Google Surf MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
1 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
1 tags
Broad capability areas detected.
  • browser
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
How this surface has changed

Detected changes to Google Surf 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.

2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain Google Surf MCP?

For maintainers

HVTrust scores Google Surf 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 24HVTrust 3Listed 2Score 2Grade 2Scorecard 1Delisted 1MCP 1Surface 1
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank rose 214 spots (#851 → #637)
2026-09-23
HVTrust Changed
HVTrust up 32.0pts (27.8 → 59.8)
2026-09-22
Newly Listed
First tracked at rank #851
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-20
Rank Moved
Rank dropped 28 spots (#592 → #620)
2026-09-19
Rank Moved
Rank rose 12 spots (#604 → #592)
2026-09-13
Rank Moved
Rank dropped 10 spots (#570 → #580)
2026-09-12
Rank Moved
Rank dropped 16 spots (#554 → #570)
2026-09-11
Rank Moved
Rank dropped 24 spots (#530 → #554)
2026-09-10
Rank Moved
Rank rose 14 spots (#544 → #530)
2026-09-07
Rank Moved
Rank dropped 38 spots (#493 → #531)
2026-09-06
Rank Moved
Rank dropped 10 spots (#483 → #493)
2026-09-05
Rank Moved
Rank dropped 70 spots (#413 → #483)
2026-09-04
Rank Moved
Rank dropped 21 spots (#392 → #413)
2026-09-03
Rank Moved
Rank dropped 10 spots (#382 → #392)
2026-09-02
Grade Changed
Trust grade D → C
2026-09-02
Rank Moved
Rank rose 587 spots (#969 → #382)
2026-09-02
HVTrust Changed
HVTrust up 23.5pts (38.2 → 61.7)
2026-09-01
Scorecard Added
OSSF Scorecard: 4.0/10
2026-09-01
Rank Moved
Rank rose 239 spots (#1208 → #969)
2026-09-01
HVTrust Changed
HVTrust up 16.7pts (21.5 → 38.2)
2026-08-31
Rank Moved
Rank dropped 26 spots (#1182 → #1208)
2026-08-30
Rank Moved
Rank dropped 27 spots (#1155 → #1182)
2026-08-29
Rank Moved
Rank dropped 28 spots (#1127 → #1155)
2026-08-28
Rank Moved
Rank dropped 24 spots (#1103 → #1127)
2026-08-27
Rank Moved
Rank dropped 12 spots (#1091 → #1103)
2026-08-26
Rank Moved
Rank dropped 41 spots (#1050 → #1091)
2026-08-26
Activity Score Changed
Activity score up 7pts (51 → 58)
2026-08-17
Rank Moved
Rank rose 13 spots (#1051 → #1038)
2026-08-16
Rank Moved
Rank dropped 32 spots (#1019 → #1051)
2026-08-12
Rank Moved
Rank rose 12 spots (#1022 → #1010)
2026-08-10
Rank Moved
Rank dropped 56 spots (#975 → #1031)
2026-08-09
Activity Score Changed
Activity score down 5pts (55 → 50)
2026-08-08
Newly Listed
First tracked at rank #949

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 59.1 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/google-surf-mcp.svg)](https://hvtracker.net/agents/google-surf-mcp)
HTML:
<a href="https://hvtracker.net/agents/google-surf-mcp"><img src="https://hvtracker.net/badge/google-surf-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