B+

getamber.dev

Item: getamber.dev
Rating: 89
Author: wmcp.sh

https://getamber.dev/api/mcp

89/100 · MCP Trust Grade · checked 5h ago · MCP 2025-03-26

✓ Watched since 2026-06-03 — behavioral baseline locked. We re-check this server's tool surface on a schedule; if it adds, removes, or silently rewrites a tool (rug-pull), we record it.

What it offers — 6 tools · Database

ambr_list_templates

List available contract templates on Ambr. Returns all active Ricardian Contract templates with their slugs, names, descriptions, categories, paramete

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

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, ma

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 v

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 verificati

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

Spec conformance20%100

✓ initialize → protocolVersion 2025-03-26
✓ initialize HTTP 200
✓ unknown method → -32601
✓ tools/list → 6 tools
✓ every tool has name + inputSchema

Security (OWASP MCP)30%100

6 tools scanned
no injection markup
no secret-path refs

Reliability / performance20%92

single-probe latency 249ms (PRELIMINARY — continuous uptime/p95 from proxy telemetry lands in v2)

Tool hygiene15%70

83% of tools have typed inputSchema
0/6 declare outputSchema
no unannotated destructive tools

Transparency / provenance15%70

HTTPS ✓
advertises protocol 2025-03-26

Observed behavior

No proxied traffic observed for this host yet. Connect it at /connect and its grade gains a measured Reliability score + per-tool behavioral evidence — the half a static scan can't produce.

Findings

No blocking issues found in the static + spec checks.

Grade another server

We re-grade getamber.dev on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.

Share this report card

A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.

MCP Trust report card — getamber.dev grade B+

Share on X Open card image

https://wmcp.sh/mcp/grade/getamber.dev

Embed this grade

A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.

Markdown (for your README)

[![MCP Trust Grade B+](https://wmcp.sh/mcp/grade/getamber.dev/badge.svg)](https://wmcp.sh/mcp/grade/getamber.dev)

HTML

<a href="https://wmcp.sh/mcp/grade/getamber.dev"><img src="https://wmcp.sh/mcp/grade/getamber.dev/badge.svg" alt="MCP Trust Grade B+ · wmcp.sh"></a>

Agents: check this before connecting

Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:

https://wmcp.sh/mcp/trust

How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.