LineBreak Gate & Spec Bridge
PYPI · LINEBREAK-GATE
Approved acceptance criteria served over MCP to Claude Code, Cursor, or Codex. Git-only, sealed.
Available components
Last scanned (14 hours ago)
Scores higher than 70% of PyPI servers
Category Testing and QA
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 build step with no custom scripting around it. View diagnostics → Pass
- 2 of 41 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Build provenance is cryptographically sound, but it attests a different repository to the one declared in the registry. Most often the declared URL is simply stale. View diagnostics → Unverified
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 42 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
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 Management70
- Stability observed for 21 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
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.
- 4 Nov 26 −4
- Stability: pass → 0.67 functional
- 30 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 29 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 28 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 27 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 26 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 23 Oct 26 0
- Stability: 0.97 → pass security
- 22 Oct 26 0
- Stability: pass → 0.97 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 5 Nov 2026 · Analysed pypi/linebreak-gate@1.10.3
Provenance Repository mismatch
The attestation is cryptographically sound but binds a different repository to the one the registry declares. Most often the declared URL is simply stale.
| Result | Repository mismatch |
|---|---|
| Ecosystem | pypi |
| Reason | Repository mismatch |
| Discovered via | Registry attestation endpoint |
| Source repo | Baktun-Studio/linebreak |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Baktun-Studio/linebreak/.github/workflows/publish-gate.yml@refs/heads/main |
| Rekor log index | 2421581340 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:2b5613eb62d3ae7679036d47a106eb4ad062ad50089c92b3ba0c16727413ad33 |
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.
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
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 73 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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 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 LineBreak Gate & Spec Bridge MCP server under?
LineBreak Gate & Spec Bridge declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.