Vouch Kb MCP Server

vouch-kb PyPI v1.5.0

Published by plind-junior — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

Git-native, review-gated knowledge base for LLM agents. MCP server + CLI.

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 93/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 13

high Tool "kb_eval_embeddings" exposes command/code executionMTC-CAP-001

Tool "kb_eval_embeddings" appears to run shell commands or evaluate code (keyword "eval" in tool name). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.

Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.

Location: tool kb_eval_embeddings

high Shell/command execution in server code (adapters/openclaw/vouch-context-engine.mjs)MTC-SRC-002

In the server's implementation (`adapters/openclaw/vouch-context-engine.mjs:19`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: spawnSync } from 'node:child_process'; export const ENGINE_ID = 'vouch'; export const ENGINE_NAME = 'Vouch Context Eng

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server adapters/openclaw/vouch-context-engine.mjs

high Shell/command execution in server code (src/vouch/auto_pr.py)MTC-SRC-002

In the server's implementation (`src/vouch/auto_pr.py:100`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: try: proc = subprocess.run( argv, cwd=cwd, input=stdin, capture_output=True, text=True,

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server src/vouch/auto_pr.py

high Shell/command execution in server code (src/vouch/capture.py)MTC-SRC-002

In the server's implementation (`src/vouch/capture.py:198`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: try: names = subprocess.run( ["git", "diff", "--name-only", "HEAD"], cwd=cwd, capture

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server src/vouch/capture.py

high Shell/command execution in server code (src/vouch/llm_draft.py)MTC-SRC-002

In the server's implementation (`src/vouch/llm_draft.py:45`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: try: proc = subprocess.run( llm_cmd, shell=True, cwd=tmp, input=prompt, capt

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server src/vouch/llm_draft.py

high Shell/command execution in server code (src/vouch/pr_cache.py)MTC-SRC-002

In the server's implementation (`src/vouch/pr_cache.py:150`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: try: res = subprocess.run( ["gh", *args], check=False, text=True,

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server src/vouch/pr_cache.py

medium Dynamic module load from a non-literal (src/vouch/web/__init__.py)MTC-SRC-005

In the server's implementation (`src/vouch/web/__init__.py:44`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: try: __import__(name) except ImportError: missing.append(name) if missing:

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server src/vouch/web/__init__.py

low Mutating tool "kb_eval_embeddings" declares no destructiveHintMTC-CAP-005

Tool "kb_eval_embeddings" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool kb_eval_embeddings

low Shell/command execution in packaging/dev tooling (tests/test_capture.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_capture.py:242`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: : str) -> None: subprocess.run( ["git", "-c", "user.email=t@t", "-c", "user.name=t", *args],

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/test_capture.py

low Shell/command execution in packaging/dev tooling (tests/test_cli.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_cli.py:691`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: = "latin-1" proc = subprocess.run( [sys.executable, "-m", "vouch", *args], cwd=tmp_path, en

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/test_cli.py

low Shell/command execution in packaging/dev tooling (tests/test_codex_adapter_load_real.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_codex_adapter_load_real.py:44`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: is not None return subprocess.run( [CODEX, *args], env=env, cwd=cwd, capture_output

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/test_codex_adapter_load_real.py

low Shell/command execution in packaging/dev tooling (tests/test_hub.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_hub.py:67`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: ) -> str: out = subprocess.run( [sys.executable, "-c", code], capture_output=True, text=True, check=

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/test_hub.py

low Shell/command execution in packaging/dev tooling (tests/test_install_adapter.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_install_adapter.py:1080`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: "hatchling") proc = subprocess.run( [sys.executable, "-m", "hatchling", "build", "-t", "wheel", "-d", str(tm

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/test_install_adapter.py

Tools 68

Each tool and what it can reach — statically extracted from the published source.

  • kb_eval_embeddingsruns code / shell
  • kb_activityno sensitive capability
  • kb_approveno sensitive capability
  • kb_archiveno sensitive capability
  • kb_auditno sensitive capability
  • kb_capabilitiesno sensitive capability
  • kb_citeno sensitive capability
  • kb_clear_claimsno sensitive capability
  • kb_compileno sensitive capability
  • kb_confirmno sensitive capability
Show 58 more tools ↓
  • kb_contextno sensitive capability
  • kb_contradictno sensitive capability
  • kb_crystallizeno sensitive capability
  • kb_dedup_scanno sensitive capability
  • kb_detect_themesno sensitive capability
  • kb_diffno sensitive capability
  • kb_digestno sensitive capability
  • kb_doctorno sensitive capability
  • kb_embeddings_statsno sensitive capability
  • kb_expertsno sensitive capability
  • kb_expireno sensitive capability
  • kb_exportno sensitive capability
  • kb_export_checkno sensitive capability
  • kb_get_skillno sensitive capability
  • kb_graph_exportno sensitive capability
  • kb_impactno sensitive capability
  • kb_import_checkno sensitive capability
  • kb_index_rebuildno sensitive capability
  • kb_lintno sensitive capability
  • kb_list_claimsno sensitive capability
  • kb_list_entitiesno sensitive capability
  • kb_list_pagesno sensitive capability
  • kb_list_pendingno sensitive capability
  • kb_list_relationsno sensitive capability
  • kb_list_sessionsno sensitive capability
  • kb_list_skillsno sensitive capability
  • kb_list_sourcesno sensitive capability
  • kb_neighborsno sensitive capability
  • kb_propose_claimno sensitive capability
  • kb_propose_deleteno sensitive capability
  • kb_propose_entityno sensitive capability
  • kb_propose_pageno sensitive capability
  • kb_propose_relationno sensitive capability
  • kb_propose_themeno sensitive capability
  • kb_provenance_rebuildno sensitive capability
  • kb_read_claimno sensitive capability
  • kb_read_entityno sensitive capability
  • kb_read_pageno sensitive capability
  • kb_read_relationno sensitive capability
  • kb_register_sourceno sensitive capability
  • kb_register_source_from_pathno sensitive capability
  • kb_reindex_embeddingsno sensitive capability
  • kb_rejectno sensitive capability
  • kb_reject_extractedno sensitive capability
  • kb_searchno sensitive capability
  • kb_session_endno sensitive capability
  • kb_session_startno sensitive capability
  • kb_session_transcriptno sensitive capability
  • kb_source_verifyno sensitive capability
  • kb_statsno sensitive capability
  • kb_statusno sensitive capability
  • kb_summarize_sessionno sensitive capability
  • kb_supersedeno sensitive capability
  • kb_synthesizeno sensitive capability
  • kb_traceno sensitive capability
  • kb_triage_pendingno sensitive capability
  • kb_volunteer_contextno sensitive capability
  • kb_whyno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.5.0 latest A 93/100 13 1.13.0 2026-08-25

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/vouch-kb/badge.svg)](https://mcptrustchecker.com/registry/vouch-kb)
HTML
<a href="https://mcptrustchecker.com/registry/vouch-kb"><img src="https://mcptrustchecker.com/registry/vouch-kb/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/vouch-kb/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan vouch-kb --online --registry pypi

Use the free API → How scoring works

More in Developer Tools