Skip to content
MCP server

Ambr

By getambrAll Ambr servers

Ricardian contracts for AI agents — dual-format, SHA-256 bound, legible by construction.

First seen 2 Oct 2026. One server, whatever directories list it: each directory listing keeps its own page and history.

1
Directories
Collected by InvokeRank
7
Tools
From an anonymous probe
-
ToolBench grade
Not graded by Arcade
-
GitHub stars
No repository data

Tools

ToolDescriptionBehaviour
ambr_agent_handshakeInitiate a handshake on a contract on behalf of your delegating principal. Requires an API key with an active delegation (principal wallet registered via /api/v1/delegations). Records the agent's intent to accept, reject, or request changes on the contract. The principal must separately approve via wallet signature on the Reader Portal. Args: - contract_id (string, required): Contract ID (amb-YYYY-NNNN), SHA-256 hash, or UUID - intent (string, required): "accept" | "reject" | "request_changes" - message (string, optional): Note for the counterparty - visibility_preference (string, optional): "private" | "metadata_only" | "public" | "encrypted" Returns: Handshake status and next steps for principal approval. Legibility: the handshake itself is auditable — delegation scope, agent identity, and principal approval are recorded alongside the contract hash.Changes data
ambr_check_transactionCheck one payment against the limits of an agreement. Advisory only: Ambr compares what you report with the figures stored with the agreement; it does not authorize, block or see the payments it checks, and a "within_limits" answer is not an approval or a guarantee. It checks only what a program can check exactly: status, validity window, currency, per-transaction and monthly limits, a total budget, a price or monthly fee, the approval and escalation thresholds, and the category and action labels you send, matched exactly against the agreement's lists (case, spaces, dots, colons and hyphens are folded, and a leading "do not", "don't", "no", "not", "never", "avoid", "without" or "prohibited:" on a prohibited entry is ignored). The limits come from the form answers stored with the agreement, not from its text. It reads the delegation templates (general authorization, power of attorney, limited service, fleet) and the commerce templates (API access, compute SLA, task execution). If the agreement was amended, the newest approved version is checked. Free: no credits are burned. Amounts are compared in USD (USDC counts as USD) or in the template's own currency; a payment in another currency is not compared and the verdict is "incomplete". It does NOT read the agreement's human-readable text. Anything written in words (the scope, conditions, geographic limits, who may be paid, how a limit is measured) is for you to read yourself: always read the agreement's scope and conditions before acting on any answer. The response's "not_checked" lists, by path and never the text, parts to start with (each has a kind and a short reason; at most thirty are listed, "not_checked_count" has the total). It is a best-effort hint, not a complete list: an empty or short list does not mean there is nothing to read. Read the agreement itself through the contract read. Verdicts: - "within_limits": the template is one the check reads, the form answers are stored and valid, every limit they set was evaluated and passed, every figure written in digits or in common number words in the agreement's machine-readable text is accounted for, and at least one spending limit or price was evaluated. It says nothing about terms written in words. - "out_of_scope": a limit definitely fails (status, validity window, a cap, a payment that must equal what is left of a task price, a category or action that is not on a list held in the form answers, or that is prohibited). A permitted-action or category list found only in the agreement's text is never trusted to decide this: a miss there is "incomplete". - "needs_approval": an approval or escalation threshold is exceeded. "also_incomplete": true then means some limit could not be evaluated either; the reasons still carry it. - "incomplete": something could not be checked or placed: an input you did not send (category, action, currency, period_spent), a form answer the check cannot use, a figure or statement in the agreement's text that the form answers do not explain or contradict, wording beside a limit that names another period than the one period_spent covers, a date the check cannot place as the agreement's end, a miss on a permitted-action or category list found only in the agreement's text, a payment that is not a whole number of calls at the price per call, permitted counterparties (the request carries none), a payment model the check cannot match, an agreement without stored form answers or made from another template. Ambr does not hold funds or track spend: period_spent is what was already spent in the period the limit covers (this month for a monthly limit, fee or fleet budget, for a fleet the whole fleet's; the whole agreement so far for a total budget or task price). One payment above a limit fails without it. Access: a public contract is open to anyone; otherwise use the creator's API key or pass a share_token. Args: - contract_id (string, required): Contract ID (amb-YYYY-NNNN), SHA-256 hash, or UUID - amount (number, required): payment amount, zero or more - currency (string, optional): e.g. "USD" - category (string, optional): your own category label, matched exactly against the agreement's list - action (string, optional): the action the agent is taking, matched exactly against the agreement's lists - period_spent (number, optional): already spent in the period the limit covers (this month, or the whole agreement for a total budget) - share_token (string, optional): share token for a private contract Returns: verdict ("within_limits" | "out_of_scope" | "incomplete" | "needs_approval"), the per-rule checks, plain-language reasons, "not_checked" and "not_checked_count", "also_incomplete" when it applies, and the contract that was checked (contract_id, effective_contract_id, sha256_hash, reader_url).Read-only
ambr_create_contractGenerate a Ricardian Contract from a template. Creates a dual-format contract (human-readable legal text + machine-parsable JSON) using AI, linked by SHA-256 hash. The contract is stored on Ambr and accessible via the Reader Portal. Requires a valid API key (X-API-Key header on the HTTP request) with available credits. Use ambr_list_templates first to discover templates and their required parameters. Args: - template (string, required): Template slug (e.g. "d1-general-auth") - parameters (object, required): Template-specific parameters matching the schema - principal_declaration (object, required): { agent_id, principal_name, principal_type } - principal_wallet (string, optional): the deploying party's own wallet. It must differ from the counterparty wallet in parameters (same_wallet_both_parties otherwise); left out, the first wallet that signs fills the principal side - parent_contract_hash (string, optional): SHA-256 hash of a contract you created, which this one is created under (its oversight threshold then applies). Not for amendments: propose those with POST /api/v1/contracts/{id}/amend - oversight_threshold_usd (number, optional): spending level above which work created under this contract needs human approval. Children exceeding it halt at awaiting_principal_approval. Returns: - contract_id: Unique ID (e.g. "amb-2026-0042") - sha256_hash: SHA-256 hash for verification - status: Contract status - reader_url: URL to view in Reader Portal - credits_remaining: Remaining API credits Legibility: Output is dual-format by construction and replayable to the original SHA-256 hash — the basis of Ambr's legibility guarantee.Changes data
ambr_get_contractRetrieve a contract by ID, SHA-256 hash, or UUID. With a valid API key (contract creator): returns the full contract including human-readable text, machine-readable JSON, status, and principal declaration. Without authentication: returns metadata only (contract_id, status, hash, dates). Supports three lookup formats: - Contract ID: "amb-2026-0042" - SHA-256 hash: 64-character hex string - UUID: Standard UUID format Args: - id (string, required): Contract ID, SHA-256 hash, or UUID Returns: Full contract (if authorized) or metadata-only response. Legibility: retrieval preserves the dual-format pairing — prose and JSON always replay to the same SHA-256.Read-only
ambr_get_contract_statusCheck the status of a contract and its amendment chain. Returns the current status and any linked amendments (parent or child contracts). Useful for verifying if a contract is active, amended, or terminated. Args: - id (string, required): Contract ID, SHA-256 hash, or UUID Returns: - contract_id, status, created_at - amendment_type, parent_contract_hash - amendments: Array of child contracts (if any) Legibility: amendments are bilateral and themselves dual-format — the chain stays legible from original through every revision.Read-only
ambr_list_templatesList available contract templates on Ambr. Returns all active Ricardian Contract templates with their slugs, names, descriptions, categories, parameter schemas, and pricing. Use this to discover which templates are available before creating a contract with ambr_create_contract. No authentication required. Returns: Array of template objects with slug, name, description, category, parameter_schema, price_cents, and version fields. Legibility: templates are the parameter schema for the dual-format contracts you create — starting here keeps your request conformant and your output defensible.Read-only
ambr_verify_hashVerify a contract's SHA-256 hash to confirm document integrity. Checks whether the provided hash matches a contract stored on Ambr. Returns verification status, contract metadata, and Reader Portal URL if found. Args: - hash (string, required): SHA-256 hash (64-character hex string) Returns: - verified: boolean - contract_id: string (if found) - status: string (if found) - reader_url: string (if found) Legibility: verification is the point at which legibility becomes provable — matching hash means the prose a human reads and the JSON a machine parses are the same document that was originally signed.Read-only

Directory listings

DirectoryListingTierFirst seen
Official MCP RegistryAmbr-2 Oct 2026
Ambr MCP server | InvokeRank