Codehabits
NPM · @CODEHABITS/MCP · SCANNED SEP 25
Team conventions, anti-patterns, and domain knowledge from .codehabits/ for AI coding agents.
Available components
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 Security99
- 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
- 41 of 165 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. 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 12 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 510 tokens (~63/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
How do I install the Codehabits MCP server?
Codehabits runs locally as an npm package, launched with npx -y @codehabits/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 · @codehabits/mcp
claude mcp add codehabits-dev-codehabits-mcp -- npx -y @codehabits/mcp
{
"mcpServers": {
"codehabits-dev-codehabits-mcp": {
"command": "npx",
"args": [
"-y",
"@codehabits/mcp"
]
}
}
} {
"servers": {
"codehabits-dev-codehabits-mcp": {
"command": "npx",
"args": [
"-y",
"@codehabits/mcp"
]
}
}
} codex mcp add codehabits-dev-codehabits-mcp -- npx -y @codehabits/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"codehabits-dev-codehabits-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@codehabits/mcp"
],
"enabled": true
}
}
} openclaw mcp add codehabits-dev-codehabits-mcp --command npx --arg -y --arg @codehabits/mcp
mcp_servers:
codehabits-dev-codehabits-mcp:
command: "npx"
args: ["-y", "@codehabits/mcp"] {
"McpServers": {
"codehabits-dev-codehabits-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@codehabits/mcp"
]
}
}
} assistant mcp add codehabits-dev-codehabits-mcp -t stdio -c npx -a -y @codehabits/mcp
{
"mcpServers": {
"codehabits-dev-codehabits-mcp": {
"command": "npx",
"args": [
"-y",
"@codehabits/mcp"
]
}
}
} 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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +4
- Stability: unverified → 0.27 ▲ functional
- 13 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 12 Sept 26 +17
- Malware scan: pass → unverified ▼ security
- Injection markers: unverified → pass ▲ security
- Known CVEs: partial → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
- Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
- Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
- Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
- Dependency health: partial → 0.88 functional
- Package version: 0.1.3 → 0.1.4 functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 25 Sept 2026 · Analysed npm/@codehabits/mcp@0.1.4
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 165 packages
| Packages resolved | 165 |
|---|---|
| Stale | 41 |
| 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_proposal ~55
Approve a pending proposal and merge it into active intelligence (conventions.json) and regenerate skill markdown. Creates tracked git changes.
| Name | Type | Req | Description |
|---|---|---|---|
| proposal_id | string | yes | Proposal id from record_feedback (e.g. prop-001) |
No output schema declared.
No examples provided.
check_code ~51
Validate a code snippet against team conventions and anti-patterns. Returns violations with suggestions.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The code snippet to check |
| file_path | string | – | File path for context-aware checking |
No output schema declared.
No examples provided.
get_change_routes ~49
Given a path or directory prefix, return directories/files that often change together (from git co-change heuristics).
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | File path or directory prefix to find related change routes for |
No output schema declared.
No examples provided.
get_knowledge ~50
Get domain-specific knowledge about a topic (e.g., authentication, database, deployment)
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | yes | The topic to look up (e.g., "authentication", "database", "api") |
No output schema declared.
No examples provided.
get_repo_map ~61
Get the heuristic repository map (packages, entrypoints, subsystems, hot files, docs). Prefer this over exploring the whole tree. Optional section filter keeps context small.
| Name | Type | Req | Description |
|---|---|---|---|
| section | string | – | Slice of the map to return (default: compact all) |
No output schema declared.
No examples provided.
get_team_context ~67
Get team coding conventions, anti-patterns, and domain knowledge. Use this before writing or reviewing code to understand how the team works.
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | – | File path to get context specific to that file type |
| scope | string | – | Filter context to a specific area |
No output schema declared.
No examples provided.
record_feedback ~139
Record when a user overrides or corrects team intelligence, or propose a new convention. Writes to local .codehabits/proposals.json (gitignored); does not change tracked intelligence until approve_proposal.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Convention category (e.g. testing, naming) |
| file_path | string | – | File path where this came up |
| reason | string | yes | Why this change is being proposed |
| rule | string | – | Convention rule text (for new conventions) |
| targetId | string | – | ID of existing convention (required for update, exception, or deprecate) |
| type | string | yes | Kind of change |
No output schema declared.
No examples provided.
suggest_reviewers ~38
Suggest the best reviewers for a set of changed files based on team expertise
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | yes | List of file paths that were changed |
No output schema declared.
No examples provided.
What is the Codehabits MCP server?
Codehabits is an MCP server listed in the public MCP registry as io.github.codehabits-dev/codehabits-mcp. Team conventions, anti-patterns, and domain knowledge from .codehabits/ for AI coding agents. This page covers its npm package (@codehabits/mcp).
Is the Codehabits MCP server safe to use?
Codehabits scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 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 Codehabits MCP server expose?
Codehabits exposes 8 tools: get_team_context, check_code, get_knowledge, suggest_reviewers, get_repo_map, and 3 more. Their descriptions and schemas cost roughly 510 tokens of context every time the server is loaded.
Is the Codehabits MCP server still maintained?
Codehabits is still listed as active in the MCP registry. We last reached this channel on 25 September 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 Codehabits MCP server under?
Codehabits declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.