updated 2026-10-16 16:07 UTC

Vibe Check MCP Server

Repository Website

Vibe Check is a tool that provides mentor-like feedback to AI Agents, preventing tunnel-vision, over-engineering and reasoning lock-in for complex and long-horizon agent workflows. KISS your over-eager AI Agents goodbye! Effective for: Coding, Ambiguous Tasks, High-Risk tasks

MCP Servers TypeScript Listed MIT

Is Vibe Check MCP Server safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 4.5 / 10
Provenance None
Signed commits 73%
Last push 17d ago
Advisories None known
Compare Vibe Check MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Vibe Check MCP Server scores 55.7/100 (Grade C), ranked #814 of 1378 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 4.5/10; 73% of recent commits are signed; no published advisory affects its latest release (@pv-bhat/vibe-check-mcp); last pushed 2026-09-29. Every point is earned from checkable signals — never paid placement. How scoring works →

How Vibe Check MCP Server 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 Vibe Check MCP Server and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/PV-Bhat/vibe-check-mcp-server, MIT, last pushed 2026-09-29. 73% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

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

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

  3. Published packages Linked, not attested

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: @pv-bhat/vibe-check-mcp 2.7.6. No published advisory affects it (OSV, checked 2026-10-16).

Changes to this chain

  • 2026-08-30 OSSF Scorecard: 5.7/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

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

Verify this score yourself

Every build re-issues Vibe Check MCP Server’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 Vibe Check MCP Server compares in MCP Servers

  1. #437 Git MCP Server 56.0 +0.3
  2. #438 Greptimedb MCP Server 55.8 +0.1
  3. #439 Vibe Check MCP Server 55.7 this agent
  4. #440 Ref Tools MCP 55.7 ±0
  5. #441 JS Reverse MCP 55.6 −0.1

Bars show each HVTrust score; the tick marks Vibe Check MCP Server’s 55.7.

Where the 55.7 comes from

HVTrust dimensions vs the MCP Servers average

55.7 / 100 · 100.0% confidence

Vibe Check MCP Server MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
9.3 / 25
1.2 below avg 10.5
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.7 below avg 13.5
Transparency50% declared license · 50% OSSF Scorecard
12.3 / 17
in line with avg 12.3
Maintenance60% last-push freshness · 40% commit activity
10.9 / 20
1.4 below avg 12.3
AdoptionLog-scaled stars · package downloads
9.2 / 20
1.8 above avg 7.4

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-15
Rank Moved
Rank dropped 11 spots (#806 → #817)
2026-10-14
Rank Moved
Rank dropped 12 spots (#794 → #806)
2026-10-12
Rank Moved
Rank dropped 11 spots (#778 → #789)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.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.
Compare with another agent Get email alerts for Vibe Check MCP Server View MCP Servers Report missing data
47.5
Activity sub-score · out of 100
#439
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 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-10-16 16:07 UTC · Repo last pushed 17 days ago

Rank Trend

2026-09-29 2026-10-16

Activity & Reach

Stars
501
Forks
67
Last Push
2026-09-29
17 days ago
Commits (4 wk)
0
Downloads (7d)
102
npm
HN mentions (30d)
—
Open Issues
1
Rank Change
▲3
was #817

Analysis

Activity Inputs

47.5 / 100
StarsRepository reach
16.2 / 30
FreshnessLast push recency
22.6 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
8.5 / 20

Common questions about Vibe Check MCP Server

Vibe Check MCP Server 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 Vibe Check MCP Server publish package provenance?
No published build provenance is currently detected for Vibe Check MCP 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 Vibe Check MCP Server have an OpenSSF Scorecard?
Vibe Check MCP Server has an OpenSSF Scorecard score of 4.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 Vibe Check MCP Server actively maintained?
Maintained. Last push was 17 days ago.
What license does Vibe Check MCP Server use?
Vibe Check MCP Server ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Vibe Check MCP Server's commits signed?
73% of the last 100 commits to Vibe Check MCP 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
high confidence
Implemented
Vibe Check MCP Server appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
4 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.
  • shell
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 Vibe Check MCP Server'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 dependencies: Anthropic, Google Gemini, OpenAI, OpenRouter
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain Vibe Check MCP Server?

For maintainers

HVTrust scores Vibe Check MCP 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
Rank 31HVTrust 3Listed 2Score 2Grade 2Scorecard 1Delisted 1MCP 1Surface 1
2026-10-15
Rank Moved
Rank dropped 11 spots (#806 → #817)
2026-10-14
Rank Moved
Rank dropped 12 spots (#794 → #806)
2026-10-12
Rank Moved
Rank dropped 11 spots (#778 → #789)
2026-10-09
Rank Moved
Rank dropped 12 spots (#768 → #780)
2026-10-02
Rank Moved
Rank dropped 13 spots (#742 → #755)
2026-09-30
Rank Moved
Rank rose 38 spots (#779 → #741)
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, Google Gemini, OpenAI, OpenRouter
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 225 spots (#979 → #754)
2026-09-23
HVTrust Changed
HVTrust up 30.5pts (25.3 → 55.8)
2026-09-22
Newly Listed
First tracked at rank #979
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-19
Rank Moved
Rank dropped 32 spots (#700 → #732)
2026-09-19
Activity Score Changed
Activity score down 8pts (56 → 49)
2026-09-17
Rank Moved
Rank dropped 16 spots (#675 → #691)
2026-09-11
Rank Moved
Rank dropped 40 spots (#626 → #666)
2026-09-10
Rank Moved
Rank rose 12 spots (#638 → #626)
2026-09-09
Rank Moved
Rank dropped 24 spots (#614 → #638)
2026-09-08
Rank Moved
Rank dropped 11 spots (#603 → #614)
2026-09-07
Rank Moved
Rank dropped 56 spots (#547 → #603)
2026-09-05
Rank Moved
Rank dropped 97 spots (#441 → #538)
2026-09-04
Rank Moved
Rank dropped 11 spots (#430 → #441)
2026-09-03
Grade Changed
Trust grade D → C
2026-09-03
Rank Moved
Rank rose 564 spots (#994 → #430)
2026-09-03
HVTrust Changed
HVTrust up 21.7pts (39.1 → 60.8)
2026-09-02
Rank Moved
Rank dropped 45 spots (#949 → #994)
2026-09-01
Rank Moved
Rank dropped 39 spots (#910 → #949)
2026-08-31
Rank Moved
Rank dropped 31 spots (#879 → #910)
2026-08-30
Scorecard Added
OSSF Scorecard: 5.7/10
2026-08-30
Rank Moved
Rank rose 310 spots (#1189 → #879)
2026-08-30
HVTrust Changed
HVTrust up 19.1pts (20.1 → 39.2)
2026-08-29
Rank Moved
Rank dropped 22 spots (#1167 → #1189)
2026-08-28
Rank Moved
Rank dropped 19 spots (#1148 → #1167)
2026-08-27
Rank Moved
Rank dropped 23 spots (#1125 → #1148)
2026-08-26
Rank Moved
Rank dropped 55 spots (#1070 → #1125)
2026-08-24
Rank Moved
Rank dropped 21 spots (#1050 → #1071)
2026-08-20
Rank Moved
Rank rose 24 spots (#1086 → #1062)
2026-08-20
Activity Score Changed
Activity score up 6pts (54 → 60)
2026-08-16
Rank Moved
Rank dropped 32 spots (#1059 → #1091)
2026-08-13
Rank Moved
Rank dropped 10 spots (#1054 → #1064)
2026-08-12
Rank Moved
Rank rose 12 spots (#1066 → #1054)
2026-08-10
Rank Moved
Rank dropped 61 spots (#1000 → #1061)
2026-08-08
Newly Listed
First tracked at rank #995
GitHub → Website → npm: @pv-bhat/vibe-check-mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 55.7 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/vibe-check-mcp-server.svg)](https://hvtracker.net/agents/vibe-check-mcp-server)
HTML:
<a href="https://hvtracker.net/agents/vibe-check-mcp-server"><img src="https://hvtracker.net/badge/vibe-check-mcp-server.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.4 · Raw JSON