io.github.michal-niedzwiedzki/visimark
NPM · VISIMARK-MCP
MCP server for VisiMark, a document integrity layer for Markdown: checks numbers against formulas.
Available components
Last scanned (22 hours ago)
Scores higher than 99% 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
- 0 of 2 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to michal-niedzwiedzki/visimark). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 18 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1234 tokens (~94/item across 13 items; 8 tools + 5 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "visimark_eval" implies "eval" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
- An AI judge read all 10 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
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.
- 28 Oct 26 0
- Stability: 0.97 → pass security
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 0
- Tool safety: pass → unverified ▼ security
- Stability: 0.60 → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Package version: 0.4.0 → 0.4.1 functional
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
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 npm/visimark-mcp@0.4.1
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 | michal-niedzwiedzki/visimark |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/michal-niedzwiedzki/visimark/.github/workflows/release.yml@refs/tags/v0.4.1 |
| Rekor log index | 3286297637 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:4a39986611f4a5190fb37506030c8f5eb7d255c5e24e3db06704c2525662e2717ca2de3c9e563a7d899f54f94820ab5d326ea7ffb1ac59a2caf8d7c5d |
Background: How many MCP packages publish verified provenance →
Dependencies 2 packages
| Packages resolved | 2 |
|---|---|
| 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 →
visimark_check Check a VisiMark document ~119
Verify that every computed number in a Markdown document still agrees with the formula that produced it, and report what does not. Findings are a successful result, not an error. A document given as `content` has no directory, so imports and generated artifacts cannot be verified; `skipped` names the ones that were not checked.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | The document as text, for a draft that is not on disk. Give this or `path`, never both. |
| path | string | – | Path to a Markdown document on disk. |
No output schema declared.
No examples provided.
visimark_eval Evaluate a VisiMark document ~167
Evaluate a document and return its values, its assertions and its charts. Give `get` to select a single named value. Give `scenarioPath` or `scenarioContent` to substitute parameters and see what moves — a draft scenario against a draft document, with no temp file. A false assertion is a successful result reporting problems.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | The document as text, for a draft that is not on disk. Give this or `path`, never both. |
| get | string | – | One value's qualified name, e.g. `lines.gross_total`. |
| path | string | – | Path to a Markdown document on disk. |
| scenarioContent | string | – | A scenario as JSON text. |
| scenarioPath | string | – | Path to a scenario JSON file. |
No output schema declared.
No examples provided.
visimark_explain Explain a VisiMark document's structure ~102
Describe what a document declares: its sheets, input columns, computed rules, anchored scalars, derived precision and imports. Give `sheet` to narrow it.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | The document as text, for a draft that is not on disk. Give this or `path`, never both. |
| path | string | – | Path to a Markdown document on disk. |
| sheet | string | – | A sheet id, without the leading `#`. |
No output schema declared.
No examples provided.
visimark_fmt Plan a VisiMark repair ~163
Plan the edits that would bring a document's stored numbers back into agreement with its formulas, and name the generated artifacts it would write. Nothing is written: pass the returned plan to `visimark_fmt_apply` to land it. It repairs stale computed values, anchors and generated artifacts, and nothing else — never prose, never a column with no rule, never any other finding class. A document given as `content` has no directory, so imports and generated artifacts cannot be verified; `skipped` names the ones that were not checked.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | The document as text, for a draft that is not on disk. Give this or `path`, never both. |
| path | string | – | Path to a Markdown document on disk. |
No output schema declared.
No examples provided.
visimark_fmt_apply Apply a VisiMark repair ~117
Land the plan `visimark_fmt` returned: splice the document's computed cells and anchors, and write the generated artifacts it named. Refused if the document changed since the plan was computed, and refused entirely unless the operator started the server with `--allow-write` and the host declared a root.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | The document to write. There is nothing to apply to a string. |
| plan | object | yes | The result of `visimark_fmt`, unedited apart from dropping entries you rejected. |
No output schema declared.
No examples provided.
visimark_infer Propose VisiMark rules for a plain table ~110
Derive the formulas an existing Markdown table already obeys, and propose them as `vmark` rules. Run this before hand-authoring rules for a document that already has its numbers. Returns proposals only and never writes; `visimark_infer_apply` writes them.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | The document as text, for a draft that is not on disk. Give this or `path`, never both. |
| path | string | – | Path to a Markdown document on disk. |
No output schema declared.
No examples provided.
visimark_infer_apply Apply proposed VisiMark rules ~121
Insert the `vmark` rules `visimark_infer` proposed. Pass the plan you were given, with any proposal you rejected removed. Refused if the document changed since the plan was computed, and refused entirely unless the operator started the server with `--allow-write` and the host declared a root.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | The document to write. There is nothing to apply to a string. |
| plan | object | yes | The result of `visimark_infer`, unedited apart from dropping entries you rejected. |
No output schema declared.
No examples provided.
visimark_ref VisiMark function reference ~77
Look up VisiMark's builtin functions: signature, arity, precision, errors and examples. Give `name` to look it up, or omit `name` for the whole reference. Reads no file.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | A builtin's name, e.g. `SUM`. Omit for the whole reference. |
No output schema declared.
No examples provided.
How do I install the io.github.michal-niedzwiedzki/visimark MCP server?
io.github.michal-niedzwiedzki/visimark runs locally as an npm package, launched with npx -y visimark-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 · visimark-mcp
claude mcp add michal-niedzwiedzki-visimark -- npx -y visimark-mcp
What is the io.github.michal-niedzwiedzki/visimark MCP server?
io.github.michal-niedzwiedzki/visimark is an MCP server listed in the public MCP registry as io.github.michal-niedzwiedzki/visimark. MCP server for VisiMark, a document integrity layer for Markdown: checks numbers against formulas. This page covers its npm package (visimark-mcp).
Is the io.github.michal-niedzwiedzki/visimark MCP server safe to use?
io.github.michal-niedzwiedzki/visimark scores 96 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 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 io.github.michal-niedzwiedzki/visimark MCP server expose?
io.github.michal-niedzwiedzki/visimark exposes 8 tools: visimark_ref, visimark_check, visimark_explain, visimark_eval, visimark_infer, and 3 more. Their descriptions and schemas cost roughly 976 tokens of context every time the server is loaded.
Is the io.github.michal-niedzwiedzki/visimark MCP server still maintained?
io.github.michal-niedzwiedzki/visimark 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 io.github.michal-niedzwiedzki/visimark MCP server under?
io.github.michal-niedzwiedzki/visimark declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.