signoff-mcp
MCP server for Signoff — exposes the harness over the Model Context Protocol so any MCP client (Claude Desktop, Cursor, Cline, Zed, Continue, custom agents) can ask for verification before marking work complete.
Depth + client-wiring examples: docs/mcp-integration.md.
Install
pip install signoff-mcp
Run
signoff-mcp # stdio + ./signoff.yaml
signoff-mcp --config /etc/signoff/harness.yaml
signoff-mcp --transport http --port 8765
signoff-mcp --health --transport http # probe a running HTTP server
Or as a container:
docker run -v $(pwd)/signoff.yaml:/app/signoff.yaml -p 8765:8765 signoff-mcp:dev
Tools (protocol §7.3)
| Tool | Purpose |
|---|---|
request_signoff |
Submit a deliverable + its claims. Returns a Verdict; if passed=false, the feedback_packet tells the agent what to fix. |
list_verifiers |
Return every loaded verifier plus its enabled-under-current-config status. |
get_verdict |
Optional per §7.3.3. This local server always returns an error; the hosted Signoff service implements persistent lookup. |
Auth
No auth by default — Phase 0 is a developer tool. Set SIGNOFF_MCP_AUTH_TOKEN=… and every non-/health//version request must carry Authorization: Bearer <token>.
Recommended agent prompt
Before marking any task complete, call
request_signoffwith your deliverable and claims. Ifverdict.passedisfalse, address each entry infeedback_packet.blockersand resubmit.
Metadata
Release files for signoff-mcp 0.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| signoff_mcp-0.0.1.tar.gz | 19.1 kB | Without provenance | Details for signoff_mcp-0.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| signoff_mcp-0.0.1-py3-none-any.whl | Python 3 | none | any | Details for signoff_mcp-0.0.1-py3-none-any.whl |
Total release size: 32.2 kB
Release files / signoff_mcp-0.0.1.tar.gz
| Download URL | signoff_mcp-0.0.1.tar.gz |
|---|---|
| Size | 19.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
24848aff045039404b267a490b14be52c23ecfd7c330d6e57e03b263612f120b
|
|
BLAKE2b-256 checksum How to use checksums |
6685209bfd126e13ae0e8e924731e2085b73a74322da58704cf1043df3cdf1c5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.8 {"installer":{"name":"uv","version":"0.11.8","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / signoff_mcp-0.0.1-py3-none-any.whl
| Download URL | signoff_mcp-0.0.1-py3-none-any.whl |
|---|---|
| Size | 13.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
95a619d645801ef59a2337ed9ac14bba0b3714c0854ad596b190c487f1a15e96
|
|
BLAKE2b-256 checksum How to use checksums |
4a3409c690d8935d1a2a0b45bba33260f07cb2239a4c72fa7808a007d0d3ffa0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.8 {"installer":{"name":"uv","version":"0.11.8","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for signoff-mcp 0.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.