Back to MCP Trust Indexm8ven
58
/ 100
1 month ago
github_topic

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

→ mybolide/mcp-probe-kit· listed on github_topic
Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find.

Install from

GitHub

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
🚨
Known vulnerabilities in dependencies: 1 critical, 4 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 3 credentials: MCP_TRACE_META_KEY, MEMORY_EMBEDDING_API_KEY, MEMORY_QDRANT_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies1 critical4 high1 medium

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

criticalvitest@4.0.18GHSA-5xrq-8626-4rwp

When Vitest UI server is listening, arbitrary file can be read and executed

hightar@7.5.6GHSA-34x7-hfp2-rc4v

node-tar Vulnerable to Arbitrary File Creation/Overwrite via Hardlink Path Traversal

hightar@7.5.6GHSA-83g3-92jg-28cx

Arbitrary File Read/Write via Hardlink Target Escape Through Symlink Chain in node-tar Extraction

hightar@7.5.6GHSA-9ppj-qmqm-q256

node-tar Symlink Path Traversal via Drive-Relative Linkpath

hightar@7.5.6GHSA-qffp-2rhf-9h96

tar has Hardlink Path Traversal via Drive-Relative Linkpath

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// required environment variables
This server reads these from process.env. You'll be asked to provide them before it can run.
configMCP_DISABLE_AUTO_TASK
configMCP_ENABLE_GITNEXUS_BRIDGE
configMCP_GITNEXUS_REPO
configMCP_GRAPH_SNAPSHOT_DIR— Graph snapshots are persisted to .mcp-probe-kit/graph-snapshots (customizable via )
configMCP_INCLUDE_OUTPUT_SCHEMA— What we do (v3.6.3+): tools/list omits outputSchema by default (~50 KB → ~23 KB). Structured output still works via structuredContent on tools/call. To restore full schemas: =1.
configMCP_PROJECT_RESOURCE_MAX_BYTES
configMCP_SKILLS_ROOTS
configMCP_TOOLSET
🔐 secretMCP_TRACE_META_KEY
🔐 secretMEMORY_EMBEDDING_API_KEY— "": "your-infinity-api-key",
configMEMORY_EMBEDDING_MODEL— Memory write is enabled only when MEMORY_QDRANT_URL, MEMORY_EMBEDDING_URL, and are all configured
configMEMORY_EMBEDDING_PROVIDER— (ollama by default)
configMEMORY_EMBEDDING_URL— Memory write is enabled only when MEMORY_QDRANT_URL, , and MEMORY_EMBEDDING_MODEL are all configured
🔐 secretMEMORY_QDRANT_API_KEY— "": "your-qdrant-api-key",
configMEMORY_QDRANT_COLLECTION— (default: mcp_probe_memory)
configMEMORY_QDRANT_URL— Read-only memory access only requires
configMEMORY_REPO_ID— (optional; show sourcePath only when sourceProject matches)
configVERIFY_MEMORY_ASSET_ID
configVERIFY_MEMORY_CRUD
configVERIFY_MEMORY_QUERY
configWORKSPACE_FOLDER_PATHS
// full audit trail
The full breakdown of what we checked, the deductions that landed, the network hosts, the dependency advisories, and concrete fix guidance is available to verified publishers.
// improvement guidance — verified publishers only
We have 2 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/mybolide-mcp-probe-kit-1n017u)](https://m8ven.ai/mcp/mybolide-mcp-probe-kit-1n017u)
commit: de8eafa65d1a1f362f96eb508642fd19c74971a6
code hash: bcbd5fcc020c34f58ddec988345f01df798c193d24f2a1433b87f104993c66e7
verified: 6/25/2026, 9:52:35 AM
view raw JSON →