PromptBranch
NPM · @PROMPTBRANCH/MCP · SCANNED SEP 24
Local-first MCP server for versioning, searching, evaluating, and improving AI prompts.
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
- 32 of 104 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- 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 5 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 561 tokens (~93/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 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
- 67% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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 PromptBranch MCP server?
PromptBranch runs locally as an npm package, launched with npx -y @promptbranch/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 · @promptbranch/mcp
claude mcp add promptbranch-promptbranch -- npx -y @promptbranch/mcp
{
"mcpServers": {
"promptbranch-promptbranch": {
"command": "npx",
"args": [
"-y",
"@promptbranch/mcp"
]
}
}
} {
"servers": {
"promptbranch-promptbranch": {
"command": "npx",
"args": [
"-y",
"@promptbranch/mcp"
]
}
}
} codex mcp add promptbranch-promptbranch -- npx -y @promptbranch/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"promptbranch-promptbranch": {
"type": "local",
"command": [
"npx",
"-y",
"@promptbranch/mcp"
],
"enabled": true
}
}
} openclaw mcp add promptbranch-promptbranch --command npx --arg -y --arg @promptbranch/mcp
mcp_servers:
promptbranch-promptbranch:
command: "npx"
args: ["-y", "@promptbranch/mcp"] {
"McpServers": {
"promptbranch-promptbranch": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@promptbranch/mcp"
]
}
}
} assistant mcp add promptbranch-promptbranch -t stdio -c npx -a -y @promptbranch/mcp
{
"mcpServers": {
"promptbranch-promptbranch": {
"command": "npx",
"args": [
"-y",
"@promptbranch/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.
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 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 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 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 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
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 24 Sept 2026 · Analysed npm/@promptbranch/mcp@0.2.6
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 104 packages
| Packages resolved | 104 |
|---|---|
| Stale | 31 |
| No linked repository | 1 |
| 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 →
add_note ~66
Attach a freeform note to a prompt (or a specific version of it).
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | – |
| prompt | string | yes | Prompt title (exact or unique substring) or id |
| versionId | string | – | Specific version id; omit for a prompt-level note |
No output schema declared.
No examples provided.
get_prompt ~150
Fetch and render a prompt. If status is needs_input, do not execute content: ask the user for every missingVariables value, then call get_prompt again with variables. Execute content only when status is ready. Defaults to the current (preferred) version; pin with version and/or branch.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | – | Branch name; defaults to the current version's branch |
| prompt | string | yes | Prompt title (exact or unique substring) or id |
| variables | object | – | Values for {{variables}}. If the response says needs_input, ask the user for every missing variable and call get_prompt again. |
| version | integer | – | Per-branch version number; defaults to the current version |
No output schema declared.
No examples provided.
list_prompts ~36
List prompts in the library, optionally filtered by collection or tag.
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | – | – |
| tag | string | – | – |
No output schema declared.
No examples provided.
report_run ~133
Report that a prompt version was used: which tool/model ran it, the outcome rating (1–5) and a short result summary.
| Name | Type | Req | Description |
|---|---|---|---|
| metrics | object | – | Arbitrary structured metrics (tokens, latency…) |
| model | string | – | – |
| outcomeRating | integer | – | – |
| prompt | string | yes | Prompt title (exact or unique substring) or id |
| resultSummary | string | – | – |
| tool | string | yes | Tool that ran the prompt, e.g. 'kimi-cli', 'mcp' |
| version | integer | – | Per-branch version number; defaults to the current version |
No output schema declared.
No examples provided.
search_prompts ~75
Full-text search over prompt titles, descriptions, tags, notes and version content.
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | – | Restrict to this collection (name) |
| limit | integer | – | Max results (default 10) |
| query | string | yes | – |
| tag | string | – | Restrict to prompts carrying this tag (name) |
No output schema declared.
No examples provided.
suggest_variation ~101
Propose a rewritten version of a prompt. Creates a PENDING suggestion that a human must approve in the PromptBranch app before it becomes usable — agents propose, humans approve.
| Name | Type | Req | Description |
|---|---|---|---|
| baseVersion | integer | – | Version number to base the suggestion on; defaults to current |
| newContent | string | yes | – |
| prompt | string | yes | Prompt title (exact or unique substring) or id |
| rationale | string | yes | Why this change improves the prompt |
No output schema declared.
No examples provided.
What is the PromptBranch MCP server?
PromptBranch is an MCP server listed in the public MCP registry as io.github.PromptBranch/promptbranch. Local-first MCP server for versioning, searching, evaluating, and improving AI prompts. This page covers its npm package (@promptbranch/mcp).
Is the PromptBranch MCP server safe to use?
PromptBranch scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 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 PromptBranch MCP server expose?
PromptBranch exposes 6 tools: get_prompt, search_prompts, list_prompts, report_run, add_note, suggest_variation. Their descriptions and schemas cost roughly 561 tokens of context every time the server is loaded.
Is the PromptBranch MCP server still maintained?
PromptBranch is still listed as active in the MCP registry. We last reached this channel on 24 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 PromptBranch MCP server under?
PromptBranch declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.