Knowledge (codemcp) MCP Server

@codemcp/knowledge npm v2.2.0

Published by @codemcp — no publish provenance and no vendor-owned scope, so the publisher could not be verified. The repository link below is self-declared.

Trust grade
A
100/100
Last scanned
Trust
A · 100/100
How safe the published surface and source look. 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

Started at 100 and nothing was deducted: the deterministic scan raised no scored threat in the published surface it inspected. Capability observations and advisory notes are recorded but never lower the score.

Findings 4

high Shell/command execution in server code (packages/cli/dist/chunk-RYB5PQKB.js)MTC-SRC-002

In the server's implementation (`packages/cli/dist/chunk-RYB5PQKB.js:3170`): 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: child_process

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 packages/cli/dist/chunk-RYB5PQKB.js

high Shell/command execution in server code (packages/cli/dist/index.js)MTC-SRC-002

In the server's implementation (`packages/cli/dist/index.js:31`): 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: child_process

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 packages/cli/dist/index.js

high Shell/command execution in server code (packages/content-loader/dist/content/git-repo-loader.js)MTC-SRC-002

In the server's implementation (`packages/content-loader/dist/content/git-repo-loader.js:6`): 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: child_process

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 packages/content-loader/dist/content/git-repo-loader.js

high Shell/command execution in server code (packages/mcp-server/dist/chunk-TXODDW25.js)MTC-SRC-002

In the server's implementation (`packages/mcp-server/dist/chunk-TXODDW25.js:3376`): 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: child_process

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 packages/mcp-server/dist/chunk-TXODDW25.js

What this scan could not see

Versions

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
v2.2.0 latest A 100/100 4 1.5.0 2026-07-22

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 · 100/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/codemcp-knowledge/badge.svg)](https://mcptrustchecker.com/registry/codemcp-knowledge)
HTML
<a href="https://mcptrustchecker.com/registry/codemcp-knowledge"><img src="https://mcptrustchecker.com/registry/codemcp-knowledge/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/codemcp-knowledge/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 @codemcp/knowledge --online

Use the free API → How scoring works

Other implementations of Knowledge 7

Independent packages implementing the same tool, scanned with the same engine. Compare all 8 side by side →

More in Learning & Documentation