mcpbeat Sign in

Ambr MCP Server

answering

Ambr is answering right now. Last checked 12 min ago. It exposes 6 tools.

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

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 47 days of history · worst day 36%
47 days agonow
71.4%
Uptime 24h
65 of 91 checks
6
Tools
read from the server
382 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 2

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 25 August 2026. No other catalogue keeps this.

25 Aug a tool description was rewritten ambr_create_contract
25 Aug a tool changed the parameters it asks for ambr_create_contract

Ambr does not always answer

Over the last week it answered 95.9% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

run in your terminal
claude mcp add ambr-mcp-server --transport http https://getamber.dev/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "ambr-mcp-server": {
      "url": "https://getamber.dev/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.ambr-mcp-server]
url = "https://getamber.dev/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "ambr-mcp-server": {
      "url": "https://getamber.dev/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "ambr-mcp-server": {
      "url": "https://getamber.dev/api/mcp"
    }
  }
}

Available tools 6

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

ambr
ambr_agent_handshake
Initiate 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.
ambr_create_contract
Generate 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 } - parent_contract_hash (string, optional): SHA-256 hash of parent contract for amendments - 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. - amendment_type (string, optional): "original" | "amendment" | "extension" 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.
ambr_get_contract
Retrieve 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.
ambr_get_contract_status
Check 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.
ambr_list_templates
List 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.
ambr_verify_hash
Verify 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.

Endpoints

URLTransportStateLatencyChecked
https://getamber.dev/api/mcp streamable-http answering 253 ms 12 min ago

Alternatives to Ambr

same job, measured the same way
Gildara
by gildara

Operating contracts for AI agents. Structured instructions compiled into system prompts.

local only
Agentseal
by joeybrar

Verifiable action logs for AI agents. Every action is recorded in a SHA-256 hash chain.

33 installs/wk local only
Agent Guard
by mdfifty50-boop

Constitutional guardrails and loop detection for AI agents

35 installs/wk local only
JSON Contracts
by json-contracts

JSON contract registry and validator for structured LLM and agent outputs.

53 installs/wk local only
Smartpolicy
by smartpolicy-protocol

Runtime authorization for AI agents and smart contracts via an immutable on-chain policy registry

48 installs/wk local only
VisualSpec
by utkarshx27

Structured, constraint-aware visual generation and deterministic layout for AI agents

130 installs/wk local only
Trace Forge
by mdfifty50-boop

Structured execution trace and span logging for AI agents

28 installs/wk local only
Aethereum
by br9704

The team layer for AI coding agents: shared contracts, collision alerts, E2EE sessions.

75 installs/wk answering

Ambr — questions

Answers built from our own checks of this server.

What can Ambr do?
It exposes 6 tools, read directly from the server on our last check. Among them: ambr_agent_handshake, ambr_create_contract, ambr_get_contract, ambr_get_contract_status, ambr_list_templates, ambr_verify_hash. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Ambr working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 65 of 91 checks got a reply (71.4%), average response time 382 ms. The bar chart above shows every period we have measured.
Is Ambr still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect Ambr?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Ambr need an API key?
No. Ambr completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 6 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Ambr?
It answers our handshake in 382 ms on average, which is faster than 40% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.