TARGET Checklist MCP server

Read from the package source without running it. The installed server may list more.

• aggregate_corpus

  Roll up many assessments into per-item completeness rates plus coverage denominators (supplement-retrieval status, full-text availability, evidence- resolution rate). Pass an array of assessment objects as `assessments`, or use_session=true to aggregate every assessment produced this session. The completeness rates are only as valid as the sample and are not yet gold-standard calibrated.

• assess_manuscript

  Assess a manuscript against all applicable TARGET leaves in one batched pass. `document` is a path, raw text, or a text_sha256 returned by parse_manuscript.

• build_coding_sheet

  Emit blank per-paper coding sheets for human gold-standard coding: one row per applicable leaf with its intent and verdict boundaries and empty verdict/evidence/note fields. blind=true (default) withholds the instrument's verdict so coders are not anchored — use blind coding for the primary reference standard. Pass `assessments` or use_session=true.

• get_checklist

  Return the encoded TARGET checklist spec: 39 scoreable leaf subitems (grouped into the 21 published items) with intent, assessor notes, signal terms, pairing links, and applicability rules. Pass a version id to pin; omit for the current default.

• parse_manuscript

  PRIMARY entry point: parse a manuscript into a SectionMap with character-offset, source-tagged section spans.

• parse_pmcid

  CONVENIENCE / BATCH entry point: retrieve an open-access article from Europe PMC by PMCID and parse it. Reach for this in the corpus/batch case (no file in hand) or to auto-fetch an open-access paper's supplement; for a single manuscript you were given, use parse_manuscript instead. Fetches JATS main text plus (if available) PMC-hosted supplementary files, merged into one source-tagged SectionMap.

• render_checklist

  Render a finalized assessment as the completed TARGET checklist form: the 21 published items (39 leaf rows, in checklist order) with the published item wording and a Location-reported column derived from the resolved evidence spans. The default enriched view adds, per leaf, the instrument's verdict and the verbatim evidence quote that justifies the location; view='official' strips to the published

• render_checklist_docxwrite action

  Write the completed TARGET checklist to a Word (.docx) file and return it. Same content as render_checklist (published item wording + a Location-reported column from the resolved evidence spans; enriched view adds verdict and evidence), serialized as a submission-ready landscape table, one per manuscript section. Pass a full `assessment` object or the `manuscript_id` of one assessed this session.

• render_checklist_html

  Render the completed TARGET checklist as a self-contained HTML page — same content as render_checklist, styled to the Black Swan Causal Labs identity (canvas ground, one aligned table, verdict pills), viewable in any browser on any host. Returns the HTML string in `html` (show it inline or publish it as an artifact) and the same bytes as base64 in `content_base64` (decode and save as an .html file

• submit_scaffold_verdictswrite action

  Scaffold-mode completion: validate verdicts produced by the calling agent (leaf coverage, verdict vocabulary, mandatory verbatim evidence quotes resolved to spans) and return the stamped assessment TOGETHER WITH the finished, rendered deliverable. `items` is the verdict array from the forced tool call — one object per leaf with `id`, `verdict`, `confidence`, `rationale`, and (for reported/partial)

• validate_against_gold

  Compute per-leaf agreement between instrument assessments and human gold-standard codings: raw agreement, Cohen's kappa, Gwet's AC1, and binary (reported-vs-rest) sensitivity/specificity with the human coding as the reference standard, plus a span-keyed disagreement list for adjudication. Agreement is reported PER LEAF; the pooled figure is orientation only. Both arguments are arrays of assessment

• Code scan13 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancelast push 71 days ago12/15
• Maintainer identitynamespace and repository owner differ4/10

Safety score

82/100

higher than 63% of 48,255 servers

Tools

11

the typical server has 7

Tools that change things

18%

typical: 0%. Fewer write tools means less an agent can break

Downloads a week

30

more than 18% of 12,191 servers with a package

Grade history

• 2026-11-01downgradeA → Bscore 82

TARGET Checklist MCP: common questions

Is TARGET Checklist MCP server safe?

Mostly: it is graded B (82/100). Read the TARGET Checklist MCP safety report

How do I install TARGET Checklist MCP?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does TARGET Checklist MCP need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is TARGET Checklist MCP maintained?

The last commit was 73 days ago (2026-08-23). The latest release is v0.2.0.

How does TARGET Checklist MCP compare with other MCP servers?

safety score 82/100 (higher than 63% of 48,255 servers); tools 11 (the typical server has 7); tools that change things 18% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.