claimseed
NPM · @CLAIMSEED/MCP
Synthetic US medical-billing documents (PDF and ground truth) for testing extractors and agents
Available components
Last scanned (9 hours ago)
Scores higher than 87% of npm 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 Security98
- 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
- 40 of 145 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to claimseed/claimseed). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 1 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1987 tokens (~152/item across 13 items; 6 tools + 7 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 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
- 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 8 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
- Supports UI / widget rendering.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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 +11
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.87 ▲ functional
- 3 Nov 26 −11
- Known CVEs: pass → unverified ▼ security
- Schema quality: 125 → 152 ▼ functional
- Dependency health: 0.87 → unverified ▼ functional
- Package version: 0.4.0 → 0.5.0 functional
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Schema quality: pass → fail ▼ functional
- Stability: unverified → 0.10 ▲ functional
- Package version: 0.3.0 → 0.4.0 functional
- 30 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 29 Oct 26 +18
- Malware scan: pass → unverified ▼ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: pass functional
- First check of Capabilities: pass functional
- First check of Schema quality: pass functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
- First check of Tool coverage: 100 functional
- Package version: 0.1.0 → 0.3.0 functional
- 28 Oct 26 49
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/@claimseed/mcp@0.5.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | claimseed/claimseed |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/claimseed/claimseed/.github/workflows/release.yml@refs/tags/v0.5.0 |
| Rekor log index | 3660805255 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:d06532164188f1b192de9c639a043c50090fa68509a877c88805f10eaf8637ad44879e0c334bfbd0a8810bd52057770f959c2bd156d4e79b0cb6c8abf |
Background: How many MCP packages publish verified provenance →
Dependencies 145 packages
| Packages resolved | 145 |
|---|---|
| Stale | 40 |
| 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 →
degrade_document Render a scanned-looking copy of a document ~392
Render a degraded copy of one document and return it: a flatbed scan, a fax, a phone photo or a low-resolution copy (preset), as an image-only PDF with the specimen band and watermark drawn on top of the degraded pages. The settings come from the seed and are recorded in the ground truth (degradation, degradationParams); the fields are those of the clean document. Returns page images (as many as fit), the ground truth, and the PDF itself when include_pdf is set and it fits. No file is saved.
| Name | Type | Req | Description |
|---|---|---|---|
| from_page | integer | – | first page to return as an image (default 1) |
| include_pdf | boolean | – | also return the degraded PDF itself; it counts toward the same size limit as the page images and is left out, with a note, when it alone is over it |
| layout_variant | string | – | Optional. A layout variant id from this document type's published list, or seeded to pick one from the seed. Applies only to itemized-bill, ppo-eob and hmo-eob. Leave it out for the standard layout,… |
| preset | string | yes | scan (flatbed scan), fax (black and white, standard or fine), photo (phone photo of the page on a table) or low-res |
| preview | string | – | pages returned as images: none, the first (from from_page), or all from from_page on, as many as fit in one result (default all) |
| scenario | string | yes | scenario slug, e.g. baseline-clean (see describe_document_type) |
| seed | string | – | any short string (letters, digits, . _ -); the same seed always gives the same document |
| type | string | yes | document type: msn, itemized-bill, ppo-eob, hmo-eob |
| Name | Type | Req | Description |
|---|---|---|---|
| bytes | number | yes | – |
| degradation | string|null | yes | – |
| groundTruth | object | yes | – |
| groundTruthFile | string|null | yes | – |
| pages | number | yes | – |
| string|null | yes | – | |
| pdfEmbedded | boolean | yes | – |
| preview | object | yes | – |
| scenario | string | yes | – |
| seed | string | yes | – |
| sha256 | string | yes | – |
| type | string | yes | – |
No examples provided.
describe_document_type Describe a document type ~123
Describe one document type: every scenario with its description, period, number of claims, the errors it injects (kind, severity, rule), its decoys (lines that look wrong but follow the rules) and its public sources. It also lists the type's layout variant ids, which layout_variant accepts besides seeded (an empty list for msn, which has one layout). A scenario with neither errors nor decoys is a clean control.
| Name | Type | Req | Description |
|---|---|---|---|
| type | string | yes | document type: msn, itemized-bill, ppo-eob, hmo-eob |
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | – |
| groundTruthSchema | string | yes | – |
| layoutVariants | array | yes | – |
| orientation | string | yes | – |
| scenarios | array | yes | – |
| title | string | yes | – |
| type | string | yes | – |
No examples provided.
generate_data Generate document data ~184
Generate the data and ground truth of one document without rendering it (no file is saved). The same type, scenario and seed always give the same result. Every value is synthetic.
| Name | Type | Req | Description |
|---|---|---|---|
| layout_variant | string | – | Optional. A layout variant id from this document type's published list, or seeded to pick one from the seed. Applies only to itemized-bill, ppo-eob and hmo-eob. Leave it out for the standard layout,… |
| scenario | string | yes | scenario slug, e.g. baseline-clean (see describe_document_type) |
| seed | string | – | any short string (letters, digits, . _ -); the same seed always gives the same document |
| type | string | yes | document type: msn, itemized-bill, ppo-eob, hmo-eob |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
| groundTruth | object | yes | – |
No examples provided.
list_document_types List document types ~29
List the document types claimseed can render, each with a short description and its scenario slugs.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| types | array | yes | – |
No examples provided.
render_document Render a document to PDF ~368
Render one document and return it in the result: its pages as images (as many as fit; from_page shows the rest), the ground truth, the PDF's SHA-256 and page count, and the PDF itself when include_pdf is set and it fits within the size limit. No file is saved. Every page carries specimen markers.
| Name | Type | Req | Description |
|---|---|---|---|
| also | string | – | 835: also write the X12 835 remittance of the same claims (msn, ppo-eob and hmo-eob only), as a file in the workspace or as text in the result |
| from_page | integer | – | first page to return as an image (default 1) |
| include_pdf | boolean | – | also return the PDF itself, embedded in the result; it counts toward the same size limit as the page images and is left out, with a note, when it alone is over it |
| layout_variant | string | – | Optional. A layout variant id from this document type's published list, or seeded to pick one from the seed. Applies only to itemized-bill, ppo-eob and hmo-eob. Leave it out for the standard layout,… |
| preview | string | – | pages returned as images: none, the first (from from_page), or all from from_page on, as many as fit in one result (default all) |
| scenario | string | yes | scenario slug, e.g. baseline-clean (see describe_document_type) |
| seed | string | – | any short string (letters, digits, . _ -); the same seed always gives the same document |
| type | string | yes | document type: msn, itemized-bill, ppo-eob, hmo-eob |
| Name | Type | Req | Description |
|---|---|---|---|
| bytes | number | yes | – |
| degradation | string|null | yes | – |
| groundTruth | object | yes | – |
| groundTruthFile | string|null | yes | – |
| pages | number | yes | – |
| string|null | yes | – | |
| pdfEmbedded | boolean | yes | – |
| preview | object | yes | – |
| remittance | – | yes | – |
| scenario | string | yes | – |
| seed | string | yes | – |
| sha256 | string | yes | – |
| type | string | yes | – |
No examples provided.
verify_document Score an extractor against a document ~404
Score what an extractor or bill auditor reported about one document against its answer key, rebuilt from the type, scenario and seed with this version of claimseed. The report uses the answer key's vocabulary (schema://extractor-output): `fields` maps field paths of documents[0].fields to the values read; `errors` lists flagged errors as { kind, fieldRef or lineRef }. Returns field accuracy with the paths read wrong or missed, error recall and precision, false alarms, and which decoys were flagged. The result names only answer-key paths, kinds and decoy ids, never the text sent. Nothing is rendered or written.
| Name | Type | Req | Description |
|---|---|---|---|
| layout_variant | string | – | Optional. A layout variant id from this document type's published list, or seeded to pick one from the seed. Applies only to itemized-bill, ppo-eob and hmo-eob. Leave it out for the standard layout,… |
| output | object | yes | the extractor's report (schema://extractor-output). What an extractor or bill auditor reports about one claimseed document, for scoring with `claimseed-core verify` or the MCP tool verify_document. I… |
| scenario | string | yes | scenario slug, e.g. baseline-clean (see describe_document_type) |
| seed | string | – | any short string (letters, digits, . _ -); the same seed always gives the same document |
| type | string | yes | document type: msn, itemized-bill, ppo-eob, hmo-eob |
| Name | Type | Req | Description |
|---|---|---|---|
| answerKey | object | yes | – |
| errors | – | yes | – |
| fields | – | yes | – |
No examples provided.
How do I install the claimseed MCP server?
claimseed runs locally as an npm package, launched with npx -y @claimseed/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @claimseed/mcp
claude mcp add claimseed-claimseed -- npx -y @claimseed/mcp
What is the claimseed MCP server?
claimseed is an MCP server listed in the public MCP registry as io.github.claimseed/claimseed. Synthetic US medical-billing documents (PDF and ground truth) for testing extractors and agents. This page covers its npm package (@claimseed/mcp).
Is the claimseed MCP server safe to use?
claimseed scores 85 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. Its build provenance is signed and verified. 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 claimseed MCP server expose?
claimseed exposes 6 tools: list_document_types, describe_document_type, generate_data, render_document, degrade_document, verify_document. Their descriptions and schemas cost roughly 1,500 tokens of context every time the server is loaded.
Is the claimseed MCP server still maintained?
claimseed 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 claimseed MCP server under?
claimseed 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.