World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Builds S1000D data modules from structured drafts, verifies them, applies only unambiguous fixes.
作者提供的原文
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 7/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 19/100 |
质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 S1000D Writer (S1000D Stack)。按照 https://mcp.popnx.com/i/shuji-bonji-s1000d-writer-mcp.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 3/3 项检查 · 在你的电脑上运行 · ✓ 命令已检查 2026年11月18日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
需要先在电脑上安装 Node.js(只需一次) · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
把这段话复制到 Claude 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude 安装 MCP server S1000D Writer (S1000D Stack),按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "s1000d-writer": { "command": "npx", "args": [ "-y", "@shuji-bonji/s1000d-writer-mcp" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 S1000D Writer (S1000D Stack) 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
SettingsDeveloperEdit Config
{
"mcpServers": {
"s1000d-writer": {
"command": "npx",
"args": [
"-y",
"@shuji-bonji/s1000d-writer-mcp"
]
}
}
}用 S1000D Writer (S1000D Stack) 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 S1000D Writer (S1000D Stack),或回答中出现 S1000D Writer (S1000D Stack) 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 S1000D Writer (S1000D Stack)
S1000D Writer (S1000D Stack) 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
A · 使用能连接 S1000D Writer (S1000D Stack) 的应用
B · 其他 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
可连接 Claude Code,但需要先准备
需要先在电脑上安装 Node.js(只需一次)
把这段话复制到 Claude Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude Code 安装 MCP server S1000D Writer (S1000D Stack),按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):claude mcp add --scope user s1000d-writer -- npx -y @shuji-bonji/s1000d-writer-mcp 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 S1000D Writer (S1000D Stack) 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,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 s1000d-writer -- npx -y @shuji-bonji/s1000d-writer-mcp应能看到 S1000D Writer (S1000D Stack) 在列表中并显示已连接
用 S1000D Writer (S1000D Stack) 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 S1000D Writer (S1000D Stack),或回答中出现 S1000D Writer (S1000D Stack) 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor,但需要先准备
需要先在电脑上安装 Node.js(只需一次)
把这段话复制到 Cursor 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Cursor 安装 MCP server S1000D Writer (S1000D Stack),按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "s1000d-writer": { "command": "npx", "args": [ "-y", "@shuji-bonji/s1000d-writer-mcp" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 S1000D Writer (S1000D Stack) 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
用 S1000D Writer (S1000D Stack) 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 S1000D Writer (S1000D Stack),或回答中出现 S1000D Writer (S1000D Stack) 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code,但需要先准备
需要先在电脑上安装 Node.js(只需一次)
把这段话复制到 VS Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 VS Code 安装 MCP server S1000D Writer (S1000D Stack),按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "servers": { "s1000d-writer": { "type": "stdio", "command": "npx", "args": [ "-y", "@shuji-bonji/s1000d-writer-mcp" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 S1000D Writer (S1000D Stack) 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
用 S1000D Writer (S1000D Stack) 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 S1000D Writer (S1000D Stack),或回答中出现 S1000D Writer (S1000D Stack) 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
Claude Code
claude mcp add --scope user s1000d-writer -- npx -y @shuji-bonji/s1000d-writer-mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"s1000d-writer": {
"command": "npx",
"args": [
"-y",
"@shuji-bonji/s1000d-writer-mcp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"s1000d-writer": {
"command": "npx",
"args": [
"-y",
"@shuji-bonji/s1000d-writer-mcp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"s1000d-writer": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@shuji-bonji/s1000d-writer-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 账户 shuji-bonji 验证,该账户拥有此仓库
代码最后更新于前天
使用 MIT
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
尚未检查
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/shuji-bonji-s1000d-writer-mcp)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于前天,最新版本(0.6.0)于前天进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
Validate oh-my-posh configurations and segment snippets against the official schema.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.
| 本项 S1000D Writer (S1000D Stack) | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 3/3 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| 许可证 | MIT | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
English | 日本語
An MCP server that lets an LLM create S1000D® data modules without writing XML. The LLM passes a structured draft and numbering rules; the server builds the XML, verifies it against the XSD, the BREX and the references, and applies automatically only the fixes that have exactly one candidate (exact). A fix with several candidates is applied only from a selection, and a value outside the candidates is never accepted. By default nothing is written.
[!IMPORTANT]
This is a personal project and is not affiliated with ASD (Aerospace, Security and Defence Industries Association of Europe). S1000D® is a registered trademark of ASD.
The S1000D specification, XML schemas, default BREX and official samples are not included in any package or repository, because their terms of use do not grant redistribution. Obtain them from s1000d.org and point the
S1000D_SPEC_DIRenvironment variable at the extracted folder.
| Tool | Description |
|---|---|
build_data_module | Builds a data module from one draft (descript, proced, process, fault or PM) and numbering rules. The DMC, ICN and issue come from the ledger (ledger) and the CSDB, and the same sourceId always gets the same DMC. After building, it verifies the XSD, BREX and references, and applies only exact fixes, up to maxFixRounds rounds. The remaining fixes are returned in fixes[] with their candidates |
convert_manual | Converts an experiential manual (@shuji-bonji/experiential-manual-model) into one data module per topic plus a publication module. Descriptions, procedures and fault isolation map directly; a screen flow becomes one process data module plus one procedure per screen. References between DMs, the PM and ICNs are resolved on top of the CSDB overlaid with the DMs just built and the ICN originals found on disk. What the conversion cannot represent is returned in notRepresented as counts |
apply_fixes | Applies the fixes you chose from the candidates in fixes[]. A selection must be a copy of a candidate; a value outside the candidates, or one that does not fit a range, goes to rejected with a reason. It re-verifies after applying |
create_comment | Builds a comment data module (comment) and verifies it. The sequence number is the next one in the CSDB |
extract_segments | Takes the sentences a person reads out of a data module (titles, paragraphs, steps, warnings, table cells, figure captions) so they can be translated. Inline elements are replaced by {1}, {2} placeholders, and skeletonHash is returned |
apply_segments | Puts translated sentences back into the data module they were taken from. The DMC stays the same and only the language changes. It stops with skeleton-mismatch when the data module changed after extraction |
write: true does the server write DMC-….XML into the first folder of csdbDirs (or the first of S1000D_CSDB_DIR). With no destination it writes nothing and returns the reason (no-csdb-dir).write-conflict) unless overwrite: true is passed.schema-invalid) unless allowInvalid: true is passed. schema-not-found (no XSD available) is not a violation; the file is written as unverified.write: true, convert_manual also copies the original assets under their ICN file names.Only a fix whose confidence is exact and which has exactly one candidate is applied (for example, replacing a value when the BREX allows a single responsible company, or removing an element the BREX forbids). several (more than one candidate, or a value given as a range) and none are not applied and are returned in fixes[]. The user chooses, and the server never fixes with a value outside the candidates. Each applied fix is returned in appliedFixes[] with the values before and after.
verification)Every response carries the verification status of the XSD, the BREX and the references. A missing XSD is reported as schema-not-found and a skipped step as not-run; neither is valid. The server reports the result of verification only: it does not judge conformance to S1000D and does not interpret severity.
A mistake in the draft or the numbering rules is returned not as isError but as error: { code: "input-error", path, detail }. path is the location of the mistake (for example /body[1] or /allocation/rules/infoCodeByKind/proced). Fix it and call again.
[!WARNING]
- It does not accept XML written by an LLM. It builds only from a draft. The tools that take existing XML (
apply_fixes,extract_segments,apply_segments) do not change the structure of the document.
- It does not fix with a value outside the candidates. There is no entry point for writing a free value.
- It does not skip verification. A built XML is always verified before it is returned.
- It does not judge conformance to S1000D or interpret severity. Read the violations in
s1000d-verify-mcpand the explanation of BREX rules ins1000d-brex-mcp.
- It does not translate. It only takes sentences out and puts them back. The LLM or a person translates.
- It does not create illustrations or judge Simplified Technical English (STE). For an illustration it only allocates an ICN and inserts the reference.
- What a data module cannot represent, such as hotspot coordinates or part of
scopeRefsin an experiential manual, is reported innotRepresentedand never dropped silently.
-
convert_manualdoes not build the data module of a topic whoseprerequisiteslist an item without an identifier (natoStockNumberormanufacturerCode) or withoutquantity. That row ofdataModules[]carrieserror(input-error, with the path of the item); the other data modules are still built. S1000D requires an identifier and a quantity for each item, and leaving the item out would writenoSupplies, which reads as "nothing is required".
- It does not create an ACT, CCT or PCT. Applicability relies on the
applicof the draft and an existing applicability repository. When a draft given tobuild_data_modulehas noapplic, the server does not build it and returnsinput-error(pathis/applic). The server does not decide applicability, so give at leastapplic.displayText(convert_manualusesdefaultApplic, by default the display text "All", for topics withoutscopeRefs).
| Environment variable | Meaning |
|---|---|
S1000D_SPEC_DIR | The folder where you extracted the S1000D distribution you obtained. The XSDs (xml_schema_flat/) and the default BREX are searched under it |
S1000D_CSDB_DIR | The folder holding the project's data modules. Several can be given, separated by : (; on Windows). The BREX chain, reference targets and existing issues are searched here, and the first folder is the write destination |
You can also give folders with the tool argument csdbDirs (the first one is the write destination). When the argument is given, only those folders are used; S1000D_CSDB_DIR and csdbDirs in the config file are not used (they are not added together). Folders that do not exist are skipped and listed in _notes of the response. The first folder may not exist yet; it is created with write: true.
When S1000D_SPEC_DIR / S1000D_CSDB_DIR are not set, the server reads the config file ~/.config/s1000d-stack/config.json (under XDG_CONFIG_HOME if set; the location can be changed with S1000D_CONFIG). Claude Desktop does not pass environment variables to a server installed as a plugin, so write the settings here in that case.
{
"specDir": "/path/to/s1000d/issue-7", "csdbDirs": ["/path/to/your/csdb"] }
Environment variables take precedence when they are set. The config file is read again on every call.
{
"mcpServers": { "s1000d-writer": { "command": "npx", "args": ["-y", "@shuji-bonji/s1000d-writer-mcp"], "env": { "S1000D_SPEC_DIR": "/path/to/s1000d/issue-7", "S1000D_CSDB_DIR": "/path/to/your/csdb" } } } }
The default is stdio. With --http the server starts over Streamable HTTP.
npx -y @shuji-bonji/s1000d-writer-mcp --http # http://127.0.0.1:3000/mcp
npx -y @shuji-bonji/s1000d-writer-mcp --http --port 3102 --path /writer
| Argument | Default | Meaning |
|---|---|---|
--host | 127.0.0.1 | Address to bind to |
--port | 3000 | Port; 0 picks a free port |
--path | /mcp | Path of the MCP endpoint. GET /healthz returns the name and version |
--allowed-host | (see below) | Host names allowed in the Host header; comma-separated or repeated |
--allowed-origin | (see below) | Host names allowed in the Origin header |
When --host is a loopback address, Host and Origin are limited to localhost names (DNS rebinding protection). When bound to any other address they are not checked, so put the server behind the product's reverse proxy or authentication. Because this server can write files, do not expose it without authentication.
All building, verification, fixing, comment and segment code lives in the shared library @shuji-bonji/s1000d-core; this server holds only the interpretation of arguments, the shape of the responses and the conversion from a manual to drafts (src/convert/). The input schemas import the definitions of core's draft.schema.json. The conversion is also available as @shuji-bonji/s1000d-writer-mcp/convert.
npm install
npm test # runs on self-made test data only (tests/fixtures/) npm run test:spec # uses the distribution you obtained (location given by S1000D_SPEC_DIR; default ../../specs/s1000d/issue-7) npm run build && S1000D_SPEC_DIR=/path/to/issue-7 S1000D_CSDB_DIR=/path/to/csdb npm start # start over stdio
MIT. S1000D® is a registered trademark of ASD. This software is not affiliated with ASD and does not include the specification, schemas or official samples.