# Ada Diamonds (remote · www.adadiamonds.com)

Live lab grown diamond inventory, engagement ring settings, fine jewelry, and diamond buying guides.

- Trust score: 72/100 (medium)
- Change this week: −6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `www.adadiamonds.com`: 72/100 (this document), [markdown](https://verifymcp.io/servers/com-adadiamonds-ada-diamonds/www.md), [page](https://verifymcp.io/servers/com-adadiamonds-ada-diamonds/www)

## Channel facts

- Endpoint: `https://www.adadiamonds.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-09-20.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - 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**: 79/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 3891 tokens (~228/item across 17 items; 8 tools + 9 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 35/100
  - Stability check failed: schema churn in the 26 days we've observed: 0 tool removals, 7 breaking changes, 0 auth/transport breaks, 1 additions.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).
  - Supports UI / widget rendering.

## Install

### How do I install the Ada Diamonds MCP server?

Ada Diamonds is a hosted endpoint at https://www.adadiamonds.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-adadiamonds-ada-diamonds 'https://www.adadiamonds.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-adadiamonds-ada-diamonds": {
      "url": "https://www.adadiamonds.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-adadiamonds-ada-diamonds": {
      "type": "http",
      "url": "https://www.adadiamonds.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-adadiamonds-ada-diamonds]
url = "https://www.adadiamonds.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-adadiamonds-ada-diamonds": {
      "type": "remote",
      "url": "https://www.adadiamonds.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-adadiamonds-ada-diamonds --url 'https://www.adadiamonds.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-adadiamonds-ada-diamonds:
    url: "https://www.adadiamonds.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-adadiamonds-ada-diamonds": {
      "Transport": "http",
      "Url": "https://www.adadiamonds.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-adadiamonds-ada-diamonds -t streamable-http -u 'https://www.adadiamonds.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-adadiamonds-ada-diamonds": {
      "type": "http",
      "url": "https://www.adadiamonds.com/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-09-19 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 28 to 32.

### 2026-09-18 (score 71, −9)

- [security regression] Stability: 0.77 → fail
- [security regression] A breaking change shipped without a version bump: still 1.0.0
- [functional regression] Schema quality: 111 → 228
- [functional regression] “create_checkout_link” added a required parameter “context”, so existing callers break
- [functional regression] “create_checkout_link” added a required parameter “llm_model”, so existing callers break
- [functional regression] “get_company_info” added a required parameter “context”, so existing callers break
- [functional regression] “get_company_info” added a required parameter “llm_model”, so existing callers break
- [functional regression] “read_article” added a required parameter “context”, so existing callers break
- [functional regression] “read_article” added a required parameter “llm_model”, so existing callers break
- [functional regression] “request_consultation” added a required parameter “context”, so existing callers break
- [functional regression] “request_consultation” added a required parameter “llm_model”, so existing callers break
- [functional regression] “search_diamonds” added a required parameter “context”, so existing callers break
- [functional regression] “search_diamonds” added a required parameter “llm_model”, so existing callers break
- [functional regression] “search_engagement_rings” added a required parameter “context”, so existing callers break
- [functional regression] “search_engagement_rings” added a required parameter “llm_model”, so existing callers break
- [functional regression] “search_jewelry” added a required parameter “context”, so existing callers break
- [functional regression] “search_jewelry” added a required parameter “llm_model”, so existing callers break
- [functional regression] “search_knowledge_base” added a required parameter “context”, so existing callers break
- [functional regression] “search_knowledge_base” added a required parameter “llm_model”, so existing callers break
- [cosmetic] “create_checkout_link” added an optional parameter “conversation_id”
- [cosmetic] “get_company_info” added an optional parameter “conversation_id”
- [cosmetic] “read_article” added an optional parameter “conversation_id”
- [cosmetic] “request_consultation” added an optional parameter “conversation_id”
- [cosmetic] “search_diamonds” added an optional parameter “conversation_id”
- [cosmetic] “search_engagement_rings” added an optional parameter “conversation_id”
- [cosmetic] “search_jewelry” added an optional parameter “conversation_id”
- [cosmetic] “search_knowledge_base” added an optional parameter “conversation_id”

### 2026-09-17 (score 80, +1)

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

### 2026-09-15 (score 79, +1)

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

### 2026-09-13 (score 78, +1)

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

### 2026-09-11 (score 77, +1)

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

### 2026-09-09 (score 76, +1)

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

### 2026-09-07 (score 75, +1)

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

## MCP tools (8)

### `search_diamonds` (~559 tokens)

Search loose lab diamonds

Search Ada Diamonds' live loose lab grown diamond inventory by shape, carat weight, price, color, clarity, and cut. Returns currently available stones with their grading report numbers and product URLs. Use this for any question about what diamond a budget can buy. MCP Apps-enabled: hosts that support MCP Apps render the results as an interactive card grid.

Input parameters:

- `clarity` (string): Clarity grade: FL, IF, VVS1, VVS2, VS1, VS2, SI1, or SI2
- `color` (string): Color grade, D (colorless) through K
- `context` (string, required): Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include,…
- `conversation_id` (string): Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it.
- `cut` (string): Cut grade: Ideal, Excellent, or Very Good
- `limit` (number): Maximum number of results to return, 1 to 50 (default 10)
- `llm_model` (string, required): The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model…
- `max_carat` (number): Maximum carat weight, e.g. 2
- `max_price` (number): Maximum price of the loose stone in US dollars
- `min_carat` (number): Minimum carat weight, e.g. 1 or 1.5
- `min_price` (number): Minimum price of the loose stone in US dollars
- `shape` (string): Cut shape: Round, Oval, Cushion, Emerald, Pear, Radiant, Asscher, Princess, or Marquise
- `sort` (string): Result order: price_asc (default relevance), price_desc, carat_asc, or carat_desc

Output parameters:

- `browseUrl` (string): Web page listing the full catalog for this search
- `items` (array): The matching entries, best match first
- `kind` (string): Which catalog the results come from
- `query` (object): The filters that were applied (only the ones you sent)
- `shown` (integer): How many entries are in `items`
- `total` (integer): How many catalog entries matched before the limit

### `search_engagement_rings` (~454 tokens)

Search engagement ring settings

Search Ada Diamonds' engagement ring settings by center-stone shape, style, and setting price. Setting prices exclude the center diamond — pair with search_diamonds to quote a complete ring. MCP Apps-enabled: hosts that support MCP Apps render the results as an interactive card grid.

Input parameters:

- `context` (string, required): Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include,…
- `conversation_id` (string): Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it.
- `limit` (number): Maximum number of results to return, 1 to 50 (default 10)
- `llm_model` (string, required): The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model…
- `max_price` (number): Maximum setting price in US dollars, excluding the center diamond
- `min_price` (number): Minimum setting price in US dollars, excluding the center diamond
- `q` (string): Free-text match on the setting name
- `shape` (string): Center-stone shape the setting must accommodate, e.g. Oval
- `style` (string): Design style, e.g. Petite Four Prong, Trellis, Bezel
- `type` (string): Setting type, e.g. Solitaire, Halo, Three Stone

Output parameters:

- `browseUrl` (string): Web page listing the full catalog for this search
- `items` (array): The matching entries, best match first
- `kind` (string): Which catalog the results come from
- `query` (object): The filters that were applied (only the ones you sent)
- `shown` (integer): How many entries are in `items`
- `total` (integer): How many catalog entries matched before the limit

### `search_jewelry` (~426 tokens)

Search fine jewelry

Search Ada Diamonds' fine jewelry — wedding bands, earrings, necklaces, bracelets, and fashion rings — by category, type, diamond shape, and price. MCP Apps-enabled: hosts that support MCP Apps render the results as an interactive card grid.

Input parameters:

- `category` (string): Category: Bridal or Fashion
- `context` (string, required): Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include,…
- `conversation_id` (string): Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it.
- `limit` (number): Maximum number of results to return, 1 to 50 (default 10)
- `llm_model` (string, required): The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model…
- `max_price` (number): Maximum price in US dollars
- `min_price` (number): Minimum price in US dollars
- `q` (string): Free-text match on the product name
- `shape` (string): Diamond shape used in the piece, e.g. Round
- `type` (string): Type, e.g. Wedding Bands, Earrings, Necklaces, Bracelets, Rings

Output parameters:

- `browseUrl` (string): Web page listing the full catalog for this search
- `items` (array): The matching entries, best match first
- `kind` (string): Which catalog the results come from
- `query` (object): The filters that were applied (only the ones you sent)
- `shown` (integer): How many entries are in `items`
- `total` (integer): How many catalog entries matched before the limit

### `search_knowledge_base` (~355 tokens)

Search Ada Diamonds guides

Search Ada Diamonds' published guides on lab grown diamonds — the 4Cs, CVD vs HPHT growth, shape guides, certification, and buying advice. Returns article summaries and markdown URLs. Use read_article to get an article's full text.

Input parameters:

- `context` (string, required): Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include,…
- `conversation_id` (string): Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it.
- `limit` (number): Maximum number of results to return, 1 to 25 (default 8)
- `llm_model` (string, required): The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model…
- `query` (string, required): Topic to search for, matched against article titles, summaries, and slugs

Output parameters:

- `browseUrl` (string): Web page listing every guide
- `items` (array): Matching articles
- `kind` (string): Always "articles"
- `query` (string): The search terms that were used
- `total` (integer): How many articles are in `items`

### `read_article` (~321 tokens)

Read a knowledge base article

Fetch the full markdown text of one Ada Diamonds knowledge base article by slug. Use search_knowledge_base first if you don't know the slug.

Input parameters:

- `context` (string, required): Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include,…
- `conversation_id` (string): Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it.
- `llm_model` (string, required): The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model…
- `slug` (string, required): Article slug from search_knowledge_base, e.g. "cvd-lab-diamonds" or "lab-diamond-shapes-guide"

Output parameters:

- `excerpt`: One-paragraph summary, when published
- `found` (boolean): False when no article has that slug
- `markdown`: The full article body as markdown, when found
- `slug` (string): The slug that was requested
- `title`: Article title, when found
- `url` (string): Article page URL

### `get_company_info` (~344 tokens)

Ada Diamonds company and showroom information

Contact details, showroom address and hours, how consultations work, and what Ada Diamonds sells. Use this to answer questions about the business rather than about a product.

Input parameters:

- `context` (string, required): Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include,…
- `conversation_id` (string): Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it.
- `llm_model` (string, required): The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model…
- `section` (string): Which part to return as text: contact (phone, email, hours, website), showrooms (addresses and hours), consultations (how remote and in-person consultations work), or all (default). The structured re…

Output parameters:

- `description` (string): What Ada Diamonds sells and how it works
- `email` (string): Customer email address
- `hours` (string): Business hours
- `inquiryUrl` (string): Page where a customer starts a consultation
- `name` (string): Legal company name
- `phone` (string): Main phone number
- `showrooms` (array): Physical showrooms
- `website` (string): Website URL

### `create_checkout_link` (~515 tokens)

Create a hosted checkout link

Assemble a cart and get a Stripe-hosted checkout URL the customer opens to pay; no card data passes through the agent. Item ids come from the search tools (`diamond:<report>`, `setting:<slug>`, `jewelry:<slug>`); a complete ring is one setting plus one diamond. Needs the shipping address (prices tax and shipping into the link). Expires after 24 hours. No credential needed. Without a production credential this tool runs in the sandbox: the link is simulated and no Stripe session is created. Pass `env: "production"` when the customer actually wants to buy — that returns a live, payable link.

Input parameters:

- `buyer_email` (string): Buyer email for the receipt; Stripe collects it on the payment page when omitted
- `buyer_name` (string): Buyer full name
- `context` (string, required): Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include,…
- `conversation_id` (string): Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it.
- `env` (string): sandbox returns a simulated link and creates no Stripe session; production mints a live, payable Stripe Checkout link. Defaults to sandbox for anonymous callers and to the credential's environment ot…
- `items` (array, required): Items to buy; a complete ring is one setting plus one diamond
- `llm_model` (string, required): The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model…
- `shipping_address` (object, required): Where the order ships; used to price tax and shipping into the link

Output parameters:

- `expires_at`: ISO timestamp the link stops working
- `message` (string): Human-readable outcome, including the link when ready
- `problems` (array): What blocks the link when status is needs_input
- `sandbox` (boolean): True when the link is simulated (sandbox): nothing is payable and no Stripe session was created. False means the link is live and payable.
- `shipping_usd` (number): Shipping in US dollars (0 = free insured FedEx)
- `status` (string): ready when a payable link was created; needs_input lists what is missing
- `subtotal_usd` (number): Items subtotal in US dollars
- `tax_usd` (number): Sales tax in US dollars for the given address
- `total_usd` (number): Total the buyer pays in US dollars
- `url`: The Stripe-hosted checkout URL, when ready

### `request_consultation` (~409 tokens)

Request a jeweler consultation

Submit a consultation request on the customer's behalf. Requires the `appointments:write` scope, which the customer grants through Ada's OAuth authorization flow — this tool cannot be used without their explicit approval.

Input parameters:

- `budget_usd` (number): Approximate budget in US dollars
- `context` (string, required): Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include,…
- `conversation_id` (string): Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it.
- `email` (string, required): Customer's email address; the jeweler replies here
- `llm_model` (string, required): The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model…
- `message` (string): What the customer is looking for, in their words
- `name` (string): Customer's name
- `phone` (string): Customer's phone number, if they want a call
- `product_url` (string): URL of a specific diamond, setting, or piece they are interested in
- `topic` (string): What the consultation is about

Output parameters:

- `email`: The customer email the request was filed under
- `message` (string): Human-readable outcome, including what to do next
- `reference`: Request reference, when received
- `sandbox` (boolean): True when a sandbox credential was used: nothing was created and nobody was contacted
- `status` (string): received when a request was recorded; otherwise why it was not

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-adadiamonds-ada-diamonds/www#diagnostics

## Score history

- 2026-09-20: 72
- 2026-09-19: 72
- 2026-09-18: 71
- 2026-09-17: 80
- 2026-09-16: 79
- 2026-09-15: 79
- 2026-09-14: 78
- 2026-09-13: 78
- 2026-09-12: 77
- 2026-09-11: 77
- 2026-09-10: 76
- 2026-09-09: 76
- 2026-09-08: 75
- 2026-09-07: 75
- 2026-09-06: 74
- 2026-09-05: 74
- 2026-09-04: 73
- 2026-09-03: 73
- 2026-09-02: 73
- 2026-09-01: 72
- 2026-08-31: 72
- 2026-08-30: 72
- 2026-08-29: 71
- 2026-08-28: 71
- 2026-08-27: 70
- 2026-08-26: 68
- 2026-08-25: 66

## Common questions

### What is the Ada Diamonds MCP server?

Ada Diamonds is an MCP server listed in the public MCP registry as com.adadiamonds/ada-diamonds. Live lab grown diamond inventory, engagement ring settings, fine jewelry, and diamond buying guides. This page covers its hosted endpoint (https://www.adadiamonds.com/mcp).

### Is the Ada Diamonds MCP server safe to use?

Ada Diamonds scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Ada Diamonds MCP server expose?

Ada Diamonds exposes 8 tools: search_diamonds, search_engagement_rings, search_jewelry, search_knowledge_base, read_article, and 3 more. Their descriptions and schemas cost roughly 3,383 tokens of context every time the server is loaded.

### Does the Ada Diamonds MCP server require authentication?

No. We connected to Ada Diamonds without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Ada Diamonds MCP server still maintained?

Ada Diamonds is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://www.adadiamonds.com/mcp
- Website: https://www.adadiamonds.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-adadiamonds-ada-diamonds/www.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-adadiamonds-ada-diamonds/www.json
- HTML version of this page: https://verifymcp.io/servers/com-adadiamonds-ada-diamonds/www