io.github.getambr/ambr-mcp-server

Est-ce que io.github.getambr/ambr-mcp-server est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.getambr/ambr-mcp-server » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 6 outils

• ambr_agent_handshake≈ 403 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.

  Paramètres, retour & exemple (4)

  Paramètres

  • intent · string · requis · accept | reject | request_changes
    Handshake intent
  • message · string · optionnel
    Optional note for counterparty
  • contract_id · string · requis
    Contract ID, SHA-256 hash, or UUID
  • visibility_preference · string · optionnel · private | metadata_only | public | encrypted
    Optional visibility preference for negotiation

  Exemple d'appel

  {"name": "ambr_agent_handshake", "arguments": {"intent": "accept", "contract_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ambr_create_contract≈ 706 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 - 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.

  Paramètres, retour & exemple (6)

  Paramètres

  • template · string · requis
    Template slug from ambr_list_templates
  • parameters · object · requis
    Template-specific parameters
  • amendment_type · string · optionnel · original | amendment | extension
  • parent_contract_hash · string · optionnel
    SHA-256 hash of parent contract (for amendments)
  • principal_declaration · object · requis
  • oversight_threshold_usd · number · optionnel
    Spending level above which work created UNDER this contract requires human approval. A child contract exceeding the parent threshold is held at awaiting_principal_approval until a human signs, and cannot be signed or activated before then (EU AI Act Art. 14).

  Exemple d'appel

  {"name": "ambr_create_contract", "arguments": {"template": "texte", "parameters": {}, "principal_declaration": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ambr_get_contract≈ 254 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.

  Paramètres, retour & exemple (1)

  Paramètres

  • id · string · requis
    Contract ID (amb-YYYY-NNNN), SHA-256 hash, or UUID

  Exemple d'appel

  {"name": "ambr_get_contract", "arguments": {"id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ambr_get_contract_status≈ 222 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.

  Paramètres, retour & exemple (1)

  Paramètres

  • id · string · requis
    Contract ID (amb-YYYY-NNNN), SHA-256 hash, or UUID

  Exemple d'appel

  {"name": "ambr_get_contract_status", "arguments": {"id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ambr_list_templates≈ 206 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.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "ambr_list_templates", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ambr_verify_hash≈ 239 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.

  Paramètres, retour & exemple (1)

  Paramètres

  • hash · string · requis
    SHA-256 hash to verify (64-character hex)

  Exemple d'appel

  {"name": "ambr_verify_hash", "arguments": {"hash": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://getamber.dev/api/mcp