BackendGen
NPM · @2HEMI/BACKENDGEN-MCP · SCANNED SEP 20
Validate compact backend specs and generate tested NestJS, Prisma, and PostgreSQL repositories.
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 Security100
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to SiTouhemi/Backendgen). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 62 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 620 tokens (~51/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 68% 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
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 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 BackendGen MCP server?
BackendGen runs locally as an npm package, launched with npx -y @2hemi/backendgen-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 · @2hemi/backendgen-mcp
claude mcp add sitouhemi-backendgen -- npx -y @2hemi/backendgen-mcp
{
"mcpServers": {
"sitouhemi-backendgen": {
"command": "npx",
"args": [
"-y",
"@2hemi/backendgen-mcp"
]
}
}
} {
"servers": {
"sitouhemi-backendgen": {
"command": "npx",
"args": [
"-y",
"@2hemi/backendgen-mcp"
]
}
}
} codex mcp add sitouhemi-backendgen -- npx -y @2hemi/backendgen-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sitouhemi-backendgen": {
"type": "local",
"command": [
"npx",
"-y",
"@2hemi/backendgen-mcp"
],
"enabled": true
}
}
} openclaw mcp add sitouhemi-backendgen --command npx --arg -y --arg @2hemi/backendgen-mcp
mcp_servers:
sitouhemi-backendgen:
command: "npx"
args: ["-y", "@2hemi/backendgen-mcp"] {
"McpServers": {
"sitouhemi-backendgen": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@2hemi/backendgen-mcp"
]
}
}
} assistant mcp add sitouhemi-backendgen -t stdio -c npx -a -y @2hemi/backendgen-mcp
{
"mcpServers": {
"sitouhemi-backendgen": {
"command": "npx",
"args": [
"-y",
"@2hemi/backendgen-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.
- 19 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.
- 17 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.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 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.
- 12 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.
- 10 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.
- 9 Sept 26 −3
- 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 20 Sept 2026 · Analysed npm/@2hemi/backendgen-mcp@0.2.2
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 | SiTouhemi/Backendgen |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/SiTouhemi/Backendgen/.github/workflows/release.yml@refs/tags/v0.2.2 |
| Rekor log index | 2200208723 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:130d5ad90868506fdff13591e493894bb0a846a790ce278a2a58367564d031b8ec3436c03d67ca501ba1006fa2770a77edc6428459fe1ee0ecdc39291 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
describe_feature ~29
One feature's configuration JSON Schema, dependencies, conflicts and worked examples.
| Name | Type | Req | Description |
|---|---|---|---|
| feature | string | yes | – |
No output schema declared.
No examples provided.
describe_target ~29
Full detail for one target: databases, capabilities and project commands.
| Name | Type | Req | Description |
|---|---|---|---|
| targetId | string | yes | – |
No output schema declared.
No examples provided.
explain_customization_points ~70
Where to put custom code for a specification, and which interface each extension point expects.
| Name | Type | Req | Description |
|---|---|---|---|
| spec | object | – | The specification inline, as an object. Use this or specPath, not both. |
| specPath | string | – | Path to a YAML or JSON specification, inside an allowed root. |
No output schema declared.
No examples provided.
generate_backend ~102
Generate the backend. Refuses by default if a generated file was edited by hand; pass force to overwrite. Never overwrites src/custom/.
| Name | Type | Req | Description |
|---|---|---|---|
| force | boolean | – | Overwrite generated files that have local modifications. |
| outputPath | string | yes | – |
| spec | object | – | The specification inline, as an object. Use this or specPath, not both. |
| specPath | string | – | Path to a YAML or JSON specification, inside an allowed root. |
No output schema declared.
No examples provided.
get_capabilities ~29
What this compiler can generate: specification version, targets, features and response limits. Call this first.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_generation_report ~35
Read the generation manifest of an already-generated project: versions, checksums and file ownership.
| Name | Type | Req | Description |
|---|---|---|---|
| outputPath | string | yes | – |
No output schema declared.
No examples provided.
inspect_spec ~71
Compile a specification and return the normalized backend IR: entities, endpoints, events, secrets and infrastructure.
| Name | Type | Req | Description |
|---|---|---|---|
| spec | object | – | The specification inline, as an object. Use this or specPath, not both. |
| specPath | string | – | Path to a YAML or JSON specification, inside an allowed root. |
No output schema declared.
No examples provided.
list_features ~26
Feature packs available, with their dependencies and conflicts. Use describe_feature for the configuration schema.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_targets ~20
Backend targets this compiler can generate, with their supported databases.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
preview_generation ~78
Dry run: what generation would create, update, delete or refuse to overwrite. Writes nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| outputPath | string | yes | – |
| spec | object | – | The specification inline, as an object. Use this or specPath, not both. |
| specPath | string | – | Path to a YAML or JSON specification, inside an allowed root. |
No output schema declared.
No examples provided.
run_generated_tests ~59
Run the generated project's test suites and return counts, not logs. Integration tests need a reachable database.
| Name | Type | Req | Description |
|---|---|---|---|
| install | boolean | – | Install dependencies first. |
| integration | boolean | – | Also run the integration suite. |
| outputPath | string | yes | – |
No output schema declared.
No examples provided.
validate_spec ~72
Validate a specification. Returns stable error codes and JSON pointers, so a failure can be fixed without guessing.
| Name | Type | Req | Description |
|---|---|---|---|
| spec | object | – | The specification inline, as an object. Use this or specPath, not both. |
| specPath | string | – | Path to a YAML or JSON specification, inside an allowed root. |
No output schema declared.
No examples provided.
What is the BackendGen MCP server?
BackendGen is an MCP server listed in the public MCP registry as io.github.SiTouhemi/backendgen. Validate compact backend specs and generate tested NestJS, Prisma, and PostgreSQL repositories. This page covers its npm package (@2hemi/backendgen-mcp).
Is the BackendGen MCP server safe to use?
BackendGen scores 94 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 BackendGen MCP server expose?
BackendGen exposes 12 tools: get_capabilities, list_targets, describe_target, list_features, describe_feature, and 7 more. Their descriptions and schemas cost roughly 620 tokens of context every time the server is loaded.
Is the BackendGen MCP server still maintained?
BackendGen is still listed as active in the MCP registry. We last reached this channel on 20 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 BackendGen MCP server under?
BackendGen 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.