Markdown Pipeline
PYPI · MDPIPELINE
Your team's Jira as clean Markdown files, kept current for your AI agent. Local and read-only.
Available components
Last scanned (18 hours ago)
Scores higher than 56% of PyPI servers
Category Project Management
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 Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs uv_build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 32 dependencies flagged as unhealthy. 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 (Apache-2.0).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 480 tokens (~80/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 Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 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
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 current MCP spec version (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 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.1.15 → 0.1.16 functional
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 66
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 4 Nov 2026 · Analysed pypi/mdpipeline@0.1.16
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | uv_build |
Background: Why install scripts are a supply-chain risk →
Dependencies 32 packages
| Packages resolved | 32 |
|---|---|
| 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 →
list ~46
List the folders and Markdown files under path_prefix (default: the top level: the output folders, raw/ and wiki/), with a provenance summary per file.
| Name | Type | Req | Description |
|---|---|---|---|
| path_prefix | – | – | – |
No output schema declared.
No examples provided.
read ~48
Read one Markdown file of the brain (path relative to the brain, e.g. 'raw/projects/biz/pricing.md'). Returns the content and its parsed provenance.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | – |
No output schema declared.
No examples provided.
recent_changes ~86
What changed in the brain's files? The files created, changed or deleted by successful syncs since a time (ISO date or time, default: the last 24 hours), merged per file, with counts. Use it for 'what changed since yesterday?'. pipeline narrows it to one pipeline.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| pipeline | – | – | – |
| since | – | – | – |
No output schema declared.
No examples provided.
search ~114
Keyword/full-text search over the brain's Markdown (the files its pipelines wrote, plus raw/ and wiki/). Returns ranked files with matching passages and each file's provenance. Covers every pipeline target that has local files: files of other targets have paths like '@pipeline/raw/...' and a 'target' label. Use quotes for an exact phrase. path_prefix (e.g. 'raw/projects/biz') narrows the search.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| path_prefix | – | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
sync ~75
Refresh the brain: sync one pipeline (or all pipelines when none is given) from its source folders into the output folder. If the big-change guard blocks the sync, nothing is written and the result is 'blocked': only the owner can approve it in the UI or CLI. This tool cannot approve or force.
| Name | Type | Req | Description |
|---|---|---|---|
| pipeline | – | – | – |
No output schema declared.
No examples provided.
sync_status ~53
How fresh is the brain? Per pipeline: status, last run (time, result, counts), conflicts, big-change guard state and age since the last successful sync, plus the overall brain age.
| Name | Type | Req | Description |
|---|---|---|---|
| pipeline | – | – | – |
No output schema declared.
No examples provided.
How do I install the Markdown Pipeline MCP server?
Markdown Pipeline runs locally as a PyPI package, launched with uvx mdpipeline. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mdpipeline
claude mcp add markdown-pipeline-mdpipeline -- uvx mdpipeline
What is the Markdown Pipeline MCP server?
Markdown Pipeline is an MCP server listed in the public MCP registry as io.github.markdown-pipeline/mdpipeline. Your team's Jira as clean Markdown files, kept current for your AI agent. Local and read-only. This page covers its PyPI package (mdpipeline).
Is the Markdown Pipeline MCP server safe to use?
Markdown Pipeline scores 53 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 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 Markdown Pipeline MCP server expose?
Markdown Pipeline exposes 6 tools: search, read, list, sync_status, recent_changes, sync. Their descriptions and schemas cost roughly 422 tokens of context every time the server is loaded.
Is the Markdown Pipeline MCP server still maintained?
Markdown Pipeline is still listed as active in the MCP registry. We last reached this channel on 4 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 Markdown Pipeline MCP server under?
Markdown Pipeline 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.