mykg
PyPI
v0.3.26
Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.
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 − 8 = 92. 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:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −2 | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read |
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.
In the server's implementation (`src/mykg/cli.py:1326`): 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: proc = subprocess.run( cmd, check=False, ti
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/mykg/cli.py
In the server's implementation (`src/mykg/fetch_web.py:115`): 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: }.git" try: subprocess.run( ["git", "clone", "--depth", str(depth), url, str(dest)],
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/mykg/fetch_web.py
In the server's implementation (`src/mykg/llm/claude_cli_adapter.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: try: proc = subprocess.run( cmd, input=user, 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 src/mykg/llm/claude_cli_adapter.py
In the server's implementation (`src/mykg/steps/step_preprocess.py:360`): 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( cmd, check=False, timeout=_cfg.P
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/mykg/steps/step_preprocess.py
In the server's implementation (`src/mykg/uv_venv.py:29`): 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( cmd, check=False, capture_output=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/mykg/uv_venv.py
In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/live_test_grow_schema.py:101`): 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: ".join(cmd)) proc = subprocess.run(cmd, cwd=str(REPO_ROOT)) return proc.returncode def _tail_run_log(session_r
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 scripts/live_test_grow_schema.py
Each tool and what it can reach — statically extracted from the published source.
mykg_find_pathno sensitive capabilitymykg_get_neighborsno sensitive capabilitymykg_get_nodeno sensitive capabilitymykg_get_schemano sensitive capabilitymykg_get_sourceno sensitive capabilitymykg_get_statsno sensitive capabilitymykg_hub_nodesno sensitive capabilitymykg_list_node_typesno sensitive capabilitymykg_list_sessionsno sensitive capabilitymykg_orphan_nodesno sensitive capabilitymykg_query_graphno sensitive capabilitymykg_query_subgraphno sensitive capabilitymykg_read_noteno sensitive capabilitymykg_reloadno sensitive capabilitymykg_search_nodesno sensitive capabilityScan 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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.3.26 latest |
A 92/100 | 6 | 1.9.0 | 2026-07-23 |
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.
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 mykg --online --registry pypi
Security scan results for the 2sio MCP server.
ArXiv preprints + Google Scholar papers, with citation counts in one query.
Security scan results for the Add MCP server.
Security scan results for the Ai Archive MCP server.
Security scan results for the Aira Semanticscholar MCP server.
Korean premium short-term rental search: natural language or structured filters (SHV engine).