Codemesh (pyalwin) MCP Server
@pyalwin/codemesh
npm
v0.1.2
Published by @pyalwin — 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.
Intelligent code knowledge graph for AI coding agents
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 − 9.5 = 91. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −9.5 | Untrusted input concatenated into a command sink ×2 MTC-SRC-009 | injection |
2. Client adoption risk — 91 − 7 = 84. 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 |
| −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 6
high Shell/command execution in server code (dist/indexer/git-intel.js)MTC-SRC-002
In the server's implementation (`dist/indexer/git-intel.js:7`): 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: { execSync } from "node:child_process"; /** * Analyze git history to extract hotspots and co-change pairs. * * @param
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 dist/indexer/git-intel.js
high Shell/command execution in server code (dist/tools/lsp-client.js)MTC-SRC-002
In the server's implementation (`dist/tools/lsp-client.js:10`): 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: , execSync } from "node:child_process"; import { readFileSync } from "node:fs"; import { extname, resolve } from "node: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 dist/tools/lsp-client.js
medium Untrusted input concatenated into a command sink (dist/indexer/git-intel.js)MTC-SRC-009
In the server's implementation (`dist/indexer/git-intel.js:17`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. 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 { logOutput = execSync(`git log --name-only --pretty=format:'---COMMIT---%ai' -n ${maxCommits}`, {
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 dist/indexer/git-intel.js
medium Untrusted input concatenated into a command sink (dist/tools/lsp-client.js)MTC-SRC-009
In the server's implementation (`dist/tools/lsp-client.js:17`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: md) { try { execSync(`which ${cmd}`, { stdio: "ignore" }); return true; } catch { re
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 dist/tools/lsp-client.js
medium Dynamic module load from a non-literal (dist/indexer/embeddings.js)MTC-SRC-005
In the server's implementation (`dist/indexer/embeddings.js:12`): 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: on("specifier", "return import(specifier)"); // ── Model loading (lazy) ──────────────────────────────────────────── let
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 dist/indexer/embeddings.js
medium Dynamic module load from a non-literal (dist/indexer/parser.js)MTC-SRC-005
In the server's implementation (`dist/indexer/parser.js:29`): 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: imports const mod = require(grammarPackage); // tree-sitter-typescript exports { typescript, tsx } // most o
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 dist/indexer/parser.js
Tools 8
Each tool and what it can reach — statically extracted from the published source.
codemesh_answerno sensitive capabilitycodemesh_enrichno sensitive capabilitycodemesh_exploreno sensitive capabilitycodemesh_mapno sensitive capabilitycodemesh_sourceno sensitive capabilitycodemesh_statusno sensitive capabilitycodemesh_traceno sensitive capabilitycodemesh_workflowno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (8 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.1.2 latest |
B 84/100 | 6 | 1.13.0 | 2026-09-07 |
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.
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 @pyalwin/codemesh --onlineOther implementations of Codemesh 1
Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →
More in Web, Search & Scraping
Agent IP: MCP server with patents search tools
MCP server for searching the Agent Almanac — the public catalog of 9,000+ Model Context Protocol servers. Find, install, and discover MCP servers from inside Claude Desktop, Cursor, Continue, Zed, or any MCP-aware agent.
Search agents & MCP servers by capability, with daily-observed pricing, liveness and market data.
Verified merchants accepting agentic payments on Lightning/L402/BOLT12/USDT — search, verify, pay.
Airframe MCP Client - Connect agents to Airframe's product intelligence
Amazon product search demand over time, with growth for any keyword. Free key at trendsmcp.ai