attested MCP server
Commit Nov 3, 2026Allows coding agents to run tests into Sigstore-signed receipts and retrieve redacted failure packets for verifiable test results.
Also known as Praxso/attested, @praxso/attested-mcp
- Stars
- 0
- Tools
- 3
- Downloads, 30 days
- —
- Latest version
- 0.1.2
- Last commit
- Nov 3, 2026
- License
- Apache-2.0
What is attested MCP?
attested allows coding agents to run tests into Sigstore-signed receipts and retrieve redacted failure packets for verifiable test results. It exposes 3 tools, such as attested_run, attested_packet, attested_status.
Summary generated from the project's README
About attested MCP server
Coding agents that need to prove their test results through verifiable evidence can use this server to generate Sigstore-signed receipts. By running test commands through the attested_run tool, an agent receives a receipt summary or a redacted failure packet if the tests fail. This process ensures that the results are not just reported by the agent but are backed by a signed attestation that complies with GitHub attestation verification policies.
Developers set this up locally using Node 22 or newer via npx for clients like Claude Code or Codex. The server includes a bundled attested CLI, though users can specify a different binary by configuring the ATTESTED_BIN environment variable. It provides specific tools like attested_packet to retrieve the most recent failure packet and attested_status to check if a receipt is verified against a required check policy or remains unverified as a local receipt. This setup prevents agents from submitting pull requests without verifiable proof of passing tests.
What you can do with it
- 1Verify test results with signed receiptsAn AI agent can execute a test command and receive a signed receipt to prove the tests passed.
- 2Debug failed tests with redacted packetsWhen a test fails, the agent can retrieve a redacted failure packet to understand the error without exposing sensitive data.
- 3Check attestation verification statusA developer can use the server to confirm if a test run matches the required GitHub attestation policy.
Written from the project's README. Every use case is checked against a quote from it.
How to install attested MCP
Formats verified 10 Nov 2026Install attested MCP in Claude Code
$ claude mcp add attested -- npx -y @praxso/attested-mcpInstall attested MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"attested": {
"command": "npx",
"args": [
"-y",
"@praxso/attested-mcp"
]
}
}
}Install attested MCP in VS Code
.vscode/mcp.json
{
"servers": {
"attested": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@praxso/attested-mcp"
]
}
}
}Install attested MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"attested": {
"command": "npx",
"args": [
"-y",
"@praxso/attested-mcp"
]
}
}
}Install attested MCP in Codex
~/.codex/config.toml
[mcp_servers.attested] command = "npx" args = ["-y", "@praxso/attested-mcp"]
Install attested MCP in Gemini CLI
~/.gemini/settings.json
{
"mcpServers": {
"attested": {
"command": "npx",
"args": [
"-y",
"@praxso/attested-mcp"
]
}
}
}attested MCP tools 3
Detected from the READMEattested_runattested_packetattested_status
| attested_run | — | |
| attested_packet | — | |
| attested_status | — |
README
View on GitHub@praxso/attested-mcp
MCP server for attested: coding agents run your tests into a signed, verifiable receipt and read a redacted failure packet before they open a pull request.
Tools
attested_run: runs a test command through attested and returns the receipt summary; on red, the failure packet.attested_packet: returns the last failure packet, after checking its shape. A packet that is a symlink or resolves outside the project is refused.attested_status: returnsverified, the verdict from the signed attestation thatgh attestation verifyaccepts under the required check's policy (the attesting run and its ref, from the GitHub API orrun_id/source_ref, and the head commit), andlocalReceipt, the project's own receipt fields, labelled unverified.
The server runs the attested CLI bundled with it. To run a different build, set ATTESTED_BIN in the server's own MCP configuration; a node_modules/.bin/attested in the project is never used. If the bundled CLI cannot be resolved, attested_run fails with an error saying so; it never falls back to another version.
Set up
Claude Code:
claude mcp add attested -- npx -y @praxso/attested-mcp@0.1.2
Codex, in ~/.codex/config.toml:
[mcp_servers.attested]
command = "npx"
args = ["-y", "@praxso/attested-mcp@0.1.2"]
Cursor and Copilot configuration, the Claude Code plugin, and the Codex skill are in the repository README: https://github.com/Praxso/attested#agents-mcp-server-and-skills
Requires Node 22 or newer.
License
Apache-2.0
attested MCP questions
How do I add attested MCP to Claude Code?
Run claude mcp add attested -- npx -y @praxso/attested-mcp in your terminal. Add --scope user to make it available in every project.
How do I add attested MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does attested MCP provide?
It exposes 3 tools, including attested_run, attested_packet, attested_status.
How can I use a different version of the attested CLI?
You can set the ATTESTED_BIN environment variable in the MCP server's configuration to run a different build.
What happens if the bundled CLI cannot be found?
The attested_run tool will fail with an error message; it will not attempt to fall back to any other version.
Does the server use the local node_modules version of attested?
No, the server specifically avoids using a node_modules/.bin/attested located in the project.