Kindex MCP Server

kindex PyPI v0.29.0

Published by jmcentire — 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.

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.
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 12

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

Tool "remind_exec" appears to run shell commands or evaluate code (keyword "exec" 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 remind_exec

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

In the server's implementation (`src/kindex/actions.py:169`): 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( command, shell=True, capture_output=True, text=True, tim

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/kindex/actions.py

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

In the server's implementation (`src/kindex/adapters/code.py:36`): 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: r = subprocess.run( ["ctags", "--version"], 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/kindex/adapters/code.py

high Shell/command execution in server code (src/kindex/adapters/git_hooks.py)MTC-SRC-002

In the server's implementation (`src/kindex/adapters/git_hooks.py:154`): 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: result = subprocess.run( ["git", "-C", str(repo_path), "log", f"--max-count={limit}",

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/kindex/adapters/git_hooks.py

high Shell/command execution in server code (src/kindex/adapters/github.py)MTC-SRC-002

In the server's implementation (`src/kindex/adapters/github.py:17`): 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: result = subprocess.run(["gh", "auth", "status"], capture_output=True, tex

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/kindex/adapters/github.py

high Shell/command execution in server code (src/kindex/adapters/linear.py)MTC-SRC-002

In the server's implementation (`src/kindex/adapters/linear.py:28`): 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: result = subprocess.run( ["curl", "-s", "-X", "POST", "https://api.linear.app/gr

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/kindex/adapters/linear.py

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

In the server's implementation (`src/kindex/attention.py:1295`): 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: ts.""" try: subprocess.Popen( [ sys.executable, "-m",

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/kindex/attention.py

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

In the server's implementation (`src/kindex/cli.py:5065`): 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: ss result = subprocess.run(["crontab", "-l"], capture_output=True, text=True) if result.returnco

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/kindex/cli.py

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

In the server's implementation (`src/kindex/code_map.py:37`): 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: r = subprocess.run( ["git", "rev-parse", "HEAD"], cwd=str(directory),

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/kindex/code_map.py

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

In the server's implementation (`src/kindex/config.py:496`): 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: y: result = subprocess.run( command, capture_output=True, text=True, timeout

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/kindex/config.py

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

In the server's implementation (`src/kindex/dream.py:588`): 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: log_fd: proc = subprocess.Popen( cmd, start_new_session=True, stdout=log_fd

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/kindex/dream.py

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

Tool "remind_exec" 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 remind_exec

Tools 52

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

  • remind_execruns code / shell
  • addno sensitive capability
  • askno sensitive capability
  • changelogno sensitive capability
  • contextno sensitive capability
  • coord_attachno sensitive capability
  • coord_endno sensitive capability
  • coord_injectno sensitive capability
  • coord_joinno sensitive capability
  • coord_listno sensitive capability
Show 42 more tools ↓
  • coord_postno sensitive capability
  • coord_readno sensitive capability
  • coord_startno sensitive capability
  • dreamno sensitive capability
  • editno sensitive capability
  • graph_healno sensitive capability
  • graph_mergeno sensitive capability
  • graph_statsno sensitive capability
  • ingestno sensitive capability
  • learnno sensitive capability
  • linkno sensitive capability
  • list_nodesno sensitive capability
  • lock_acquireno sensitive capability
  • lock_releaseno sensitive capability
  • mode_activateno sensitive capability
  • mode_createno sensitive capability
  • mode_exportno sensitive capability
  • mode_importno sensitive capability
  • mode_listno sensitive capability
  • mode_seedno sensitive capability
  • mode_showno sensitive capability
  • remind_checkno sensitive capability
  • remind_createno sensitive capability
  • remind_doneno sensitive capability
  • remind_listno sensitive capability
  • remind_snoozeno sensitive capability
  • searchno sensitive capability
  • showno sensitive capability
  • statusno sensitive capability
  • suggestno sensitive capability
  • supersedeno sensitive capability
  • tag_resumeno sensitive capability
  • tag_startno sensitive capability
  • tag_updateno sensitive capability
  • task_addno sensitive capability
  • task_claimno sensitive capability
  • task_doneno sensitive capability
  • task_listno sensitive capability
  • task_releaseno sensitive capability
  • watch_addno sensitive capability
  • watch_listno sensitive capability
  • watch_resolveno 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
v0.29.0 latest A 93/100 12 1.9.0 2026-07-23

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/kindex/badge.svg)](https://mcptrustchecker.com/registry/kindex)
HTML
<a href="https://mcptrustchecker.com/registry/kindex"><img src="https://mcptrustchecker.com/registry/kindex/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/kindex/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 kindex --online --registry pypi

Use the free API → How scoring works

More in Data Science & ML