Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

BackendGen

NPM · @2HEMI/BACKENDGEN-MCP · SCANNED AUG 3

Validate compact backend specs and generate tested NestJS, Prisma, and PostgreSQL repositories.

Available components

npm · @2hemi/backendgen-mcp 82
−9 this week 82 Trust /100
Trust breakdown (6 categories)

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 →

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 & Transparency97
  • 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 14 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
  • 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 Management23
  • Stability observed for 7 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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @2hemi/backendgen-mcp

# add to Claude Code
claude mcp add sitouhemi-backendgen -- npx -y @2hemi/backendgen-mcp
# add to Codex CLI
codex mcp add sitouhemi-backendgen -- npx -y @2hemi/backendgen-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "sitouhemi-backendgen": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@2hemi/backendgen-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add sitouhemi-backendgen --command npx --arg -y --arg @2hemi/backendgen-mcp
# ~/.hermes/config.yaml
mcp_servers:
  sitouhemi-backendgen:
    command: "npx"
    args: ["-y", "@2hemi/backendgen-mcp"]
// mcp.json
{
  "mcpServers": {
    "sitouhemi-backendgen": {
      "command": "npx",
      "args": [
        "-y",
        "@2hemi/backendgen-mcp"
      ]
    }
  }
}
Changelog

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.

  • 3 Aug 26 +4
    • Stability: unverified → 0.23 ▲ functional
  • 1 Aug 26 +15
    • Malware scan: unverified → pass ▲ security
  • 31 Jul 26 −10
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 −18
    • Malware scan: pass → unverified ▼ security
  • 27 Jul 26 +32
    • Tool coverage: unverified → 100 ▲ functional
    • First check of Schema quality: fail functional
    • First check of Tool coverage: 68 functional
    • First check of Schema quality: pass functional
    • First check of Schema quality: good functional
  • 26 Jul 26 59

    First indexed and scored.

    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

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 3 Aug 2026 · Analysed npm/@2hemi/[email protected]

Provenance verified

Ecosystem: npm · Outcome: verified

Reason: verified

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
Discovery method:
attestation_endpoint
Dependencies 0 packages

0 packages in the resolved dependency tree.

MCP tools — 12 exposed · ~620 tokens

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.

Tool Tokens
describe_feature ~29

One feature's configuration JSON Schema, dependencies, conflicts and worked examples.

NameTypeReqDescription
featurestringyes—

No output schema declared.

No examples provided.

describe_target ~29

Full detail for one target: databases, capabilities and project commands.

NameTypeReqDescription
targetIdstringyes—

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.

NameTypeReqDescription
specobject—The specification inline, as an object. Use this or specPath, not both.
specPathstring—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/.

NameTypeReqDescription
forceboolean—Overwrite generated files that have local modifications.
outputPathstringyes—
specobject—The specification inline, as an object. Use this or specPath, not both.
specPathstring—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.

NameTypeReqDescription
outputPathstringyes—

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.

NameTypeReqDescription
specobject—The specification inline, as an object. Use this or specPath, not both.
specPathstring—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.

NameTypeReqDescription
outputPathstringyes—
specobject—The specification inline, as an object. Use this or specPath, not both.
specPathstring—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.

NameTypeReqDescription
installboolean—Install dependencies first.
integrationboolean—Also run the integration suite.
outputPathstringyes—

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.

NameTypeReqDescription
specobject—The specification inline, as an object. Use this or specPath, not both.
specPathstring—Path to a YAML or JSON specification, inside an allowed root.

No output schema declared.

No examples provided.