MinerU
Transforms complex documents like PDFs and Office docs into LLM-ready markdown/JSON for your Agentic workflows.
MCP server for VisiMark, a document integrity layer for Markdown: checks numbers against formulas.
作者提供的原文
教 AI 做这类工作的 Skill,可与本项一起使用
Transforms complex documents like PDFs and Office docs into LLM-ready markdown/JSON for your Agentic workflows.
Agent skills for Obsidian. Teach your agent to use Obsidian CLI and open formats including Markdown, Bases, JSON Canvas.
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 0/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 12/100 |
质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 Visimark。按照 https://mcp.popnx.com/i/michal-niedzwiedzki-visimark.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 3/3 项检查 · 在你的电脑上运行 · ✓ 命令已检查 2026年11月13日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
需要先在电脑上安装 Node.js(只需一次) · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
把这段话复制到 Claude 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude 安装 MCP server Visimark,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "visimark": { "command": "npx", "args": [ "-y", "visimark-mcp" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Visimark 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
SettingsDeveloperEdit Config
{
"mcpServers": {
"visimark": {
"command": "npx",
"args": [
"-y",
"visimark-mcp"
]
}
}
}用 Visimark 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Visimark,或回答中出现 Visimark 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 Visimark
Visimark 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
可连接 Claude Code,但需要先准备
需要先在电脑上安装 Node.js(只需一次)
把这段话复制到 Claude Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude Code 安装 MCP server Visimark,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):claude mcp add --scope user visimark -- npx -y visimark-mcp 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Visimark 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --scope user visimark -- npx -y visimark-mcp应能看到 Visimark 在列表中并显示已连接
用 Visimark 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Visimark,或回答中出现 Visimark 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor,但需要先准备
需要先在电脑上安装 Node.js(只需一次)
把这段话复制到 Cursor 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Cursor 安装 MCP server Visimark,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "visimark": { "command": "npx", "args": [ "-y", "visimark-mcp" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Visimark 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
用 Visimark 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Visimark,或回答中出现 Visimark 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code,但需要先准备
需要先在电脑上安装 Node.js(只需一次)
把这段话复制到 VS Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 VS Code 安装 MCP server Visimark,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "servers": { "visimark": { "type": "stdio", "command": "npx", "args": [ "-y", "visimark-mcp" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Visimark 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
用 Visimark 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Visimark,或回答中出现 Visimark 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
Claude Code
claude mcp add --scope user visimark -- npx -y visimark-mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"visimark": {
"command": "npx",
"args": [
"-y",
"visimark-mcp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"visimark": {
"command": "npx",
"args": [
"-y",
"visimark-mcp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"visimark": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"visimark-mcp"
]
}
}
}这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月20日
注册名称已通过 GitHub 账户 michal-niedzwiedzki 验证,该账户拥有此仓库
代码最后更新于5天前
使用 MIT
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
OSV.dev 中没有 visimark-mcp@0.4.1 的记录
只检查这个版本的包本身,不包括所有依赖 · 检查于 2026年11月15日
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/michal-niedzwiedzki-visimark)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于5天前,最新版本(0.4.1)于34天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:Puter MCP, XcodeBuildMCP, Vexa, Atlassian Rovo MCP Server, Anki MCP Server
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Puter MCP enables AI tools to interact with Puter: manage files, websites, workers, and more
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Connect to Atlassian Jira, Confluence, Loom, and more to search, create, and manage your work.
MCP server for Anki flashcards: adaptive review, notes, media, and deck management via AnkiConnect.
| 本项 Visimark | Puter MCP | XcodeBuildMCP | Vexa | Atlassian Rovo MCP Server | Anki MCP Server | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 在云端运行,无需安装 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 | 需要安装在电脑上 |
| 需要密钥 | 否 | 否 | 否 | 是 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 是 | 否 |
| 基础检查 | 3/3 | 4/4 | 3/3 | 2/4 | 4/4 | 3/3 |
| 许可证 | MIT | AGPL-3.0 | MIT | Apache-2.0 | Apache-2.0 | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
A document integrity layer for Markdown: it checks that every number in a document still matches the formula that produced it, so an agent's correct formula can't ship with a wrong total.
VisiMark checks the numbers in Markdown documents, especially ones an agent wrote. Every computed value carries its formula, a machine proves the two still agree, and CI fails when they don't. The document stays plain Markdown.
This matters most when the Markdown is written or edited by an AI agent. Agents are reliable at writing formulas and unreliable at the arithmetic those formulas describe: Net = Price * Qty is something an agent gets right, 50.00 is something it guesses. Write the formula instead of the number and the number stops being a claim and becomes a derivation — reviewable in a diff, re-runnable, enforceable in CI. The agent writes, VisiMark verifies, Git records the result.
A VisiMark document is an ordinary Markdown file. It renders correctly on GitHub, in VS Code preview, and through pandoc to both HTML and Word, today, with no plugin — verified, not assumed. What VisiMark adds is that every computed number in it carries the formula that produced it, that a machine can prove the two still agree, and that a change to either shows up as a small, readable diff.
Six audiences so far, each with a specific entry point. Kept short on purpose — it grows when one of these gets a real user, not before.
eval --scenario, worked through on a headcount model in docs/tutorial/runway.md.remark-lint-visimark, markdownlint-rule-visimark, and the composite GitHub Action.Rate [PLN] or speed [m/s] = Distance / Duration, and check refuses kg + m and derives km/h (see What it refuses to do).NPV, IRR, PMT, and the decimal precision the three of them force you to declare, worked through in a loan and an investment appraisal.docs/example-invoice-drift.md is a real B2B invoice after someone raised the on-call hours from 12 to 20 and updated nothing that depends on it. It renders as a clean, plausible invoice on GitHub, in a Markdown preview, anywhere — which is the entire argument for this project. Every number in it carries the formula that produced it; the syntax follows further down. Here is visimark check reading the same file a reviewer just skimmed and approved:
$ visimark check docs/example-invoice-drift.md
docs/example-invoice-drift.md
STALE lines.Net · On-call support 3120.00 ≠ 5200.00 Qty * Rate STALE lines.VAT · On-call support 717.60 ≠ 1196.00 Net * vat STALE lines.Gross · On-call support 3837.60 ≠ 6396.00 Net + VAT STALE lines.Gross · Discovery workshop 4428.50 ≠ 4428.00 Net + VAT STALE lines.net_total 23300.00 ≠ 25380.00 SUM(Net) STALE lines.vat_total 5359.00 ≠ 5837.40 SUM(VAT) STALE lines.gross_total 28659.00 ≠ 31217.40 SUM(Gross) STALE lines.gross_total 28659.00 ≠ 31217.40 SUM(Gross) STALE schedule.Amount · Signature 8597.70 ≠ 9365.22 Share * lines.gross_total STALE schedule.Amount · Delivery of backend 11463.60 ≠ 12486.96 Share * lines.gross_total STALE schedule.Amount · Acceptance 8597.70 ≠ 9365.22 Share * lines.gross_total STALE schedule.covered 28659.00 ≠ 31217.40 SUM(Amount) STALE terms.early_pay_total 28085.82 ≠ 30593.05 STALE terms.early_pay_saved 573.18 ≠ 624.35 STALE 8 prose anchors bound to the values above
DATE schedule.Due · Delivery of backend "15.10.2026" Dates must be ISO 8601 calendar dates: YYYY-MM-DD. Unambiguous — visimark fmt --fix-dates rewrites it to 2026-10-15.
DATE schedule.Due · Acceptance "11/12/2026" Dates must be ISO 8601 calendar dates: YYYY-MM-DD. Ambiguous: 2026-12-11 or 2026-11-12, 29 days apart. Fix by hand.
NOTE schedule.Days · 2 rows not verified (upstream DATE errors)
UNDEF terms.eur_total unknown name fx_rate did you mean fx_eur?
VECTOR recon.variance schedule.Amount is a column, not a value. Wrap it in an aggregate: SUM(schedule.Amount)
CYCLE late_fees.base → late_fees.fee → late_fees.total → late_fees.base
27 problems (22 stale, 5 errors) $ echo $? 1
Twenty-seven problems: a payment date ambiguous by twenty-nine days, a cell someone nudged by hand to make a column look right, a circular reference — all invisible on the rendered page, all caught before a human had to notice.
More and more of the documents that carry numbers are written as text and kept in Git: reports and research notes, estimates and budgets, quotes and invoices, project plans, financial summaries. Text is excellent for collaboration, review and version control. But ordinary Markdown has no way to say *this number came from these inputs, and it must still agree with them* — so the moment an input changes, every figure downstream of it is a guess until a human re-checks it by hand.
VisiMark adds that missing layer. The working stack for collaborating with an agent is a text editor over lightly formatted artifacts; Markdown already covers the prose, and this covers the calculation. The arithmetic is not the value — the audit trail is.
| Item | Price | Qty | Net |
|-------|------:|----:|------:| | pen | 5.00 | 10 | 50.00 | | paper | 0.10 | 100 | 10.00 |
Net = Price * Qty
total = SUM(Net)
Order total: 60.00
Four ideas, and that is the whole format:
Net = Price * Qty is one rule for every row, not a formula per cell. Columns with no rule are inputs, and are never overwritten.docs/tutorial.md is the end-to-end tutorial: twenty-eight short chapters from a plain Markdown table to a checked document, a CI job and a script reading values back out. It teaches the language in dependency order, every finding check can report, and the one habit that keeps a green check meaningful. Every transcript in it is real.
There is a side-by-side reader for it at docs/tutorial.html, which shows each block's Markdown source next to its rendering, in lockstep.
docs/example-invoice.md is a complete B2B invoice that computes itself: line items, VAT, a payment schedule derived from the gross total, early-payment terms, a currency conversion, and a reconciliation that proves the instalments sum to the invoice. Its appendix explains each mechanism.
docs/example-invoice-drift.md is that same invoice with the drift shown at the top of this README — the 27 problems transcript above is check reading this exact file, and its appendix walks through every one of the 27 problems.
docs/example-quote-plain.md is the other direction: a quote with no VisiMark in it at all — no vmark block, no anchor, just a table and a total written in prose, the way an agent hands one over before anyone has wired it up. visimark infer reads it and proposes the rules that reproduce every number already there:
$ visimark infer docs/example-quote-plain.md
docs/example-quote-plain.md table at line 10 — 4 rows, 7 columns
column rules Revenue = Seats * Fee 4/4 rows Materials = Revenue * 0.08 4/4 rows Delivered = Revenue + Materials 4/4 rows
constants worth naming 0.08 also appears as "8%" in prose, line 18
scalars matching figures in prose 72 line 17 = SUM(Seats) seats_total 27600.00 line 18 = SUM(Revenue) revenue_total 2208.00 line 19 = SUM(Materials) materials_total 29808.00 line 19 = SUM(Delivered) delivered_total 530.00 line 20 = AVG(Fee) fee_avg
no rule found — treating as inputs Module, Format, Seats, Fee
also fits, not proposed Delivered = Revenue * 1.08 prefers a rule over materialised columns Delivered = Materials * 13.5 prefers a rule over materialised columns
docs/example-quote-plain.md table at line 24 — 3 rows, 4 columns
column rules Amount = Share * unnamed1.delivered_total 3/3 rows
scalars matching figures in prose 29808.00 line 30 = SUM(Amount) amount_total
no rule found — treating as inputs Stage, Share, Due
also fits, not proposed Amount = Share * 29808 prefers a rule over materialised columns
4 rules, 0 aliases, 6 scalars, 6 anchors.
A rule is proposed only if it reproduces every row exactly, at that column's own precision — never a best fit, never a threshold, and also fits, not proposed is listed rather than silently dropped, because a rule over materialised columns beating one with a bare constant is a judgment call worth seeing. --write inserts exactly the blocks and anchors above and rewrites nothing else. A rule that fits every row but one is never written; it is reported as a near-miss instead — the tool telling you the document already has a wrong number in it, before anyone runs check on it. The document's own appendix walks through every mechanism, including that near-miss case.
infer is the way in for the document check would otherwise have nothing to say about: one with no formulas at all. Pairing the two closes the loop — infer gets a plain table wired up, and check keeps it that way.
VisiMark parses the document, builds a dependency graph across every sheet, sorts it topologically, and evaluates in decimal arithmetic. Circular dependencies are reported with the full path through the cycle.
flowchart LR
parse[Parse Markdown] --> deps[Build dependency graph] deps --> sort[Topological sort] sort --> evaluate[Evaluate in decimal] evaluate --> cycle{"Cycle?"} cycle -->|yes| report[Report the CYCLE path] cycle -->|no| values[Computed values]
The CLI is the product. An agent must be able to verify a document without an editor; a VS Code extension is a later, thin