Ambr
Generate SHA-256-bound Ricardian contracts your agent and humans can read before you automate payouts, access, or agent-to-agent deals.
Overview
Ambr is an MCP server for the Validate phase that creates SHA-256-bound Ricardian contracts legible to both humans and AI agents.
What is this MCP server?
- Ricardian contracts: human-legible text bound to machine format with SHA-256
- Remote MCP at https://getamber.dev/api/mcp (streamable-http, v0.3.0)
- Branded Ambr with sites ambr.run and getamber.dev
- Legible-by-construction workflow for AI agent agreements
- GitHub source: getambr/site
- Server version 0.3.0
- Contracts SHA-256 bound (per description)
- Remote endpoint https://getamber.dev/api/mcp
What problem does it solve?
Agent deals often live in vague chat instructions with no tamper-evident link between what humans agreed and what code enforces.
Who is it for?
Indie builders scoping agent services, API resale, or marketplace rules who need clear human-plus-machine contract artifacts early.
Skip if: Teams that only need informal README specs with no binding terms, or enterprises requiring full legal review without technical contract tooling.
What do I get? / Deliverables
You get dual-format, hash-bound agreements your agent can reference while stakeholders still read plain obligations before build and ship.
- Dual-format Ricardian contract artifacts
- SHA-256 integrity binding between prose and machine views
- Scoped agent obligations documented before implementation
Recommended MCP Servers
Journey fit
Validate is canonical because dual-format agreements clarify scope, obligations, and machine-enforceable terms before you build automation on top. Scope covers contractual boundaries and intent—not the frontend polish or post-launch analytics.
How it compares
Contract-structure MCP service, not a generic document editor skill or payment processor integration.
Common Questions / FAQ
Who is io.github.getambr/ambr-mcp-server for?
Solo builders and agent developers who need Ricardian-style agreements that bind human-readable terms to machine-readable forms via SHA-256.
When should I use io.github.getambr/ambr-mcp-server?
Use it during validate when scoping agent permissions, revenue shares, or service levels—and before automating enforcement in build or ship.
How do I add io.github.getambr/ambr-mcp-server to my agent?
Add the remote MCP URL https://getamber.dev/api/mcp (streamable-http) in your MCP client configuration and invoke Ambr tools from Claude Code, Cursor, or a compatible host.