Ada Diamonds
REMOTE · WWW.ADADIAMONDS.COM
Live lab grown diamond inventory, engagement ring settings, fine jewelry, and diamond buying guides.
Available components
Last scanned (1 hour ago)
Scores higher than 96% of remote servers
Reachable. Last reached 5 Nov 2026.
Category E-commerce
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 → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 4223 tokens (~248/item across 17 items; 8 tools + 9 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
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.
- 5 Nov 26 0
- Stability: 0.97 → pass security
- 4 Nov 26 0
- Stability: pass → 0.97 functional
- 30 Oct 26 0
- “create_checkout_link” reworded the description of “conversation_id” cosmetic
- “get_company_info” reworded the description of “conversation_id” cosmetic
- “read_article” reworded the description of “conversation_id” cosmetic
- “request_consultation” reworded the description of “conversation_id” cosmetic
- “search_diamonds” reworded the description of “conversation_id” cosmetic
- “search_engagement_rings” reworded the description of “conversation_id” cosmetic
- “search_jewelry” reworded the description of “conversation_id” cosmetic
- “search_knowledge_base” reworded the description of “conversation_id” cosmetic
8 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 24 Oct 26 0
- MCP protocol: Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28. functional
- MCP protocol version: 2026-07-28 → 2025-11-25 functional
- “search_engagement_rings” reworded the description of “q” cosmetic
- “search_jewelry” reworded the description of “q” cosmetic
- 18 Oct 26 +7
- Stability: fail → pass ▲ security
- 28 Sept 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
- 25 Sept 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
- 18 Sept 26 0
- Stability: 0.77 → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Schema quality: 111 → 228 ▼ functional
- “create_checkout_link” added a required parameter “context”, so existing callers break ▼ functional
- “create_checkout_link” added a required parameter “llm_model”, so existing callers break ▼ functional
- “get_company_info” added a required parameter “context”, so existing callers break ▼ functional
- “get_company_info” added a required parameter “llm_model”, so existing callers break ▼ functional
- “read_article” added a required parameter “context”, so existing callers break ▼ functional
- “read_article” added a required parameter “llm_model”, so existing callers break ▼ functional
- “request_consultation” added a required parameter “context”, so existing callers break ▼ functional
- “request_consultation” added a required parameter “llm_model”, so existing callers break ▼ functional
- “search_diamonds” added a required parameter “context”, so existing callers break ▼ functional
- “search_diamonds” added a required parameter “llm_model”, so existing callers break ▼ functional
- “search_engagement_rings” added a required parameter “context”, so existing callers break ▼ functional
- “search_engagement_rings” added a required parameter “llm_model”, so existing callers break ▼ functional
- “search_jewelry” added a required parameter “context”, so existing callers break ▼ functional
- “search_jewelry” added a required parameter “llm_model”, so existing callers break ▼ functional
- “search_knowledge_base” added a required parameter “context”, so existing callers break ▼ functional
- “search_knowledge_base” added a required parameter “llm_model”, so existing callers break ▼ functional
- “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” cosmetic
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 5 Nov 2026 · Probed https://www.adadiamonds.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=adadiamonds.com | CN=YE2,O=Let's Encrypt,C=US | 29 Oct 2026 | 27 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 67775f19c2ebeb9bc51ec142989d3392c7c |
| SANs: *.adadiamonds.com, adadiamonds.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.adadiamonds.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| adadiamonds.com. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.adadiamonds.com/mcp | Verified | 400 | |
| http (plaintext) | http://www.adadiamonds.com/mcp | HTTPS enforced | 308 | https://www.adadiamonds.com/mcp |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create_checkout_link Create a hosted checkout link ~554
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | – | Pass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Kee… |
| 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 | yes | Items to buy; a complete ring is one setting plus one diamond |
| llm_model | string | yes | 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 | yes | Where the order ships; used to price tax and shipping into the link |
| Name | Type | Req | Description |
|---|---|---|---|
| expires_at | string|null | yes | ISO timestamp the link stops working |
| message | string | yes | Human-readable outcome, including the link when ready |
| problems | array | yes | What blocks the link when status is needs_input |
| sandbox | boolean | yes | 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 | yes | Shipping in US dollars (0 = free insured FedEx) |
| status | string | yes | ready when a payable link was created; needs_input lists what is missing |
| subtotal_usd | number | yes | Items subtotal in US dollars |
| tax_usd | number | yes | Sales tax in US dollars for the given address |
| total_usd | number | yes | Total the buyer pays in US dollars |
| url | string|null | yes | The Stripe-hosted checkout URL, when ready |
No examples provided.
get_company_info Ada Diamonds company and showroom information ~383
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.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | 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 | – | Pass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Kee… |
| llm_model | string | yes | 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… |
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | What Ada Diamonds sells and how it works |
| string | yes | Customer email address | |
| hours | string | yes | Business hours |
| inquiryUrl | string | yes | Page where a customer starts a consultation |
| name | string | yes | Legal company name |
| phone | string | yes | Main phone number |
| showrooms | array | yes | Physical showrooms |
| website | string | yes | Website URL |
No examples provided.
read_article Read a knowledge base article ~360
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.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | 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 | – | Pass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Kee… |
| llm_model | string | yes | 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 | yes | Article slug from search_knowledge_base, e.g. "cvd-lab-diamonds" or "lab-diamond-shapes-guide" |
| Name | Type | Req | Description |
|---|---|---|---|
| excerpt | string|null | yes | One-paragraph summary, when published |
| found | boolean | yes | False when no article has that slug |
| markdown | string|null | yes | The full article body as markdown, when found |
| slug | string | yes | The slug that was requested |
| title | string|null | yes | Article title, when found |
| url | string | yes | Article page URL |
No examples provided.
request_consultation Request a jeweler consultation ~448
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.
| Name | Type | Req | Description |
|---|---|---|---|
| budget_usd | number | – | Approximate budget in US dollars |
| context | string | yes | 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 | – | Pass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Kee… |
| string | yes | Customer's email address; the jeweler replies here | |
| llm_model | string | yes | 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 |
| Name | Type | Req | Description |
|---|---|---|---|
| string|null | yes | The customer email the request was filed under | |
| message | string | yes | Human-readable outcome, including what to do next |
| reference | string|null | yes | Request reference, when received |
| sandbox | boolean | yes | True when a sandbox credential was used: nothing was created and nobody was contacted |
| status | string | yes | received when a request was recorded; otherwise why it was not |
No examples provided.
search_diamonds Search loose lab diamonds ~598
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.
| Name | Type | Req | Description |
|---|---|---|---|
| clarity | string | – | Clarity grade: FL, IF, VVS1, VVS2, VS1, VS2, SI1, or SI2 |
| color | string | – | Color grade, D (colorless) through K |
| context | string | yes | 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 | – | Pass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Kee… |
| 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 | yes | 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 |
| Name | Type | Req | Description |
|---|---|---|---|
| browseUrl | string | yes | Web page listing the full catalog for this search |
| items | array | yes | The matching entries, best match first |
| kind | string | yes | Which catalog the results come from |
| query | object | yes | The filters that were applied (only the ones you sent) |
| shown | integer | yes | How many entries are in `items` |
| total | integer | yes | How many catalog entries matched before the limit |
No examples provided.
search_engagement_rings Search engagement ring settings ~503
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.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | 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 | – | Pass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Kee… |
| limit | number | – | Maximum number of results to return, 1 to 50 (default 10) |
| llm_model | string | yes | 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, e.g. "east west bezel"; typo tolerant, best match first |
| 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 |
| Name | Type | Req | Description |
|---|---|---|---|
| browseUrl | string | yes | Web page listing the full catalog for this search |
| items | array | yes | The matching entries, best match first |
| kind | string | yes | Which catalog the results come from |
| query | object | yes | The filters that were applied (only the ones you sent) |
| shown | integer | yes | How many entries are in `items` |
| total | integer | yes | How many catalog entries matched before the limit |
No examples provided.
search_jewelry Search fine jewelry ~475
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Category: Bridal or Fashion |
| context | string | yes | 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 | – | Pass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Kee… |
| limit | number | – | Maximum number of results to return, 1 to 50 (default 10) |
| llm_model | string | yes | 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, e.g. "east west bezel"; typo tolerant, best match first |
| shape | string | – | Diamond shape used in the piece, e.g. Round |
| type | string | – | Type, e.g. Wedding Bands, Earrings, Necklaces, Bracelets, Rings |
| Name | Type | Req | Description |
|---|---|---|---|
| browseUrl | string | yes | Web page listing the full catalog for this search |
| items | array | yes | The matching entries, best match first |
| kind | string | yes | Which catalog the results come from |
| query | object | yes | The filters that were applied (only the ones you sent) |
| shown | integer | yes | How many entries are in `items` |
| total | integer | yes | How many catalog entries matched before the limit |
No examples provided.
search_knowledge_base Search Ada Diamonds guides ~394
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.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | 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 | – | Pass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Kee… |
| limit | number | – | Maximum number of results to return, 1 to 25 (default 8) |
| llm_model | string | yes | 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 | yes | Topic to search for, matched against article titles, summaries, and slugs |
| Name | Type | Req | Description |
|---|---|---|---|
| browseUrl | string | yes | Web page listing every guide |
| items | array | yes | Matching articles |
| kind | string | yes | Always "articles" |
| query | string | yes | The search terms that were used |
| total | integer | yes | How many articles are in `items` |
No examples provided.
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.
remote · www.adadiamonds.com
claude mcp add --transport http com-adadiamonds-ada-diamonds 'https://www.adadiamonds.com/mcp'
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 88 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,715 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.