LineBreak Gate & Spec Bridge
PYPI · LINEBREAK-GATE · SCANNED SEP 21
Approved acceptance criteria served over MCP to Claude Code, Cursor, or Codex. Git-only, sealed.
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
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 2 of 41 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- 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
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 428 tokens (~71/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 Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
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 7 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 LineBreak Gate & Spec Bridge MCP server?
LineBreak Gate & Spec Bridge runs locally as a PyPI package, launched with uvx linebreak-gate. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · linebreak-gate
claude mcp add com-linebreakapp-linebreak-gate -- uvx linebreak-gate
{
"mcpServers": {
"com-linebreakapp-linebreak-gate": {
"command": "uvx",
"args": [
"linebreak-gate"
]
}
}
} {
"servers": {
"com-linebreakapp-linebreak-gate": {
"command": "uvx",
"args": [
"linebreak-gate"
]
}
}
} codex mcp add com-linebreakapp-linebreak-gate -- uvx linebreak-gate
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-linebreakapp-linebreak-gate": {
"type": "local",
"command": [
"uvx",
"linebreak-gate"
],
"enabled": true
}
}
} openclaw mcp add com-linebreakapp-linebreak-gate --command uvx --arg linebreak-gate
mcp_servers:
com-linebreakapp-linebreak-gate:
command: "uvx"
args: ["linebreak-gate"] {
"McpServers": {
"com-linebreakapp-linebreak-gate": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"linebreak-gate"
]
}
}
} assistant mcp add com-linebreakapp-linebreak-gate -t stdio -c uvx -a linebreak-gate
{
"mcpServers": {
"com-linebreakapp-linebreak-gate": {
"command": "uvx",
"args": [
"linebreak-gate"
]
}
}
} 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.
- 21 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.
- 19 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.
- 18 Sept 26 −3
- Stability: pass → 0.80 functional
- Package version: 1.10.2 → 1.10.3 functional
- 17 Sept 26 0
- Stability: 0.97 → pass security
- 16 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.
- 15 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 14 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- 13 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- Package version: 1.10.2 → 1.10.3 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 21 Sept 2026 · Analysed pypi/linebreak-gate@1.10.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 41 packages
| Packages resolved | 41 |
|---|---|
| Stale | 1 |
| 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 →
check_story ~70
Run this story's acceptance criteria against the working tree with the SAME engine as the merge gate (`linebreak-gate check`). Returns pass | fail | needs-signoff per criterion — verify your work here BEFORE pushing instead of discovering failures at the merge.
| Name | Type | Req | Description |
|---|---|---|---|
| story_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_story ~66
One approved story in full: title, epic, and every acceptance criterion with its id, statement, and check type (build | tests | command | manual). Read this BEFORE implementing the story — the criteria are the approved definition of done.
| Name | Type | Req | Description |
|---|---|---|---|
| story_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_stories ~57
All approved stories in this repository: id, title, epic, local status (todo|doing|review|done), and how many acceptance criteria each carries. The list IS the approved scope — nothing else is in spec.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
next_story ~35
The next approved story that is not yet done, per local story state. Use this to pick up work without guessing at priorities.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
set_story_status ~69
Record story progress: status is doing | review | done. Writes LOCAL story state only (the repo's tracker-sync artifact) — never a configured external tracker, and never the approved criteria.
| Name | Type | Req | Description |
|---|---|---|---|
| comment | – | – | – |
| status | string | yes | – |
| story_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
spec_status ~46
Is there an approved spec bundle: version, source phase, approver, story count, and the approval signature state (verified | invalid | signed-unverified | unsigned), verified entirely offline.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
What is the LineBreak Gate & Spec Bridge MCP server?
LineBreak Gate & Spec Bridge is an MCP server listed in the public MCP registry as com.linebreakapp/linebreak-gate. Approved acceptance criteria served over MCP to Claude Code, Cursor, or Codex. Git-only, sealed. This page covers its PyPI package (linebreak-gate).
Is the LineBreak Gate & Spec Bridge MCP server safe to use?
LineBreak Gate & Spec Bridge scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. 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 LineBreak Gate & Spec Bridge MCP server expose?
LineBreak Gate & Spec Bridge exposes 6 tools: list_stories, get_story, next_story, set_story_status, check_story, spec_status. Their descriptions and schemas cost roughly 343 tokens of context every time the server is loaded.
Is the LineBreak Gate & Spec Bridge MCP server still maintained?
LineBreak Gate & Spec Bridge is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.