Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

Ambr

REMOTE · GETAMBER.DEV · SCANNED AUG 3

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

Available components

+7 this week 69 Trust /100
Trust breakdown (6 categories)

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. How we score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability59
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 83% of tool parameters carry a description.Partial
Capabilities40
  • Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · getamber.dev

# add to Claude Code
claude mcp add --transport http getambr-ambr-mcp-server https://getamber.dev/api/mcp
# ~/.codex/config.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
    }
  }
}
# add to OpenClaw
openclaw mcp add getambr-ambr-mcp-server --url https://getamber.dev/api/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  getambr-ambr-mcp-server:
    url: "https://getamber.dev/api/mcp"
// mcp.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 we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 2 Aug 26 +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.

  • 31 Jul 26 +5
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Jul 26 +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.

  • 27 Jul 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 61

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://getamber.dev/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=getamber.dev CN=YR1,O=Let's Encrypt,C=US 6 Jul 2026 4 Oct 2026 RSA 2048 SHA256-RSA 56e3a5db904248bc84ec46563ad667aff3c
SANs: getamber.dev
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f
DNSSEC insecure

Validation of getamber.dev. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
getamber.dev. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://getamber.dev/api/mcp Verified 200
http (plaintext) http://getamber.dev/api/mcp HTTPS enforced 308 https://getamber.dev/api/mcp
MCP tools — 6 exposed · ~1,229 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
ambr_agent_handshake ~258

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.

NameTypeReqDescription
contract_idstringyesContract ID, SHA-256 hash, or UUID
intentstringyesHandshake intent
messagestringOptional note for counterparty
visibility_preferencestringOptional visibility preference for negotiation

No output schema declared.

No examples provided.

ambr_create_contract ~348

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.

NameTypeReqDescription
amendment_typestring
parametersobjectyesTemplate-specific parameters
parent_contract_hashstringSHA-256 hash of parent contract (for amendments)
principal_declarationobjectyes
templatestringyesTemplate slug from ambr_list_templates

No output schema declared.

No examples provided.

ambr_get_contract ~189

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.

NameTypeReqDescription
idstringyesContract ID (amb-YYYY-NNNN), SHA-256 hash, or UUID

No output schema declared.

No examples provided.

ambr_get_contract_status ~150

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.

NameTypeReqDescription
idstringyesContract ID (amb-YYYY-NNNN), SHA-256 hash, or UUID

No output schema declared.

No examples provided.

ambr_list_templates ~121

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

ambr_verify_hash ~163

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.

NameTypeReqDescription
hashstringyesSHA-256 hash to verify (64-character hex)

No output schema declared.

No examples provided.