Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

md-feedback

NPM · MD-FEEDBACK · SCANNED AUG 3

Review markdown plans before AI agents build. Annotate, gate-check, apply fixes, session handoffs.

Available components

−10 this week 66 Trust /100
Trust breakdown (6 categories)

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 →

Supply Chain Security87
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency32
Schema Quality & AI Usability75
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 2116 tokens (~78/item across 27 items; 27 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · md-feedback

# add to Claude Code
claude mcp add yeominux-md-feedback -- npx -y md-feedback
# add to Codex CLI
codex mcp add yeominux-md-feedback -- npx -y md-feedback
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "yeominux-md-feedback": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "md-feedback"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add yeominux-md-feedback --command npx --arg -y --arg md-feedback
# ~/.hermes/config.yaml
mcp_servers:
  yeominux-md-feedback:
    command: "npx"
    args: ["-y", "md-feedback"]
// mcp.json
{
  "mcpServers": {
    "yeominux-md-feedback": {
      "command": "npx",
      "args": [
        "-y",
        "md-feedback"
      ]
    }
  }
}
Changelog

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.

  • 2 Aug 26 +61
    • Provenance: unverified → fail security
    • Known CVEs: unverified → partial security
    • Install scripts: unverified → pass security
    • Malware scan: unverified → pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • License: unverified → fail functional
    • Security disclosure: unverified → fail functional
    • Maintenance: unverified → pass functional
    • Stability: unverified → 0.20 functional
    • Dependency health: unverified → partial functional
    • MCP protocol: unverified → pass functional
    • Tool coverage: unverified → 100 functional
    • Licence: SUL-1.0 functional
  • 1 Aug 26 −30
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Security disclosure: fail → unverified functional
    • Capabilities: pass → unverified functional
    • Tool coverage: 100 → unverified functional
  • 31 Jul 26 −5
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 −36
    • Known CVEs: partial → unverified security
    • Malware scan: pass → unverified security
    • Provenance: fail → unverified security
    • Install scripts: pass → unverified security
    • License: fail → unverified functional
    • Dependency health: partial → unverified functional
    • Maintenance: pass → unverified functional
    • Licence: SUL-1.0 functional
  • 27 Jul 26 +51
    • Provenance: unverified → fail security
    • Known CVEs: unverified → partial security
    • Install scripts: unverified → pass security
    • License: unverified → fail functional
    • Security disclosure: unverified → fail functional
    • Maintenance: unverified → pass functional
    • Tool coverage: unverified → 100 functional
    • First check of Tool coverage: 100 functional
    • First check of Schema quality: good functional
    • First check of Schema quality: pass functional
    • First check of Schema quality: fail functional
    • Licence: SUL-1.0 functional
  • 26 Jul 26 25

    First indexed and scored.

    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

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 3 Aug 2026 · Analysed npm/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 95 packages

95 packages in the resolved dependency tree · 95 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 27 exposed · ~2,116 tokens

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.

Tool Tokens
advance_workflow_phase ~63

Advance workflow phase in strict sequence: scope -> root_cause -> implementation -> verification.

NameTypeReqDescription
filestringyesPath to the annotated markdown file
notestringOptional transition note
toPhasestringyesNext phase to move to

No output schema declared.

No examples provided.

apply_memo ~290

Apply an implementation action to a memo. Supports text_replace (requires occurrence or replaceAll when oldText has multiple matches; optional section-scoped propagation), file_patch (applies unified diff patch — snapshot saved first), and file_create (create a new file). Creates a snapshot before modification, records the implementation, and updates memo status to needs_review.

NameTypeReqDescription
actionstringyesType of implementation action
contentstringFor file_create: the file content to write
dryRunbooleanIf true, return preview without writing
filestringyesPath to the annotated markdown file
memoIdstringyesThe memo ID to apply implementation to
newTextstringFor text_replace: the replacement text
occurrenceintegerFor text_replace: which occurrence to replace (1-indexed). Required when oldText appears multiple times unless replaceAll=true
oldTextstringFor text_replace: the text to find and replace
patchstringFor file_patch: unified diff patch content
replaceAllbooleanFor text_replace: replace all occurrences instead of one
scopestringFor text_replace: replacement scope (body = whole document body, section = heading section around memo anchor)
targetFilestringFor file_patch/file_create: target file path

No output schema declared.

No examples provided.

approve_checkpoint ~68

Approve a pending high-risk checkpoint. Grants one execution for the approved tool.

NameTypeReqDescription
approvedBystringyesApprover identity
filestringyesPath to the annotated markdown file
reasonstringyesApproval rationale
toolstringyesTool name being approved

No output schema declared.

No examples provided.

batch_apply ~68

Apply multiple implementation operations in a single transaction. Parses the document once, applies all operations sequentially, then writes once. Each operation follows the same format as apply_memo.

NameTypeReqDescription
filestringyesPath to the annotated markdown file
operationsarrayyesArray of operations to apply

No output schema declared.

No examples provided.

create_annotation ~143

Create a new review annotation on a markdown file. Finds the anchor text in the document and attaches a review memo. Auto-creates a quality gate and updates cursor.

NameTypeReqDescription
anchorTextstringyesThe exact text in the document to annotate (must exist in the file)
filestringyesPath to the annotated markdown file
occurrenceintegerWhich occurrence of anchorText to annotate (1-indexed, default 1). Use when the same text appears multiple times.
textstringyesThe review feedback or note to attach
typestringyesfix = needs change, question = needs clarification, highlight = mark for reference

No output schema declared.

No examples provided.

create_checkpoint ~59

Create a review checkpoint in an annotated markdown file. Records current annotation counts and reviewed sections.

NameTypeReqDescription
filestringyesPath to the annotated markdown file
notestringyesCheckpoint note (e.g., "Phase 1 review done")

No output schema declared.

No examples provided.

evaluate_gates ~43

Evaluate all gates in a markdown file against current memo statuses. Returns updated gate statuses without modifying the file.

NameTypeReqDescription
filestringyesPath to the annotated markdown file

No output schema declared.

No examples provided.

export_review ~92

Export review feedback in a format optimized for a specific AI coding tool. Targets: claude-code, cursor, codex, copilot, cline, windsurf, roo-code, gemini, antigravity, generic, handoff. Returns formatted markdown ready to save to the appropriate file.

NameTypeReqDescription
filestringyesPath to the annotated markdown file
targetstringyesTarget AI tool format

No output schema declared.

No examples provided.

generate_handoff ~61

Generate a structured handoff document from an annotated markdown file. Anti-compression format: explicit fields, numbers, lists only.

NameTypeReqDescription
filestringyesPath to the annotated markdown file
targetstringOutput format target (default: standalone)

No output schema declared.

No examples provided.

get_checkpoints ~31

List all checkpoints in an annotated markdown file.

NameTypeReqDescription
filestringyesPath to the annotated markdown file

No output schema declared.

No examples provided.

get_document_structure ~78

Parse an annotated markdown file and return v0.4.0 ReviewDocument metadata. By default bodyMd is omitted to reduce context size; set includeBody=true only when full body is required.

NameTypeReqDescription
filestringyesPath to the annotated markdown file
includeBodybooleanInclude full bodyMd content (larger payload)

No output schema declared.

No examples provided.

get_memo_changes ~80

Get the implementation history and progress for a memo. Returns all MemoImpl records and progress entries from .md-feedback/progress.json. If memoId is omitted, returns all changes.

NameTypeReqDescription
filestringyesPath to the annotated markdown file
memoIdstringOptional memo ID to filter by — if omitted, returns all changes

No output schema declared.

No examples provided.

get_policy_status ~20

Return current runtime policy profile and memo-action routing rules.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_review_status ~65

Get current review session status: annotation counts, checkpoints, and reviewed sections. Summary-only — returns counts and metadata, not individual memos. Use list_annotations for memo details or get_document_structure for the full parse.

NameTypeReqDescription
filestringyesPath to the annotated markdown file

No output schema declared.

No examples provided.

get_severity_status ~36

Return memo severity overrides and unresolved blocking memo IDs for the document.

NameTypeReqDescription
filestringyesPath to the annotated markdown file

No output schema declared.

No examples provided.

get_workflow_status ~34

Return current workflow phase and transition history for a document.

NameTypeReqDescription
filestringyesPath to the annotated markdown file

No output schema declared.

No examples provided.

link_artifacts ~75

Link file artifacts (source files, configs, etc.) to a memo. Creates a MemoArtifact record in the document.

NameTypeReqDescription
filestringyesPath to the annotated markdown file
filesarrayyesArray of relative file paths to link
memoIdstringyesThe memo ID to link artifacts to

No output schema declared.

No examples provided.

list_annotations ~74

List all annotations (USER_MEMO comments) in a markdown file. Returns structured array with id, type, status, owner, text, and color. Lightweight — returns only memo data, no document body or sections. Use get_document_structure for the full parse.

NameTypeReqDescription
filestringyesPath to the annotated markdown file

No output schema declared.

No examples provided.

list_documents ~63

List markdown files in the workspace. Optionally filter to only files that already contain annotations.

NameTypeReqDescription
annotatedOnlybooleanIf true, return only files containing USER_MEMO/HIGHLIGHT_MARK annotations
maxFilesintegerMaximum number of files to return

No output schema declared.

No examples provided.

pickup_handoff ~42

Parse an existing handoff document to resume a review session. Returns structured data for session continuity.

NameTypeReqDescription
filestringyesPath to the handoff markdown file

No output schema declared.

No examples provided.

request_approval_checkpoint ~67

Create an approval checkpoint for a high-risk action before execution.

NameTypeReqDescription
filestringyesPath to the annotated markdown file
reasonstringyesReason for approval request
toolstringyesHigh-risk tool name (e.g., batch_apply, rollback_memo)

No output schema declared.

No examples provided.

respond_to_memo ~90

Add an AI response to a memo annotation. Inserts a REVIEW_RESPONSE block into the markdown file directly below the memo's anchor text. Automatically sets the memo status to "needs_review" for human approval.

NameTypeReqDescription
filestringyesPath to the annotated markdown file
memoIdstringyesThe memo ID to respond to
responsestringyesThe response text (markdown supported)

No output schema declared.

No examples provided.

rollback_memo ~72

Rollback the latest implementation for a memo. Reverses text_replace operations (swaps before/after), marks the impl as reverted, and sets the memo status back to open.

NameTypeReqDescription
filestringyesPath to the annotated markdown file
memoIdstringyesThe memo ID to rollback

No output schema declared.

No examples provided.

set_memo_severity ~67

Set severity override for a memo. Defaults remain: fix=blocking, question/highlight=non_blocking.

NameTypeReqDescription
filestringyesPath to the annotated markdown file
memoIdstringyesMemo ID to classify
severitystringyesSeverity override

No output schema declared.

No examples provided.

update_cursor ~98

Update the plan cursor position in a markdown file. The cursor tracks "where we are" in a plan. Only one cursor per document.

NameTypeReqDescription
filestringyesPath to the annotated markdown file
nextActionstringyesDescription of the next action to take
stepstringyesCurrent step (e.g., "3/7" or "Phase 2")
taskIdstringyesCurrent task ID

No output schema declared.

No examples provided.

update_memo_progress ~120

Update the progress of a memo with a status change and message. Writes progress to .md-feedback/progress.json and updates the memo status. Terminal statuses (done, failed) require human approval via VS Code.

NameTypeReqDescription
filestringyesPath to the annotated markdown file
memoIdstringyesThe memo ID to update progress for
messagestringyesProgress message describing what was done or what failed
statusstringyesNew progress status. Terminal statuses (done, failed) require human approval via VS Code.

No output schema declared.

No examples provided.

update_memo_status ~117

Update the status of a memo annotation. Writes the change back to the markdown file. Returns the updated memo. Terminal statuses (answered, done, failed, wontfix) require human approval via VS Code.

NameTypeReqDescription
filestringyesPath to the annotated markdown file
memoIdstringyesThe memo ID to update
ownerstringOptionally change the owner
statusstringyesNew status. Terminal statuses (answered, done, failed, wontfix) require human approval via VS Code.

No output schema declared.

No examples provided.