H2BIS ProjectBrain MCP
NPM · H2BIS-MCP · SCANNED AUG 3
Connect AI agents to H2BIS ProjectBrain - manage projects, use cases, and capabilities via MCP.
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 →
Supply Chain Security88
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (117 of 121), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (117 of 121), so this covers what we could see, not the whole tree. 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 117 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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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 · h2bis-mcp
claude mcp add h2bis-dev-h2bis-projectbrain-mcp -- npx -y h2bis-mcp
codex mcp add h2bis-dev-h2bis-projectbrain-mcp -- npx -y h2bis-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"h2bis-dev-h2bis-projectbrain-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"h2bis-mcp"
],
"enabled": true
}
}
} openclaw mcp add h2bis-dev-h2bis-projectbrain-mcp --command npx --arg -y --arg h2bis-mcp
mcp_servers:
h2bis-dev-h2bis-projectbrain-mcp:
command: "npx"
args: ["-y", "h2bis-mcp"] {
"mcpServers": {
"h2bis-dev-h2bis-projectbrain-mcp": {
"command": "npx",
"args": [
"-y",
"h2bis-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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Aug 26 +48
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Schema quality: unverified → good ▲ functional
- Stability: unverified → 0.23 ▲ functional
- Maintenance: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- License: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Licence: MIT functional
- 1 Aug 26 −7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 30 Jul 26 +18
- Dependency health: partial → unverified ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- 28 Jul 26 −18
- Tool coverage: 100 → unverified ▼ functional
- Dependency health: unverified → partial ▲ functional
- First check of Schema quality: unverified functional
- 27 Jul 26 44
First indexed and scored.
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/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 117 packages
117 packages in the resolved dependency tree · 110 deprecated · 35 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
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.