codemcp
NPM · CODEMCP-CLI
Code mode for MCP: search, describe and execute over all your servers, with a sandbox and approvals.
Available components
Last scanned (12 hours ago)
Scores higher than 69% of npm servers
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known low-severity CVE affects esbuild 0.27.7, reached via codemcp-core > esbuild. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 6 of 57 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to stackunseen/codemcp). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 1 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 383 tokens (~95/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage81
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 44% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +11
- Known CVEs: unverified → fail ▼ security
- Dependency health: unverified → 0.96 ▲ functional
- 3 Nov 26 −8
- Known CVEs: fail → unverified ▼ security
- Dependency health: 0.90 → unverified ▼ functional
- Stability: unverified → 0.13 ▲ functional
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- Package version: 0.4.0 → 0.5.0 functional
- 31 Oct 26 +1
- Security disclosure: unverified → pass ▲ functional
- 30 Oct 26 77
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/codemcp-cli@0.5.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | stackunseen/codemcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/stackunseen/codemcp/.github/workflows/release.yml@refs/heads/main |
| Rekor log index | 3657939832 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:57663631492e47169d173334ffc4620adb829b71abe84cee25f2b914c45a1f806516a93a49e156cf7195fb87b820a5b19351a926156b96321c3d91b1f |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-g7r4-m6w7-qqqr | low | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 57 packages
| Packages resolved | 57 |
|---|---|
| Stale | 6 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
approve ~47
Resume an execution that paused for approval. Only call this after a human has explicitly decided.
| Name | Type | Req | Description |
|---|---|---|---|
| allow | boolean | yes | – |
| executionId | string | yes | – |
| seq | integer | yes | – |
No output schema declared.
No examples provided.
describe ~94
Return TypeScript signatures (and, with detail=full, documentation and output types) for the given tools or for every tool of a server. Call this to learn exact argument shapes before writing code. Servers: (none connected).
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | – |
| server | string | – | Describe every tool of this server instead. |
| tools | array | – | Qualified names (server.tool) or stub paths (tools.server.tool). |
No output schema declared.
No examples provided.
execute ~174
Run TypeScript/JavaScript in a sandbox. Call tools as `await tools.<server>.<tool>({...})`. Use loops, filters and `console.log` freely; only the returned value and logs come back to you. The sandbox has no network, filesystem, timers beyond the deadline, or access to credentials. Return a compact result; large intermediate data should stay in the sandbox. Write the body of an async function. Use `return` to send a value back. Tools are at `tools.<server>.<tool>(args)` and return Promises. Call `describe` first for exact types. Independent tool calls may run concurrently with Promise.all. Errors from tools throw; catch them if you want to continue.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Body of an async function. Use `return` for the result. |
No output schema declared.
No examples provided.
search ~68
Search the available tools by keyword. Returns qualified names and one-line summaries. Use before `describe` or `execute` when you do not already know the tool you need.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | Keywords, a tool name fragment, or a short task description. |
No output schema declared.
No examples provided.
How do I install the codemcp MCP server?
codemcp runs locally as an npm package, launched with npx -y codemcp-cli. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · codemcp-cli
claude mcp add stackunseen-codemcp -- npx -y codemcp-cli
What is the codemcp MCP server?
codemcp is an MCP server listed in the public MCP registry as io.github.stackunseen/codemcp. Code mode for MCP: search, describe and execute over all your servers, with a sandbox and approvals. This page covers its npm package (codemcp-cli).
Is the codemcp MCP server safe to use?
codemcp scores 81 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the codemcp MCP server expose?
codemcp exposes 4 tools: search, describe, execute, approve. Their descriptions and schemas cost roughly 383 tokens of context every time the server is loaded.
Is the codemcp MCP server still maintained?
codemcp is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the codemcp MCP server under?
codemcp declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.