Attestify Os
Run governed agent tool calls with spend budgets, x402 payments, signed receipts, and an audit trail you can prove to finance or compliance.
Overview
Attestify OS is an Operate-phase MCP server that governs agent execution with x402 payments, budgets, receipts, verification, and audit.
What is this MCP server?
- Governed /api/run execution with optional tenant API key (ATTESTIFY_API_KEY from POST /api/keys)
- x402 payment flows, budgets, receipts, verification, and audit logging in one MCP surface
- Dual transport: npm stdio (attestify-os 0.1.1) and remote streamable-http on attestify-os.vercel.app
- Discovery works without a key; governed runs require the issued API key
- MCP registry server schema 2025-12-11 with GitHub source at attestifyagent/attestify-os
- Server version 0.1.1
- 1 npm stdio package plus 1 streamable-http remote endpoint
- 1 secret env var: ATTESTIFY_API_KEY
What problem does it solve?
Agents that hit paid APIs or privileged actions leave you guessing about spend, proof of execution, and who approved what.
Who is it for?
Indie builders running payment-enabled or high-trust agent workflows who need receipts and audit before scaling usage.
Skip if: Static coding assistants with no external paid tools, or teams that only need local linting with zero spend governance.
What do I get? / Deliverables
After you register Attestify OS, agent runs can flow through a governed endpoint with budgets, receipts, and audit artifacts instead of unchecked tool calls.
- Governed agent runs via /api/run with policy-oriented execution
- Payment, budget, receipt, and verification artifacts tied to runs
- Auditable history suitable for operate-phase compliance review
Recommended MCP Servers
Journey fit
Production agent stacks need guardrails after you ship: who paid what, what ran, and whether it was verified—not something you solve only in the idea phase. Infra covers the execution plane (stdio npm package plus streamable HTTP remote at /api/run) that wraps agent runs with policy, not just app feature code.
How it compares
MCP execution governance and audit plane, not a brainstorming or planning agent skill.
Common Questions / FAQ
Who is Attestify OS for?
Solo and indie builders using Claude Code, Cursor, or similar agents who need budgets, payments, receipts, and audit on governed runs.
When should I use Attestify OS?
Use it in Operate (and late Build when wiring MCP) once agents call paid or sensitive tools and you need verification and an audit trail per run.
How do I add Attestify OS to my agent?
Add the npm MCP server attestify-os via stdio or point your client at the streamable-http remote URL; set ATTESTIFY_API_KEY for governed /api/run calls after POST /api/keys.