updated 2026-11-10 04:07 UTC

MCP Hub for Neovim

Repository Website by ravitemer

An MCP client for Neovim that seamlessly integrates MCP servers into your editing workflow with an intuitive interface for managing, testing, and using MCP servers with your favorite chat plugins.

Protocols & Tool Integration Lua Listed MIT

Is MCP Hub for Neovim safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 3.1 / 10
Provenance None
Signed commits 22%
Last push 296d ago
Compare MCP Hub for Neovim

How does it stack up against its Protocols & Tool Integration neighbours?

Pick any agent to compare →
Suggest a correction

In detail: MCP Hub for Neovim scores 36.1/100 (Grade D), ranked #1275 of 1374 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.1/10; 22% of recent commits are signed; last pushed 2026-01-18. Every point is earned from checkable signals — never paid placement. How scoring works →

How MCP Hub for Neovim could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships MCP Hub for Neovim and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/ravitemer/mcphub.nvim, MIT, last pushed 2026-01-18. 22% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 3.1/10 (scanned Oct 31, 2026). The checks that decide who can get a change released:

    • Code Review3
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies1
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 4
    CII-Best-Practices 0
    Code-Review 3
    Contributors 0
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 0
    Packaging -1
    Pinned-Dependencies 1
    SAST 0
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages None

    No registry package. MCP Hub for Neovim is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

  • 2026-09-08 OSSF Scorecard: 3.2/10

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads (missing)
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues MCP Hub for Neovim’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How MCP Hub for Neovim compares in Protocols & Tool Integration

  1. #58 MCP Playwright 36.9 +0.8
  2. #59 CrewAI tools 36.1 ±0
  3. #60 MCP Hub for Neovim 36.1 this agent
  4. #61 TUUI 33.9 −2.2
  5. #62 Scira MCP Chat 30.7 −5.4

Bars show each HVTrust score; the tick marks MCP Hub for Neovim’s 36.1.

Where the 36.1 comes from

HVTrust dimensions vs the Protocols & Tool Integration average

36.1 / 100 · 100.0% confidence

MCP Hub for Neovim Protocols & Tool Integration average (63 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.0 / 25
6.2 below avg 11.2
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.3 below avg 12.1
Transparency50% declared license · 50% OSSF Scorecard
11.1 / 17
1.9 below avg 13.0
Maintenance60% last-push freshness · 40% commit activity
0 / 20
14.6 below avg 14.6
AdoptionLog-scaled stars · package downloads
7.8 / 20
3.3 below avg 11.1

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.1/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 296 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent
View Protocols & Tool Integration Report missing data
28.8
Activity sub-score · out of 100
#60
In Protocols & Tool Integration

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-11-10 04:07 UTC · Repo last pushed 296 days ago — may be stale

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
1.8k
Forks
98
Last Push
2026-01-18
296 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
18
Rank Change
=
was #1275

Analysis

Activity Inputs

28.8 / 100
StarsRepository reach
19.5 / 30
FreshnessLast push recency
0.0 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
9.3 / 20

Common questions about MCP Hub for Neovim

Public trust evidence for MCP Hub for Neovim 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 Hub for Neovim publish package provenance?
No published build provenance is currently detected for MCP Hub for Neovim. 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 Hub for Neovim have an OpenSSF Scorecard?
MCP Hub for Neovim has an OpenSSF Scorecard score of 3.1/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 Hub for Neovim actively maintained?
Stale. The repository has not been pushed to in 296 days. Consider whether the project is still being maintained.
What license does MCP Hub for Neovim use?
MCP Hub for Neovim ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are MCP Hub for Neovim's commits signed?
22% of the last 100 commits to MCP Hub for Neovim 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
MCP Hub for Neovim appears to expose MCP server capabilities.
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
high confidence
Extensions
Extension based 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
How this surface has changed

Detected changes to MCP Hub for Neovim'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
Tool Surface Changed
Detected tool/plugin surface changed: none → extension-based
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-03
Tool Surface Changed
Detected tool/plugin surface changed: marketplace → extension-based

Maintain MCP Hub for Neovim?

For maintainers

HVTrust scores MCP Hub for Neovim 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
Rank 6Surface 2HVTrust 2Scorecard 1Delisted 1Listed 1MCP 1
2026-10-09
Rank Moved
Rank dropped 13 spots (#1243 → #1256)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → extension-based
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank dropped 234 spots (#990 → #1224)
2026-09-23
HVTrust Changed
HVTrust up 11.0pts (25.1 → 36.1)
2026-09-22
Newly Listed
First tracked at rank #990
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-09
Rank Moved
Rank dropped 10 spots (#1200 → #1210)
2026-09-08
Scorecard Added
OSSF Scorecard: 3.2/10
2026-09-08
Rank Moved
Rank rose 119 spots (#1319 → #1200)
2026-09-08
HVTrust Changed
HVTrust up 20.8pts (15.5 → 36.3)
2026-09-03
Tool Surface Changed
Detected tool/plugin surface changed: marketplace → extension-based
2026-08-26
Rank Moved
Rank dropped 18 spots (#1262 → #1280)
2026-08-16
Rank Moved
Rank dropped 26 spots (#1240 → #1266)
GitHub → Website →

Embed Badge Badge guide for maintainers →

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

Other agents in Protocols & Tool Integration

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.4 · Raw JSON