# Ambr (remote · getamber.dev)

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

- Trust score: 69/100 (medium)
- Change this week: +7
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `getamber.dev`: 69/100 (this document), [markdown](https://verifymcp.io/servers/getambr-ambr-mcp-server/api-mcp.md), [page](https://verifymcp.io/servers/getambr-ambr-mcp-server/api-mcp)

## Channel facts

- Endpoint: `https://getamber.dev/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.3.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 59/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1229 tokens (~204/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 94/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 83% of tool parameters carry a description.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http getambr-ambr-mcp-server https://getamber.dev/api/mcp
```

### Codex

```toml
[mcp_servers.getambr-ambr-mcp-server]
url = "https://getamber.dev/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "getambr-ambr-mcp-server": {
      "type": "remote",
      "url": "https://getamber.dev/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add getambr-ambr-mcp-server --url https://getamber.dev/api/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  getambr-ambr-mcp-server:
    url: "https://getamber.dev/api/mcp"
```

### Other

```json
{
  "mcpServers": {
    "getambr-ambr-mcp-server": {
      "type": "http",
      "url": "https://getamber.dev/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 68, +5)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 63, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 62, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 61)

First indexed and scored.

## MCP tools (6)

### `ambr_list_templates` (~121 tokens)

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_create_contract` (~348 tokens)

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
  \- 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.

Input parameters:

- `amendment_type` (string)
- `parameters` (object, required): Template-specific parameters
- `parent_contract_hash` (string): SHA-256 hash of parent contract (for amendments)
- `principal_declaration` (object, required)
- `template` (string, required): Template slug from ambr_list_templates

### `ambr_get_contract` (~189 tokens)

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.

Input parameters:

- `id` (string, required): Contract ID (amb-YYYY-NNNN), SHA-256 hash, or UUID

### `ambr_get_contract_status` (~150 tokens)

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.

Input parameters:

- `id` (string, required): Contract ID (amb-YYYY-NNNN), SHA-256 hash, or UUID

### `ambr_verify_hash` (~163 tokens)

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.

Input parameters:

- `hash` (string, required): SHA-256 hash to verify (64-character hex)

### `ambr_agent_handshake` (~258 tokens)

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.

Input parameters:

- `contract_id` (string, required): Contract ID, SHA-256 hash, or UUID
- `intent` (string, required): Handshake intent
- `message` (string): Optional note for counterparty
- `visibility_preference` (string): Optional visibility preference for negotiation

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/getambr-ambr-mcp-server/api-mcp#diagnostics

## Score history

- 2026-08-03: 69
- 2026-08-02: 69
- 2026-08-01: 68
- 2026-07-31: 68
- 2026-07-30: 63
- 2026-07-29: 63
- 2026-07-28: 63
- 2026-07-27: 62
- 2026-07-26: 61

## Links

- Remote endpoint: https://getamber.dev/api/mcp
- Repository: https://github.com/getambr/site
- Website: https://ambr.run/
- Changelog RSS feed: https://verifymcp.io/servers/getambr-ambr-mcp-server/api-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/getambr-ambr-mcp-server/api-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/getambr-ambr-mcp-server/api-mcp