Is MCP Language Server safe to use?

MCP Language Server has an HVTrust score of 35.1/100 (Grade D), ranked #1240 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for MCP Language Server?

MCP Language Server scores 35.1/100 on HVTracker's evidence-weighted HVTrust scale. It has 1.6k GitHub stars and is categorized under MCP Servers.

MCP Language Server

isaacphi/mcp-language-server

mcp-language-server gives MCP enabled clients access semantic tools like get definition, references, rename, and diagnostics.

MCP Servers Go Listed BSD-3-Clause

Is MCP Language Server safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 3.5 / 10

Provenance None

Signed commits 15%

Last push 209d ago

Compare MCP Language Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: MCP Language Server scores 35.1/100 (Grade D), ranked #1240 of 1325 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.5/10; 15% of recent commits are signed; last pushed 2026-03-01. Every point is earned from checkable signals — never paid placement. How scoring works →

How MCP Language Server compares in MCP Servers

#738 Pcb MCP 35.3 +0.2
#739 Obsidian Vault MCP Server 35.2 +0.1
#740 MCP Language Server 35.1 this agent
#741 MCP Skills Server 35.1 ±0
#742 DevDocs 35.1 ±0

Bars show each HVTrust score; the tick marks MCP Language Server’s 35.1.

Where the 35.1 comes from

HVTrust dimensions vs the MCP Servers average

35.1 / 100 · 100.0% confidence

MCP Language Server MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

5.1 / 25

5.2 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.5 / 17

0.7 below avg 12.2

Maintenance60% last-push freshness · 40% commit activity

0 / 20

12.1 below avg 12.1

AdoptionLog-scaled stars · package downloads

7.7 / 20

in line with 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

Rank Moved

Rank dropped 294 spots (#945 → #1239)

2026-09-23

HVTrust Changed

HVTrust up 9.2pts (25.9 → 35.1)

2026-09-22

Newly Listed

First tracked at rank #945

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 3.5/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 209 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent Get email alerts for MCP Language Server View MCP Servers Report missing data

29.3

Activity sub-score · out of 100

#740

In MCP Servers

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 →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

1.6k

Forks

150

Last Push

2026-03-01

209 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▲1

was #1241

Analysis

Activity Inputs

29.3 / 100

StarsRepository reach

19.2 / 30

FreshnessLast push recency

0.0 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

10.1 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

3.5 / 10

OpenSSF Scorecard · scanned Sep 17, 2026

Signed Commits

15%

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 10

Fuzzing 0

License 10

Maintained 0

Packaging -1

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 6

Common questions about MCP Language Server

Public trust evidence for MCP Language Server 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 MCP Language Server publish package provenance?

No published build provenance is currently detected for MCP Language Server. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does MCP Language Server have an OpenSSF Scorecard?

MCP Language Server has an OpenSSF Scorecard score of 3.5/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 MCP Language Server actively maintained?

Stale. The repository has not been pushed to in 209 days. Consider whether the project is still being maintained.

What license does MCP Language Server use?

MCP Language Server ships under BSD-3-Clause. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are MCP Language Server's commits signed?

15% of the last 100 commits to MCP Language Server 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

None detected

No MCP server signal detected.

Detailed evidence is not shown in the public view.

External Service Dependencies

None detected

No clear third-party provider dependency detected.

Credential signal: No explicit API-key/config marker detected.

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

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 MCP Language Server?

For maintainers

HVTrust scores MCP Language Server 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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-09-23

Rank Moved

Rank dropped 294 spots (#945 → #1239)

2026-09-23

HVTrust Changed

HVTrust up 9.2pts (25.9 → 35.1)

2026-09-22

Newly Listed

First tracked at rank #945

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-08

Rank Moved

Rank dropped 14 spots (#1205 → #1219)

2026-09-07

Rank Moved

Rank dropped 16 spots (#1189 → #1205)

2026-09-06

Rank Moved

Rank dropped 15 spots (#1174 → #1189)

2026-09-05

Rank Moved

Rank dropped 31 spots (#1143 → #1174)

2026-09-04

Rank Moved

Rank dropped 14 spots (#1129 → #1143)

2026-09-03

Rank Moved

Rank dropped 48 spots (#1081 → #1129)

2026-09-02

Rank Moved

Rank dropped 45 spots (#1036 → #1081)

2026-09-01

Rank Moved

Rank dropped 38 spots (#998 → #1036)

2026-08-31

Rank Moved

Rank dropped 30 spots (#968 → #998)

2026-08-30

Rank Moved

Rank dropped 48 spots (#920 → #968)

2026-08-29

Rank Moved

Rank dropped 50 spots (#870 → #920)

2026-08-28

Rank Moved

Rank dropped 31 spots (#839 → #870)

2026-08-27

Rank Moved

Rank dropped 23 spots (#816 → #839)

2026-08-26

Scorecard Added

OSSF Scorecard: 3.5/10

2026-08-26

Rank Moved

Rank rose 464 spots (#1280 → #816)

2026-08-26

HVTrust Changed

HVTrust up 21.2pts (14.0 → 35.2)

2026-08-16

Rank Moved

Rank dropped 26 spots (#1252 → #1278)

2026-08-10

Newly Listed

First tracked at rank #1249

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/mcp-language-server.svg)](https://hvtracker.net/agents/mcp-language-server)
            
HTML:
            <a href="https://hvtracker.net/agents/mcp-language-server"><img src="https://hvtracker.net/badge/mcp-language-server.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