Proofslip MCP server
{
"mcpServers": {
"proofslip": {
"command": "npx",
"args": [
"-y",
"@proofslip/mcp-server@latest"
],
"env": {
"DATABASE_URL": "postgresql://user:password@host:5432/db",
"TEST_DATABASE_URL": "postgresql://user:password@host:5432/db",
"BASE_URL": "https://...",
"CRON_SECRET": "<cron_secret>",
"RESEND_API_KEY": "<resend_api_key>",
"PROOFSLIP_API_KEY": "<proofslip_api_key>"
}
}
}
}{
"mcpServers": {
"proofslip": {
"command": "npx",
"args": [
"-y",
"@proofslip/mcp-server@latest"
],
"env": {
"DATABASE_URL": "postgresql://user:password@host:5432/db",
"TEST_DATABASE_URL": "postgresql://user:password@host:5432/db",
"BASE_URL": "https://...",
"CRON_SECRET": "<cron_secret>",
"RESEND_API_KEY": "<resend_api_key>",
"PROOFSLIP_API_KEY": "<proofslip_api_key>"
}
}
}
}{
"mcpServers": {
"proofslip": {
"command": "npx",
"args": [
"-y",
"@proofslip/mcp-server@latest"
],
"env": {
"DATABASE_URL": "postgresql://user:password@host:5432/db",
"TEST_DATABASE_URL": "postgresql://user:password@host:5432/db",
"BASE_URL": "https://...",
"CRON_SECRET": "<cron_secret>",
"RESEND_API_KEY": "<resend_api_key>",
"PROOFSLIP_API_KEY": "<proofslip_api_key>"
}
}
}
}{
"servers": {
"proofslip": {
"command": "npx",
"args": [
"-y",
"@proofslip/mcp-server@latest"
],
"env": {
"DATABASE_URL": "${input:database_url}",
"TEST_DATABASE_URL": "${input:test_database_url}",
"BASE_URL": "${input:base_url}",
"CRON_SECRET": "${input:cron_secret}",
"RESEND_API_KEY": "${input:resend_api_key}",
"PROOFSLIP_API_KEY": "${input:proofslip_api_key}"
}
}
},
"inputs": [
{
"id": "database_url",
"type": "promptString",
"description": "Database url",
"password": true
},
{
"id": "test_database_url",
"type": "promptString",
"description": "Test database url",
"password": true
},
{
"id": "base_url",
"type": "promptString",
"description": "Base url",
"password": true
},
{
"id": "cron_secret",
"type": "promptString",
"description": "Cron secret",
"password": true
},
{
"id": "resend_api_key",
"type": "promptString",
"description": "Resend api key",
"password": true
},
{
"id": "proofslip_api_key",
"type": "promptString",
"description": "Proofslip api key",
"password": true
}
]
}{
"mcpServers": {
"proofslip": {
"command": "npx",
"args": [
"-y",
"@proofslip/mcp-server@latest"
],
"env": {
"DATABASE_URL": "postgresql://user:password@host:5432/db",
"TEST_DATABASE_URL": "postgresql://user:password@host:5432/db",
"BASE_URL": "https://...",
"CRON_SECRET": "<cron_secret>",
"RESEND_API_KEY": "<resend_api_key>",
"PROOFSLIP_API_KEY": "<proofslip_api_key>"
}
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsoninstall npx -y @proofslip/mcp-serverversion 0.2.3
What it does
ProofSlip creates and verifies public proof objects that a specific GitHub Actions job ran for a specific commit. It uses GitHub Actions OIDC tokens to establish provider-backed job identity, and optionally observes deployment endpoints and stores unverified context labels. Developers use it to create auditable release proofs that can be verified by third parties without requiring authentication.
- Create a public proof URL after a GitHub Actions workflow deploys or releases a project, which can be shared with users or systems to verify that a deployment occurred.
- Verify an existing ProofSlip proof URL to check what was provider-verified (job identity, commit SHA, workflow run) versus what was unverified (submitted labels, deployment health status).
- Poll or fetch proof JSON to inspect the issuer details, observations, submitted context, expiry, and validity status of a release proof.
Tools this server exposes
| Tool | Does |
|---|---|
| create_release_proof | Create a provider-backed release proof by submitting a GitHub Actions OIDC token with optional deployment URL and context labels. |
| verify_proof_url | Verify an existing ProofSlip URL and report what provider facts, ProofSlip observations, submitted context, expiry, and limitations it contains. |
| fetch_proof_json | Fetch public proof JSON by proof ID to inspect issuer details, observations, submitted context, and validity status. |
| update_github_workflow | Prepare and propose a GitHub Actions workflow change to add ProofSlip proof creation after an existing deploy step. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.