Chassis
NPM · CHASSIS-MCP · SCANNED SEP 30
Scaffold an Express 5 + TypeScript backend: database, auth, optional Next.js front end.
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 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 94 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- 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 61 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 323 tokens (~107/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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 Chassis MCP server?
Chassis runs locally as an npm package, launched with npx -y chassis-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 · chassis-mcp
claude mcp add dvd90-chassis-mcp -- npx -y chassis-mcp
{
"mcpServers": {
"dvd90-chassis-mcp": {
"command": "npx",
"args": [
"-y",
"chassis-mcp"
]
}
}
} {
"servers": {
"dvd90-chassis-mcp": {
"command": "npx",
"args": [
"-y",
"chassis-mcp"
]
}
}
} codex mcp add dvd90-chassis-mcp -- npx -y chassis-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dvd90-chassis-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"chassis-mcp"
],
"enabled": true
}
}
} openclaw mcp add dvd90-chassis-mcp --command npx --arg -y --arg chassis-mcp
mcp_servers:
dvd90-chassis-mcp:
command: "npx"
args: ["-y", "chassis-mcp"] {
"McpServers": {
"dvd90-chassis-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"chassis-mcp"
]
}
}
} assistant mcp add dvd90-chassis-mcp -t stdio -c npx -a -y chassis-mcp
{
"mcpServers": {
"dvd90-chassis-mcp": {
"command": "npx",
"args": [
"-y",
"chassis-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.
- 30 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 −2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 0
- Stability: 0.97 → pass security
- Security disclosure: unverified → fail ▼ functional
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 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 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 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 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 −3
- Security disclosure: unverified → fail ▼ functional
- Stability: pass → 0.80 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 30 Sept 2026 · Analysed npm/chassis-mcp@0.1.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 94 packages
| Packages resolved | 94 |
|---|---|
| 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 →
chassis_conventions Chassis conventions ~76
How to write code in a Chassis project: controllers, responses, errors, validation, config, and the definition of done. Read this before editing a Chassis codebase.
| Name | Type | Req | Description |
|---|---|---|---|
| directory | string | – | A Chassis project root. Its AGENTS.md is returned when present, which is more specific than the built-in summary. |
No output schema declared.
No examples provided.
create_chassis_project Create a Chassis project ~206
Scaffold a Chassis backend (Express 5 + TypeScript) into a new or empty directory. The result typechecks, lints and tests green as created, and contains only the modules chosen — declined ones are removed from the source and from package.json.
| Name | Type | Req | Description |
|---|---|---|---|
| auth | string | – | Auth provider. |
| db | string | – | Database and ORM. |
| directory | string | yes | Target directory. Must not exist, or must be empty. |
| docker | boolean | – | Dockerfile + docker-compose. |
| install | boolean | – | Run npm install afterwards. Default false — it is slow. |
| mcp | boolean | – | An MCP server exposing the generated project's own API. |
| preset | string | – | Starting point; individual fields below override it. |
| sentry | boolean | – | Sentry error reporting. |
| web | boolean | – | Add a Next.js front end (workspaces monorepo). |
| x402 | boolean | – | x402 payment-gated routes. |
No output schema declared.
No examples provided.
list_chassis_options List Chassis options ~41
List the presets, databases, auth providers and add-ons that create_chassis_project accepts. Call this first when you are not sure which stack to request.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the Chassis MCP server?
Chassis is an MCP server listed in the public MCP registry as io.github.dvd90/chassis-mcp. Scaffold an Express 5 + TypeScript backend: database, auth, optional Next.js front end. This page covers its npm package (chassis-mcp).
Is the Chassis MCP server safe to use?
Chassis scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 30 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 Chassis MCP server expose?
Chassis exposes 3 tools: list_chassis_options, create_chassis_project, chassis_conventions. Their descriptions and schemas cost roughly 323 tokens of context every time the server is loaded.
Is the Chassis MCP server still maintained?
Chassis is still listed as active in the MCP registry. We last reached this channel on 30 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 Chassis MCP server under?
Chassis declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.