Skip to content

MCP servers › io.github.ayuanxx-max › signoff-cli

MCP server · registry snapshot 2026-11-13 · last checked 2026-11-13

signoff-cli MCP server

Registry name io.github.ayuanxx-max/signoff-cli

by ayuanxx-max · GitHub account (the registry's namespace rule)repository: same ownerSource ↗npm ↗

Five gates that make an agent's 'done' provable: run them, read the verdict, audit the record. — the publisher's description

9 of 9 record checks metversion 4.8.0JavaScriptMITstandard input/output

Summary

io.github.ayuanxx-max/signoff-cli is a local MCP server listed in the official MCP registry at version 4.8.0, under the namespace of the GitHub account ayuanxx-max. Its linked repository, github.com/ayuanxx-max/signoff-cli, belongs to the same GitHub account.

Record checks

9 of 9 record checks met

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • met: Repository publishes a security policy (SECURITY.md)
  • met: Package names its licence with a standard (SPDX) identifier
  • met: The version the registry lists can be installed and is not withdrawn
  • met: npm package carries build provenance (attestation)
  • met: No known critical or high advisory in the package or its dependencies

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it

Key facts

Runs
local package
Transport
standard input/output
Your own values
none declared (not a guarantee)
Package
npm · listed version current
License
MIT
Dependencies
no known high or critical advisories
Repository
public
Last tested
not tested

Tool list

Not read: It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's. So there is no tool-list size and no result from the three APIs.

Add to your client

Worth knowing before you connect it

  • Its package is signed and carries a build record naming its source.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested
no
Last tested
not tested
Latest version
4.8.0, published 2026-11-12 (registry, as of the 2026-11-13 snapshot)
First listed version
2026-11-07 (earliest version still in the registry; older removed versions would be earlier)
Version history
28 versions listed, 2026-11-07 to 2026-11-12; 28 in the 90 days before the 2026-11-13 snapshot.
Most recent 12 versions
  • 4.8.0 · 2026-11-12
  • 4.7.1 · 2026-11-11
  • 4.7.0 · 2026-11-11
  • 4.6.2 · 2026-11-11
  • 4.6.1 · 2026-11-11
  • 4.6.0 · 2026-11-11
  • 4.5.0 · 2026-11-11
  • 4.4.5 · 2026-11-11
  • 4.4.4 · 2026-11-11
  • 4.4.3 · 2026-11-11
  • 4.4.2 · 2026-11-11
  • 4.4.1 · 2026-11-11
(versions still listed in the registry only)
Registry data
snapshot 2026-11-13
Package and repository
checked 2026-11-13

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry; listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

Version 4.7.1 (published 2026-11-11) → 4.8.0 (published 2026-11-12), between the registry lists of 2026-11-12 and 2026-11-13.

The publisher’s GitHub release note for v4.8.0 (“signoff-cli 4.8.0:闸门按代价分层”), published 2026-11-12.

Read the release note (the publisher’s text, shown as plain text)
**闸门按代价分层,反向对照只问「会不会红」。**

## 钩子:提交跑快检,推送跑全套

- `signoff init` 装的三个钩子各司其职:`pre-commit` 跑 p1 的快检层,`pre-push` 与 CI 跑全套。快检入口取自
  `.signoff/config.json` 的 `fast_cmd` 或 `package.json` 的 `test:fast`;两样都没有就退回全套——没声明就没有这一层。
- `.signoff/cache.json` 的键带上运行模式(`fast` / `full`):快检通过不能替推送那一次的全套作保。
- 本仓库新增 `node test/smoke.js`(8 项,约 2.4 s),断言落在真正渲染出的页面 chip 上,不是源码里的字符串。
- `npm test` 改成两段并行(`test/run-all.js`):用例一条没少,全套 93 s → 50 s 量级,推送闸门 126 s → **53 s**。
  `node test/selftest.js` 仍是完整串行路径,并支持 `SIGNOFF_TIMING=1` 排出最慢的 12 条用例。

## 反向对照:改过的测试必须在旧代码上红

`signoff p1 --negative-control` 把这次改过的测试文件放进 `git worktree` 检出的 base 版本里跑一遍,**必须红**。
两棵树都绿判红(`green-on-base`),在 base 上跑不起来单列 `cannot-run-on-base`,不冒充「测出来了」。
推送与 CI 自动带上,只有 touched 非空才付这笔钱,`--nc-budget` 默认 180 s、超时算红。
它只问「会不会红」,所以套件在 `SIGNOFF_NC=1` 下第一条红就收工:反向对照 60.4 s → **2.2 s**。

## 界面:金额带词、版面有据可查

- 侧栏与看板的金额一律先出词再出数:中文 `费用 $0.02`,英文 `cost $0.02`;`class="cost"` 的可见文本都形如 `费用 $…`。
- 看板加「Token 与费用」:累计 token、金额、按天、按任务组、按提交的 agent 花费;`signoff tokens` 在终端问同一件事。
  数据只读本机 DSH 会话记录,金额按 DeepSeek 峰/谷价估算,`.signoff/prices.json` 可覆盖;读不到就写明原因而不是显示 0。
- 新增 `docs/DESIGN.md`、`node tools/ui-shot.js`(看板出图)、`jsconfig.json` + `npm run typecheck`(运行时依赖仍是零)。

## 修复(挑要紧的)

- 看板任务组的三个数字取同一个窗口,不再在一句话里自相矛盾。
- `integrity` / `review` / `fix` 统一走 `git -z`:路径含中文或空格时不再被八进制转义骗成「没有改动」
  (删掉 `tests/测试.test.js` 的断言曾判 clean,`Lib/P1.js` 曾能覆盖 `lib/p1.js`)。
- `fix` 回滚不再删掉补丁自己新建、被 `.gitignore` 挡住的文件;`patterns` 不再把回滚/被推翻/被拒算成门失败。
- `dispute` 不再把拼错的命令当证据,`--budget` 带 timeout 与 SIGKILL;`uninstall` 收走新增状态。

## English

**Gates are layered by cost; the negative control only asks whether a test goes red.**

- Hooks now have separate jobs: `pre-commit` runs the p1 fast layer, `pre-push` and CI run the full suite. The fast
  command comes from `.signoff/config.json` or `package.json`; with neither declared the hook falls back to the full
  suite instead of waving the commit through. The cache key carries the run mode, so a green fast run cannot stand
  in for the full run at push time.
- `npm test` runs two shards in parallel (`test/run-all.js`): no case was dropped, the suite went 93 s → 50 s range,
  and the push gate 126 s → **53 s**. `node test/selftest.js` remains the full serial path and accepts
  `SIGNOFF_TIMING=1` to rank the slowest cases.
- New `signoff p1 --negative-control`: the test files touched by a change run inside a base version checked out with
  `git worktree` and **must go red**. Green on both trees is `green-on-base`; a base checkout where they cannot start
  is reported as `cannot-run-on-base` instead of pretending the test proved anything. Under `SIGNOFF_NC=1` the suite
  stops at the first red, taking the negative control from 60.4 s to **2.2 s**.
- Amounts always carry a label first (`费用 $0.02` / `cost $0.02`); the board gains a "Token and cost" block fed by
  this machine's DSH session records (read-only, no network), and `signoff tokens` answers the same question in the
  terminal. When the records are unreadable the block says why instead of showing 0.
- New `docs/DESIGN.md`, `node tools/ui-shot.js`, `jsconfig.json` + `npm run typecheck`; runtime dependencies stay zero.
- `integrity`, `review` and `fix` now parse `git -z` instead of human-readable output: paths with Chinese characters
  or spaces no longer look like "nothing changed". Rollback, refutation and rejection are recorded as tool outcomes,
  not gate failures.

**Full self-test**: 619 passed / 0 failed. Published from GitHub Actions with a provenance attestation.

The release on GitHub

Source: the official MCP Registry list on 2026-11-12 and on 2026-11-13; release notes from the GitHub Releases API, checked 2026-11-13.

What it is

How do I add it to my client?

Config from the registry entry

From the npm package signoff-cli

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below. The command runs the publisher’s code on your machine.

Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)
{
  "mcpServers": {
    "signoff-cli": {
      "command": "npx",
      "args": [
        "-y",
        "signoff-cli@4.8.0",
        "mcp"
      ]
    }
  }
}
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "signoff-cli": {
      "command": "npx",
      "args": [
        "-y",
        "signoff-cli@4.8.0",
        "mcp"
      ]
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "signoff-cli": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "signoff-cli@4.8.0",
        "mcp"
      ]
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"signoff-cli","type":"stdio","command":"npx","args":["-y","signoff-cli@4.8.0","mcp"]}'
Claude Code
claude mcp add --transport stdio signoff-cli -- npx -y signoff-cli@4.8.0 mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "signoff-cli": {
      "command": "npx",
      "args": [
        "-y",
        "signoff-cli@4.8.0",
        "mcp"
      ],
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "signoff-cli": {
      "command": "npx",
      "args": [
        "-y",
        "signoff-cli@4.8.0",
        "mcp"
      ]
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.signoff-cli]
command = "npx"
args = ["-y", "signoff-cli@4.8.0", "mcp"]
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "signoff-cli": {
      "command": "npx",
      "args": [
        "-y",
        "signoff-cli@4.8.0",
        "mcp"
      ]
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 -- npx -y signoff-cli@4.8.0 mcp
  • Arguments are written as the registry entry gives them; a named one as “--name value”, the form the registry documentation shows.
  • This runs the publisher's code on your machine (npx). Read its README first.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Can it be installed, and is it up to date?

Version pin · advisories

Listed version

Registry lists
4.8.0
Latest stable
4.8.0
Status
current
Withdrawn
no

Source: registry.npmjs.org · 2026-11-13. About the version the registry lists; a manual install may resolve to a different one.

Dependency advisories

critical0high0moderate0low0

Counted in the full dependency tree as resolved on 2026-11-13 (npm audit; each bar counts packages with an advisory, not advisories). Bars share one scale. The package itself has no known vulnerability (OSV.dev).

Integrity, provenance, license

Integrity
sha512-6VqWL0oDvwlM3TG/t…
Signature
signed and attested
License
MIT

Source: the package registry · 2026-11-13.

Usage

Downloads
7,389 in the last month

Source: api.npmjs.org · 2026-11-13.

What do the published files and outside lists say?

Read as text · nothing run · no tool called

Package files

  • Install-time script (npm). Runs a command when installed: postinstall: node bin/signoff.js ensure --from-install --quiet (runs a file) (from the published package.json, version 4.8.0). We read it; we did not run it. Source: registry.npmjs.org/signoff-cli/4.8.0 · read 2026-11-13.
  • Operating systems and processors (npm). The npm package sets no os or cpu limit (package.json). Source: registry.npmjs.org/signoff-cli/4.8.0 · read 2026-11-13.
  • Node.js version (npm). Needs Node 18 or later (engines.node >=18). Source: registry.npmjs.org/signoff-cli/4.8.0 · read 2026-11-13.
  • MCP SDK in the package files. Ships no MCP SDK code in its own files by our rule, and does not list @modelcontextprotocol/sdk or any of the MCP SDK's split packages (core, server, client, node, express, hono, fastify, server-legacy) as a dependency. Source: registry.npmjs.org/signoff-cli/-/signoff-cli-4.8.0.tgz · read 2026-11-13.
  • Build workflow. Built and published by GitHub Actions workflow .github/workflows/publish.yml in https://github.com/ayuanxx-max/signoff-cli (npm provenance). Source: read 2026-11-13.

Registry entry

  • Same package in other registry entries. No other registry entry lists this entry's npm or PyPI package at a newer version. Source: own registry snapshot · read 2026-11-13.

Outside lists

  • CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-13. This product uses the NVD API but is not endorsed or certified by the NVD.
  • GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-13. GitHub Advisory Database, CC BY 4.0
  • Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-13. Source: read 2026-11-13.
  • Cline marketplace. Not in the Cline marketplace on 2026-11-13. Source: read 2026-11-13.

Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Version 4.8.0 on npmExists and can be installedmatchesnpm · 2026-11-13
Repository github.com/ayuanxx-max/signoff-cliOpens publiclymatchesapi.github.com · 2026-11-13

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
io.github.ayuanxx-max · 2 servers
GitHub owner
a personal account (ayuanxx-max)
Build record
signed and attested
Repository
github.com/ayuanxx-max/signoff-cli
Stars
3
Repository age
0–30 days
Last push
0–30 days ago
Archived
no
Security policy
SECURITY.md

Source: the registry entry and api.github.com · 2026-11-13; security policy read from GitHub · 2026-11-19.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

9 of 9 record checks met

  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • MetRepository publishes a security policy (SECURITY.md)SECURITY.md found.
  • MetPackage names its licence with a standard (SPDX) identifierMIT
  • MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
  • Metnpm package carries build provenance (attestation)Signed, with a build attestation naming the source and workflow.
  • MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-13 (security policy 2026-11-19). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about io.github.ayuanxx-max/signoff-cli

Answered from the data above

Who publishes io.github.ayuanxx-max/signoff-cli?

The registry ties the namespace io.github.ayuanxx-max to the GitHub account ayuanxx-max; only its owner can publish under it. Its linked repository, github.com/ayuanxx-max/signoff-cli, belongs to the same GitHub account. These are facts from the registry and GitHub, not a rating.

Is io.github.ayuanxx-max/signoff-cli safe to install?

We do not rate servers as safe or unsafe. 9 of its 9 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its npm package carries a build-provenance attestation that names its source repository and build workflow. Its source repository opens publicly. Its repository had a push in the last 90 days. The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has no known advisory. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Has io.github.ayuanxx-max/signoff-cli been security tested?

No. It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's.

Does io.github.ayuanxx-max/signoff-cli publish a security policy?

Yes: its repository has a public security policy (github.com/ayuanxx-max/signoff-cli/blob/HEAD/SECURITY.md). That is the publisher's statement, not permission for us to test the server, and we call none of its tools.

Is the listed version current?

Yes. The registry lists 4.8.0, the latest stable release on npm.

Where is the source code of io.github.ayuanxx-max/signoff-cli?

In github.com/ayuanxx-max/signoff-cli, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

Has it been tested?

Feature #1

It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's. — our limit

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added at the next monthly refresh
listed 2026-11-13; not classified yet
Pricing modelAI-classified
not checked
no website in the registry entry
Programming language
api.github.com · 2026-11-13
Hosting type
registry · 2026-11-13
MCP capability
not checked
not read (no session)
Transport
standard input/output
registry · 2026-11-13
Required credentials
none declared
registry · 2026-11-13 · no declaration is not a guarantee
Package registry
registry · 2026-11-13
Freshness
0–30 days
registry updatedAt · 2026-11-13
Lifecycle status
registry · 2026-11-13
License class
package registry · 2026-11-13
Integrity hash
declared (sri)
package registry · 2026-11-13
Signature / provenance
package registry · 2026-11-13
Dependency advisories
none known
npm audit · 2026-11-13
Popularity
7,389 downloads a month
package registry · 2026-11-13
Publisher signals
owner: a personal account · repository age: 0–30 days · stars: 0–9 · build record: signed and attested
api.github.com · 2026-11-13
Maintenance
api.github.com · 2026-11-13
Environment
your machine
where it runs, from the hosting type · 2026-11-13

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.ayuanxx-max/signoff-cli: MCP server record.” Data checked 2026-11-13. https://protocolprobe.com/mcp/servers/io.github.ayuanxx-max/signoff-cli

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 9 of 9 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.ayuanxx-max/signoff-cli)](https://protocolprobe.com/mcp/servers/io.github.ayuanxx-max/signoff-cli)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).

Write to hello@protocolprobe.com · corrections log · methodology