MCP Probe Kit

Spec-driven dev workflow MCP for Cursor & AI agents — start_feature/bugfix orchestration, auto Skill+AGENTS bootstrap, m

MCP Servers TypeScript Grade C Listed MIT
54.2/100
Rank #779 of 1328
Compare MCP Probe Kit

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade B · 3/5 signals
Last push
2026-08-20 · 19d ago
Recent change
Rank +9

Is MCP Probe Kit safe? MCP Probe Kit scores 54.2/100 (Grade C), ranked #779 of 1328 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.2/10; recent commits are unsigned; last pushed 2026-08-20. 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 12 spots (#767 → #779)
2026-09-07
Rank Moved
Rank dropped 52 spots (#715 → #767)
2026-09-05
Rank Moved
Rank dropped 81 spots (#625 → #706)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.2/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.
45.6
Activity sub-score · out of 100
#426

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-08 15:33 UTC · Repo last pushed 19 days ago

Rank Trend

2026-08-11 2026-09-08

Activity & Reach

Stars
36
Forks
4
Last Push
2026-08-20
19 days ago
Commits (4 wk)
6
Downloads (7d)
214
npm
HN mentions (30d)
Open Issues
0
Rank Change
▼12
was #767

Analysis

HVTrust Dimensions vs MCP Servers

54.2 / 100 · 100.0% confidence

MCP Probe Kit MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.3 / 25
4.6 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
12.1 / 17
in line with avg 12.0
Maintenance60% last-push freshness · 40% commit activity
14.1 / 20
1.9 above avg 12.2
AdoptionLog-scaled stars · package downloads
6.9 / 20
in line with avg 6.9

Activity Inputs

45.6 / 100
StarsRepository reach
9.4 / 30
FreshnessLast push recency
22.4 / 25
ActivityRecent commits
10.5 / 25
CommunityFork signal
3.3 / 20

Supply Chain Trust

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

Is MCP Probe Kit safe?

Public trust evidence for MCP Probe Kit 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 Probe Kit publish package provenance?
No published build provenance is currently detected for MCP Probe Kit. 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 Probe Kit have an OpenSSF Scorecard?
MCP Probe Kit has an OpenSSF Scorecard score of 4.2/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 Probe Kit actively maintained?
Maintained. Last push was 19 days ago.
What license does MCP Probe Kit use?
MCP Probe Kit ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are MCP Probe Kit's commits signed?
0% of the last 100 commits to MCP Probe Kit 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 Probe Kit 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
None detected
No clear plugin system or broad tool surface detected.
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

Maintain MCP Probe Kit?

For maintainers

HVTrust scores MCP Probe Kit 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 18Score 3HVTrust 2Listed 1Scorecard 1Grade 1
2026-09-08
Rank Moved
Rank dropped 12 spots (#767 → #779)
2026-09-07
Rank Moved
Rank dropped 52 spots (#715 → #767)
2026-09-05
Rank Moved
Rank dropped 81 spots (#625 → #706)
2026-09-04
Grade Changed
Trust grade D → C
2026-09-04
Rank Moved
Rank rose 483 spots (#1108 → #625)
2026-09-04
HVTrust Changed
HVTrust up 18.7pts (36.1 → 54.8)
2026-09-03
Rank Moved
Rank dropped 46 spots (#1062 → #1108)
2026-09-03
Activity Score Changed
Activity score down 8pts (54 → 46)
2026-09-02
Rank Moved
Rank dropped 50 spots (#1012 → #1062)
2026-09-01
Rank Moved
Rank dropped 43 spots (#969 → #1012)
2026-08-31
Rank Moved
Rank dropped 32 spots (#937 → #969)
2026-08-30
Scorecard Added
OSSF Scorecard: 4.4/10
2026-08-30
Rank Moved
Rank rose 249 spots (#1186 → #937)
2026-08-30
HVTrust Changed
HVTrust up 16.1pts (20.2 → 36.3)
2026-08-29
Rank Moved
Rank dropped 27 spots (#1159 → #1186)
2026-08-28
Rank Moved
Rank dropped 21 spots (#1138 → #1159)
2026-08-27
Rank Moved
Rank dropped 19 spots (#1119 → #1138)
2026-08-26
Rank Moved
Rank dropped 62 spots (#1057 → #1119)
2026-08-17
Rank Moved
Rank rose 10 spots (#1074 → #1064)
2026-08-16
Rank Moved
Rank dropped 34 spots (#1040 → #1074)
2026-08-13
Rank Moved
Rank dropped 11 spots (#1034 → #1045)
2026-08-12
Rank Moved
Rank rose 15 spots (#1049 → #1034)
2026-08-11
Activity Score Changed
Activity score up 21pts (41 → 61)
2026-08-10
Rank Moved
Rank dropped 69 spots (#1050 → #1119)
2026-08-09
Activity Score Changed
Activity score down 6pts (47 → 41)
2026-08-08
Newly Listed
First tracked at rank #1031

Embed Badge Badge guide for maintainers →

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