# rigforge MCP server

> Verifies AI coding agent claims by sealing finished work into signed ProofPackets that include hashed artifacts and HMAC signatures.

- Repository: https://github.com/mrodgersjs-web/rigforge
- Page: https://hostedmcp.org/servers/mrodgersjs-web/rigforge
- Transport: —
- Stars: 0
- License: MIT

## Environment variables

| Name | Required | Secret | Description |
|---|---|---|---|
| `GH_TOKEN` | no | no |  |

## FAQ

### How does rigforge prevent AI agents from lying about completed work?

It seals finished work into a ProofPacket where every artifact is hashed and the packet is HMAC-signed, allowing for verifiable re-checks.

### Can rigforge catch forged build claims?

Yes, it is designed to catch forged claims; benchmarks show it caught 8/8 forgeries with 1.00 accuracy in tested scenarios.

### Is the signing key shared with the AI agent?

No, the signing key stays with the user and is never shared with the agent.

### What is the security limitation of the HMAC signatures?

HMAC signatures are symmetric, which limits who can verify the packets.
