H2BIS ProjectBrain MCP
NPM · H2BIS-MCP
Connect AI agents to H2BIS ProjectBrain - manage projects, use cases, and capabilities via MCP.
Available components
Last scanned (2 hours ago)
Scores higher than 53% of npm servers
Category Project Management
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 35 of 115 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 211 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1737 tokens (~115/item across 15 items; 15 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage86
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 59% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "removeProjectDomainModel" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 15 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
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.
- 5 Nov 26 +1
- Stability: 0.97 → pass security
- 3 Nov 26 −1
- Stability: pass → 0.93 functional
- 28 Oct 26 +1
- Stability: 0.97 → pass security
- 27 Oct 26 −1
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 21 Oct 26 0
- Stability: 0.97 → pass security
- 20 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.83 → pass security
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 5 Nov 2026 · Analysed npm/h2bis-mcp@1.1.18
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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 115 packages
| Packages resolved | 115 |
|---|---|
| Stale | 35 |
| 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 →
createProject ~102
Create a new software development project with metadata, tech stack, architecture details, and quality gates.
| Name | Type | Req | Description |
|---|---|---|---|
| _id | string | yes | Unique project identifier (e.g., "my-project") |
| accessControl | object | – | Access control settings |
| description | string | – | Project description |
| lifecycle | string | – | Project lifecycle stage |
| metadata | object | – | Project metadata including tech stack, architecture, standards, etc. |
| name | string | yes | Project name |
No output schema declared.
No examples provided.
createUseCase ~271
Create a new use case with all necessary details. If projectId is provided, automatically triggers capability graph generation. Required fields: key, name, description. All other fields are optional.
| Name | Type | Req | Description |
|---|---|---|---|
| acceptanceCriteria | array | – | List of acceptance criteria |
| aiDirectives | object | – | – |
| aiMetadata | object | – | – |
| businessValue | string | – | Business value or justification |
| description | string | yes | Detailed description of the use case |
| errorHandling | object | – | – |
| flows | array | – | – |
| functionalRequirements | object | – | – |
| implementationRisk | array | – | – |
| interfaces | object | – | – |
| key | string | yes | Unique key for the use case (e.g., "UC-LOGIN") |
| name | string | yes | Name of the use case |
| normative | boolean | – | – |
| primaryActor | string | – | Primary actor (e.g., "User", "Admin") |
| projectId | string | – | Project ID to associate the use case with (triggers capability generation) |
| quality | object | – | – |
| relationships | array | – | – |
| scope | object | – | – |
| stakeholders | array | – | List of stakeholders |
| status | object | – | – |
| tags | array | – | – |
| technicalSurface | object | – | – |
No output schema declared.
No examples provided.
deleteUseCase ~53
Delete a use case (soft delete). The use case will be marked as deleted but not removed from the database.
| Name | Type | Req | Description |
|---|---|---|---|
| useCaseId | string | yes | The unique identifier (_id) of the use case to delete |
No output schema declared.
No examples provided.
enhanceUseCase ~92
Enhance a use case using AI. Fills in missing sections (flows, technical surface, domain model) based on existing data. Optionally specify enhancementType: full, partial, flows_only, or technical_only.
| Name | Type | Req | Description |
|---|---|---|---|
| enhancementType | string | – | Type of enhancement to apply (default: full) |
| useCaseId | string | yes | The unique identifier (_id) of the use case to enhance with AI |
No output schema declared.
No examples provided.
getProjectById ~54
Get a specific project by ID with complete details including metadata, architecture, tech stack, quality gates, domain catalog, stats, and endpoints.
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | string | yes | The unique identifier of the project to retrieve |
No output schema declared.
No examples provided.
getUseCaseById ~59
Get a specific use case by ID with complete details including functional requirements, flows, technical surface, domain model, and all other sections.
| Name | Type | Req | Description |
|---|---|---|---|
| useCaseId | string | yes | The unique identifier (_id) of the use case to retrieve |
No output schema declared.
No examples provided.
getUseCaseWithProjectContext ~112
Retrieve a use case together with the full development context of its owning project (architecture, tech stack, repository, coding standards, auth strategy, quality gates, deployment, external services, developed endpoints, and stats). Use this tool whenever an AI agent needs to implement a software feature from a use case, so it can align the implementation with the project's architecture and conventions.
| Name | Type | Req | Description |
|---|---|---|---|
| useCaseId | string | yes | The unique identifier (_id) of the use case to retrieve together with its full project context |
No output schema declared.
No examples provided.
listProjects ~85
List projects with optional filtering by status and pagination. Returns id, name, description, lifecycle, and stats. Use this first to discover projects, then use getProjectById for full details.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of projects to return |
| offset | number | – | Number of projects to skip for pagination |
| status | string | – | Filter projects by status |
No output schema declared.
No examples provided.
listUseCases ~98
List use cases with optional filtering by project and pagination. Returns id, key, name, description, status, and basic details. Use this first to discover use cases, then use getUseCaseById for full details.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of use cases to return |
| offset | integer | – | Number of use cases to skip (for pagination) |
| projectId | string | – | Filter use cases by project ID |
No output schema declared.
No examples provided.
logout ~54
Sign out of the H2BIS system. Revokes the server-side refresh token and deletes the locally persisted access tokens. After logging out, the next tool call will automatically open a browser for a fresh GitHub OAuth sign-in.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
removeProjectDomainModel ~80
Remove a domain model from a project's domain catalog by name. Use this when a model is deleted or renamed during refactoring.
| Name | Type | Req | Description |
|---|---|---|---|
| modelName | string | yes | Exact name of the domain model to remove (case-sensitive, e.g. "UserDocument") |
| projectId | string | yes | The _id of the project that owns the domain catalog |
No output schema declared.
No examples provided.
updateProject ~93
Update an existing project's details, metadata, lifecycle stage, or access control settings.
| Name | Type | Req | Description |
|---|---|---|---|
| accessControl | object | – | Updated access control settings |
| description | string | – | Updated project description |
| lifecycle | string | – | Updated project lifecycle stage |
| metadata | object | – | Updated project metadata |
| name | string | – | Updated project name |
| projectId | string | yes | The unique identifier of the project to update |
No output schema declared.
No examples provided.
updateUseCase ~217
Update an existing use case. All fields are optional — only provided fields will be updated. Use this for manual updates based on human input or agent analysis.
| Name | Type | Req | Description |
|---|---|---|---|
| acceptanceCriteria | array | – | – |
| aiDirectives | object | – | – |
| aiMetadata | object | – | – |
| businessValue | string | – | – |
| description | string | – | Update the description |
| errorHandling | object | – | – |
| flows | array | – | – |
| functionalRequirements | object | – | – |
| implementationRisk | array | – | – |
| interfaces | object | – | – |
| name | string | – | Update the name |
| normative | boolean | – | – |
| primaryActor | string | – | – |
| quality | object | – | – |
| relationships | array | – | – |
| scope | object | – | – |
| stakeholders | array | – | – |
| status | object | – | – |
| tags | array | – | – |
| technicalSurface | object | – | – |
| useCaseId | string | yes | The unique identifier (_id) of the use case to update |
No output schema declared.
No examples provided.
updateUseCaseWithAI ~102
Update a use case with AI-driven changes based on natural language instructions. Use this when you want to make targeted changes to a use case without manually editing fields. Preserves human-reviewed sections by default.
| Name | Type | Req | Description |
|---|---|---|---|
| instructions | string | yes | Natural language instructions for AI-driven changes |
| preserveHumanEdits | boolean | – | Whether to preserve human-reviewed sections |
| useCaseId | string | yes | The unique identifier (_id) of the use case to update |
No output schema declared.
No examples provided.
upsertProjectDomainModel ~265
Add or replace a domain model (class/interface/DTO) in a project's domain catalog. Call this whenever you create or significantly change a TypeScript interface, class, Mongoose schema, Zod schema, or DTO while implementing a feature. Provide every field with its type, required flag, constraints, and the architectural layer (data | dto | domain | response | request | event | other). The model is upserted by name — re-calling with the same name updates it.
| Name | Type | Req | Description |
|---|---|---|---|
| addedBy | string | – | Agent or user identifier who is adding/updating this model (defaults to "system-mcp") |
| description | string | – | What this model represents |
| fields | array | – | Field definitions for this model |
| layer | string | – | Architectural layer: data=DB document, dto=transport, domain=domain object, response/request=API shapes, event=async message, other. |
| name | string | yes | Domain model name (e.g. "UserDocument", "ProjectDto"). Case-sensitive — acts as the unique key for upsert. |
| projectId | string | yes | The _id of the project that owns this domain catalog |
| usedByUseCases | array | – | List of use case IDs that reference this model |
No output schema declared.
No examples provided.
How do I install the H2BIS ProjectBrain MCP server?
H2BIS ProjectBrain MCP runs locally as an npm package, launched with npx -y h2bis-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 · h2bis-mcp
claude mcp add h2bis-dev-h2bis-projectbrain-mcp -- npx -y h2bis-mcp
What is the H2BIS ProjectBrain MCP server?
H2BIS ProjectBrain MCP is listed in the public MCP registry as io.github.h2bis-dev/h2bis-projectbrain-mcp. Connect AI agents to H2BIS ProjectBrain - manage projects, use cases, and capabilities via MCP. This page covers its npm package (h2bis-mcp).
Is the H2BIS ProjectBrain MCP server safe to use?
H2BIS ProjectBrain MCP scores 76 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 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 H2BIS ProjectBrain MCP server expose?
H2BIS ProjectBrain MCP exposes 15 tools: listProjects, getProjectById, createProject, updateProject, upsertProjectDomainModel, and 10 more. Their descriptions and schemas cost roughly 1,737 tokens of context every time the server is loaded.
Is the H2BIS ProjectBrain MCP server still maintained?
H2BIS ProjectBrain MCP is still listed as active in the MCP registry. We last reached this channel on 5 November 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 H2BIS ProjectBrain MCP server under?
H2BIS ProjectBrain MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.