io.github.flatbread-cli/flatbread
NPM · FLATBREAD-CLI
Share a coding agent's session as one link, secrets redacted first; pull another run's brief.
Available components
Last scanned (10 hours ago)
Scores higher than 33% of npm servers
Category Developer Tools
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
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency35
- 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 5 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 744 tokens (~248/item across 3 items; 3 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 1 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 51
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 5 Nov 2026 · Analysed npm/flatbread-cli@0.9.8
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 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
flatbread_get_brief Get a run's execution brief ~104
Fetch the execution brief of one Flatbread run: what was asked, how the human steered it, each blocker and the fix (so you do not repeat it), what the tests said, and the diff. Every quote is the run's own text. Pass a run ID from flatbread_search_traces, or a flatbread.io/r/<id> link.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | A run ID, or a /r/<id> link |
No output schema declared.
No examples provided.
flatbread_search_traces Search Flatbread runs ~150
Search recorded AI coding-agent runs (your own Flatbread account's, and public runs on flatbread.io) for one that already did a similar task. Use it BEFORE starting a task that someone may have solved before, or after hitting an error, to find a run that hit the same wall. Returns run IDs; pass one to flatbread_get_brief for what that run learned.
| Name | Type | Req | Description |
|---|---|---|---|
| harness | string | – | Only runs from this agent harness |
| query | string | – | Two to four words from the task or the error. Runs with every word in their title or ID come first; when none has them all, the closest are listed, marked with how many words they share |
No output schema declared.
No examples provided.
flatbread_share Share this run ~374
Share the session you are in now as a Flatbread run. Call it when the user says "share this run", "flatbread share", "share to flatbread" or anything like it. It finds this session, leaves the share request out, opens a review page with every secret redacted by default, and returns its link at once - give the user that link: it is uploaded when the user presses Confirm there, which shares it to their Flatbread account. That press is the user's to make, never yours. Always pass cwd and suggested_title. For only part of a long session ("share from prompt 4 to 8"), pass from and to_prompt.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Your current working directory, as an absolute path. It is how this session is found when the server was started somewhere else |
| from | string | – | Start at this prompt: its number ("3"), or words from it. Leave out to start at the first |
| harness | string | – | Which agent you are, only when you are not Claude Code or Codex |
| redact_terms | array | – | Words or phrases to redact everywhere in the run, case-insensitive: a codename, a client, an internal host the user named. Secrets the scanner knows are redacted already |
| suggested_title | string | – | A clean 5 to 10 word engineering title for what this run accomplished, e.g. "Fix retry backoff in the upload client". Write it yourself: the first prompt is often "continue" or a pasted error. At mos… |
| to_prompt | string | – | End at this prompt: its number ("8"), or words from it. Leave out to end at the last prompt before this share request |
No output schema declared.
No examples provided.
How do I install the io.github.flatbread-cli/flatbread MCP server?
io.github.flatbread-cli/flatbread runs locally as an npm package, launched with npx -y flatbread-cli. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · flatbread-cli
claude mcp add flatbread-cli-flatbread -- npx -y flatbread-cli
What is the io.github.flatbread-cli/flatbread MCP server?
io.github.flatbread-cli/flatbread is an MCP server listed in the public MCP registry as io.github.flatbread-cli/flatbread. Share a coding agent's session as one link, secrets redacted first; pull another run's brief. This page covers its npm package (flatbread-cli).
Is the io.github.flatbread-cli/flatbread MCP server safe to use?
io.github.flatbread-cli/flatbread scores 66 out of 100 on VerifyMCP. We found no known CVEs affecting 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 io.github.flatbread-cli/flatbread MCP server expose?
io.github.flatbread-cli/flatbread exposes 3 tools: flatbread_search_traces, flatbread_get_brief, flatbread_share. Their descriptions and schemas cost roughly 628 tokens of context every time the server is loaded.
Is the io.github.flatbread-cli/flatbread MCP server still maintained?
io.github.flatbread-cli/flatbread 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.