Gopls MCP

MCP server for golang projects development: Expand AI Code Agent ability boundary to have a semantic understanding and d

MCP Servers Go Grade D Listed BSD-3-Clause
41.9/100
Rank #1104 of 1328
Compare Gopls 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-07-21 · 49d ago
Recent change
Rank +9

Is Gopls MCP safe? Gopls MCP scores 41.9/100 (Grade D), ranked #1104 of 1328 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.6/10; 9% of recent commits are signed; last pushed 2026-07-21. 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
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-08
Rank Moved
Rank dropped 15 spots (#1089 → #1104)
2026-09-07
Rank Moved
Rank dropped 29 spots (#1060 → #1089)
2026-09-06
Rank Moved
Rank dropped 15 spots (#1045 → #1060)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.6/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.
Refresh maintenance signals The repo was last pushed 49 days ago. Fresh activity helps separate stable projects from stale ones.
32.7
Activity sub-score · out of 100
#649

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D 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-08 15:33 UTC · Repo last pushed 49 days ago

Rank Trend

2026-08-11 2026-09-08

Activity & Reach

Stars
57
Forks
6
Last Push
2026-07-21
49 days ago
Commits (4 wk)
0
Downloads (7d)
HN mentions (30d)
Open Issues
3
Rank Change
▼15
was #1089

Analysis

HVTrust Dimensions vs MCP Servers

41.9 / 100 · 100.0% confidence

Gopls MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
4.9 / 25
5.0 below avg 9.9
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.6 below avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
11.6 / 17
in line with avg 12.0
Maintenance60% last-push freshness · 40% commit activity
8.7 / 20
3.5 below avg 12.2
AdoptionLog-scaled stars · package downloads
4.2 / 20
2.7 below avg 6.9

Activity Inputs

32.7 / 100
StarsRepository reach
10.6 / 30
FreshnessLast push recency
18.2 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
3.9 / 20

Supply Chain Trust

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

Is Gopls MCP safe?

Public trust evidence for Gopls 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 Gopls MCP publish package provenance?
No published build provenance is currently detected for Gopls 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 Gopls MCP have an OpenSSF Scorecard?
Gopls MCP has an OpenSSF Scorecard score of 3.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 Gopls MCP actively maintained?
Slowing down. Last push was 49 days ago — keep an eye on whether activity resumes.
What license does Gopls MCP use?
Gopls MCP ships under BSD-3-Clause. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Gopls MCP's commits signed?
9% of the last 100 commits to Gopls 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
medium confidence
Implemented
Gopls MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
medium confidence
1 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain Gopls MCP?

For maintainers

HVTrust scores Gopls 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 16Listed 1HVTrust 1Scorecard 1
2026-09-08
Rank Moved
Rank dropped 15 spots (#1089 → #1104)
2026-09-07
Rank Moved
Rank dropped 29 spots (#1060 → #1089)
2026-09-06
Rank Moved
Rank dropped 15 spots (#1045 → #1060)
2026-09-05
Rank Moved
Rank dropped 39 spots (#1006 → #1045)
2026-09-04
Rank Moved
Rank dropped 27 spots (#979 → #1006)
2026-09-03
Rank Moved
Rank dropped 58 spots (#921 → #979)
2026-09-02
Scorecard Added
OSSF Scorecard: 3.6/10
2026-09-02
Rank Moved
Rank rose 356 spots (#1277 → #921)
2026-09-02
HVTrust Changed
HVTrust up 24.0pts (18.3 → 42.3)
2026-09-01
Rank Moved
Rank dropped 11 spots (#1266 → #1277)
2026-08-30
Rank Moved
Rank dropped 16 spots (#1241 → #1257)
2026-08-29
Rank Moved
Rank dropped 17 spots (#1224 → #1241)
2026-08-28
Rank Moved
Rank dropped 13 spots (#1211 → #1224)
2026-08-27
Rank Moved
Rank dropped 14 spots (#1197 → #1211)
2026-08-26
Rank Moved
Rank dropped 43 spots (#1154 → #1197)
2026-08-24
Rank Moved
Rank dropped 15 spots (#1141 → #1156)
2026-08-16
Rank Moved
Rank dropped 24 spots (#1122 → #1146)
2026-08-10
Rank Moved
Rank dropped 64 spots (#1052 → #1116)
2026-08-08
Newly Listed
First tracked at rank #1047

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 41.9 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/gopls-mcp.svg)](https://hvtracker.net/agents/gopls-mcp)
HTML:
<a href="https://hvtracker.net/agents/gopls-mcp"><img src="https://hvtracker.net/badge/gopls-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON