MCP Probe Kit
Spec-driven dev workflow MCP for Cursor & AI agents — start_feature/bugfix orchestration, auto Skill+AGENTS bootstrap, memory, GitNexus. npx -y mcp-probe-kit@latest
Is MCP Probe Kit safe? Promising trust profile, but some evidence still deserves review.
Compare MCP Probe Kit
How does it stack up against its MCP Servers neighbours?
- Mnemoverse Memory +0.1 higher
- Federal Compass MCP +0.1 higher
- Screaming Frog SEO Spider MCP Server same score
In detail: MCP Probe Kit scores 68.8/100 (Grade B), ranked #357 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 4.2/10; recent commits are unsigned; last pushed 2026-09-23. Every point is earned from checkable signals — never paid placement. How scoring works →
How MCP Probe Kit compares in MCP Servers
- #211 Mnemoverse Memory 68.9 +0.1
- #212 Federal Compass MCP 68.9 +0.1
- #213 MCP Probe Kit 68.8 this agent
- #214 Screaming Frog SEO Spider MCP Server 68.8 ±0
- #215 Whoop MCP 68.7 −0.1
Bars show each HVTrust score; the tick marks MCP Probe Kit’s 68.8.
Where the 68.8 comes from
HVTrust dimensions vs the MCP Servers average
68.8 / 100 · 100.0% confidenceMCP Probe Kit MCP Servers average (775 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B 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 →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
49.9 / 100Supply Chain Trust
Common questions about MCP Probe Kit
Does MCP Probe Kit publish package provenance?
Does MCP Probe Kit have an OpenSSF Scorecard?
Is MCP Probe Kit actively maintained?
What license does MCP Probe Kit use?
Are MCP Probe Kit's commits signed?
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
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to MCP Probe Kit'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.
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
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/mcp-probe-kit)
<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
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