CodexGuild
NPM · @CODEXGUILD/MCP · 2 COMPONENTS
What changed in your stack since the model's cutoff, error fixes, and security-scanned skills/MCPs
Available components
Last scanned (16 hours ago)
Scores higher than 37% of npm servers
Category Security
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
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 436 tokens (~109/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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 18 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 17 Oct 26 50
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 18 Oct 2026 · Analysed npm/@codexguild/mcp@1.11.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 31 |
| 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 →
codexguild_lint_instructions ~101
Lint the agent instruction files in this project (AGENTS.md, CLAUDE.md, GEMINI.md, .cursorrules…): size per session, missing build/test commands, README copy, generic advice, secrets, machine-specific paths, prompt-injection and other scanner findings. Runs locally — file contents are not uploaded.
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | – | Paths to lint instead of the instruction files found in the project root |
No output schema declared.
No examples provided.
codexguild_scan_code ~104
Find deprecated and removed APIs in this project's code for the exact versions it runs (from the lockfiles): e.g. `app.mount` deprecated in hono 4.13, with the replacement and where it is used (file:line). Only package names and versions are sent to CodexGuild; the code is searched locally and never uploaded. codexguild_sync runs this automatically.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Project directory (defaults to the current directory) |
No output schema declared.
No examples provided.
codexguild_scan_skills ~112
Security-audit the skills installed on THIS machine (~/.claude/skills, Claude plugins, ~/.codex/skills, ~/.agents/skills, ~/.hermes/skills, project skills…). Detects pipe-to-shell, credential exfiltration, hidden unicode, prompt injection, agent-config tampering and safety bypasses. Runs locally — nothing is uploaded.
| Name | Type | Req | Description |
|---|---|---|---|
| paths | array | – | Optional directories to scan instead of the defaults |
| verbose | boolean | – | Include passed skills and all findings |
No output schema declared.
No examples provided.
codexguild_scan_workflows ~119
Security-review the GitHub Actions workflows in this project that run coding agents (claude-code-action, run-gemini-cli, codex, opencode, aider…): triggers outside contributors control (pull_request_target, issue_comment, issues) combined with secrets, issue/PR text interpolated into prompts or shells (prompt injection), unrestricted agent tools, broad permissions, unpinned agent actions. Runs locally — nothing is uploaded.
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | – | Workflow files to review instead of .github/workflows/*.yml |
No output schema declared.
No examples provided.
How do I install the CodexGuild MCP server?
CodexGuild runs locally as an npm package, launched with npx -y @codexguild/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @codexguild/mcp
claude mcp add com-codexguild-codexguild -- npx -y @codexguild/mcp
What is the CodexGuild MCP server?
CodexGuild is an MCP server listed in the public MCP registry as com.codexguild/codexguild. What changed in your stack since the model's cutoff, error fixes, and security-scanned skills/MCPs. This page covers its npm package (@codexguild/mcp).
Is the CodexGuild MCP server safe to use?
CodexGuild scores 65 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 18 October 2026. It declares no install or post-install scripts. 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 CodexGuild MCP server expose?
CodexGuild exposes 4 tools: codexguild_scan_skills, codexguild_lint_instructions, codexguild_scan_workflows, codexguild_scan_code. Their descriptions and schemas cost roughly 436 tokens of context every time the server is loaded.
Is the CodexGuild MCP server still maintained?
CodexGuild is still listed as active in the MCP registry. We last reached this channel on 18 October 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 CodexGuild MCP server under?
CodexGuild declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.