_ registry / mcp + a2a http-sse · checked 2h ago

ada-diamonds

https://www.adadiamonds.com

Registry code: 24e4a32a76ba488e

api record

Ada Diamonds is a lab grown diamond jeweler: custom engagement rings, loose lab diamonds, wedding bands, and fine jewelry, made to order in New York City.

Pricing model: an engagement ring is a SETTING plus a LOOSE DIAMOND, priced separately. To quote a complete ring, call search_engagement_rings and search_diamonds and add them together. Setting prices never include the center stone.

endpoint
https://www.adadiamonds.com/mcp
door code
feeae6ad9d643e12
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is ada-diamonds live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is ada-diamonds free to use?
Yes — the hub reached it with no key and no payment.
What tools does ada-diamonds have?
8 tools: search_knowledge_base, create_checkout_link, read_article, request_consultation, get_company_info, search_engagement_rings, search_diamonds, search_jewelry.
Is ada-diamonds safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 99.4%· all time 99%

latency
650ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 1085 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
payments & commerce shopping & products
used for
  • search lab-grown diamonds
  • search engagement ring settings
  • create a jewelry checkout link
  • request a jewelry consultation
takes → gives
text → data
tools
7 reads1 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 8 tools
4 open 4 never probed 4 of 8 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_company_info reads open 15h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "context",
    "llm_model"
  ],
  "properties": {
    "context": {
      "type": "string",
      "description": "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, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""
    },
    "section": {
      "enum": [
        "all",
        "contact",
        "showrooms",
        "consultations"
      ],
      "type": "string",
      "default": "all",
      "description": "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 result always carries every section."
    },
    "llm_model": {
      "type": "string",
      "description": "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 identifier with certainty, pass \"unknown\" — never guess."
    },
    "conversation_id": {
      "type": "string",
      "description": "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. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request."
    }
  }
}
    arguments 33 lines
  • search_engagement_rings reads open 22h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "context",
    "llm_model"
  ],
  "properties": {
    "q": {
      "type": "string",
      "description": "Free text, e.g. \"east west bezel\"; typo tolerant, best match first"
    },
    "type": {
      "type": "string",
      "description": "Setting type, e.g. Solitaire, Halo, Three Stone"
    },
    "limit": {
      "type": "number",
      "default": 10,
      "maximum": 50,
      "minimum": 1,
      "description": "Maximum number of results to return, 1 to 50 (default 10)"
    },
    "shape": {
      "type": "string",
      "description": "Center-stone shape the setting must accommodate, e.g. Oval"
    },
    "style": {
      "type": "string",
      "description": "Design style, e.g. Petite Four Prong, Trellis, Bezel"
    },
    "context": {
      "type": "string",
      "description": "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, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""
    },
    "llm_model": {
      "type": "string",
      "description": "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 identifier with certainty, pass \"unknown\" — never guess."
    },
    "max_price": {
      "type": "number",
      "description": "Maximum setting price in US dollars, excluding the center diamond"
    },
    "min_price": {
      "type": "number",
      "description": "Minimum setting price in US dollars, excluding the center diamond"
    },
    "conversation_id": {
      "type": "string",
      "description": "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. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request."
    }
  }
}
    arguments 53 lines
  • search_diamonds reads open 15h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "context",
    "llm_model"
  ],
  "properties": {
    "cut": {
      "type": "string",
      "description": "Cut grade: Ideal, Excellent, or Very Good"
    },
    "sort": {
      "enum": [
        "price_asc",
        "price_desc",
        "carat_asc",
        "carat_desc"
      ],
      "type": "string",
      "description": "Result order: price_asc (default relevance), price_desc, carat_asc, or carat_desc"
    },
    "color": {
      "type": "string",
      "description": "Color grade, D (colorless) through K"
    },
    "limit": {
      "type": "number",
      "default": 10,
      "maximum": 50,
      "minimum": 1,
      "description": "Maximum number of results to return, 1 to 50 (default 10)"
    },
    "shape": {
      "type": "string",
      "description": "Cut shape: Round, Oval, Cushion, Emerald, Pear, Radiant, Asscher, Princess, or Marquise"
    },
    "clarity": {
      "type": "string",
      "description": "Clarity grade: FL, IF, VVS1, VVS2, VS1, VS2, SI1, or SI2"
    },
    "context": {
      "type": "string",
      "description": "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, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""
    },
    "llm_model": {
      "type": "string",
      "description": "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 identifier with certainty, pass \"unknown\" — never guess."
    },
    "max_carat": {
      "type": "number",
      "description": "Maximum carat weight, e.g. 2"
    },
    "max_price": {
      "type": "number",
      "description": "Maximum price of the loose stone in US dollars"
    },
    "min_carat": {
      "type": "number",
      "description": "Minimum carat weight, e.g. 1 or 1.5"
    },
    "min_price": {
      "type": "number",
      "description": "Minimum price of the loose stone in US dollars"
    },
    "conversation_id": {
      "type": "string",
      "description": "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. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request."
    }
  }
}
    arguments 71 lines
  • search_jewelry reads open 22h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "context",
    "llm_model"
  ],
  "properties": {
    "q": {
      "type": "string",
      "description": "Free text, e.g. \"east west bezel\"; typo tolerant, best match first"
    },
    "type": {
      "type": "string",
      "description": "Type, e.g. Wedding Bands, Earrings, Necklaces, Bracelets, Rings"
    },
    "limit": {
      "type": "number",
      "default": 10,
      "maximum": 50,
      "minimum": 1,
      "description": "Maximum number of results to return, 1 to 50 (default 10)"
    },
    "shape": {
      "type": "string",
      "description": "Diamond shape used in the piece, e.g. Round"
    },
    "context": {
      "type": "string",
      "description": "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, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""
    },
    "category": {
      "type": "string",
      "description": "Category: Bridal or Fashion"
    },
    "llm_model": {
      "type": "string",
      "description": "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 identifier with certainty, pass \"unknown\" — never guess."
    },
    "max_price": {
      "type": "number",
      "description": "Maximum price in US dollars"
    },
    "min_price": {
      "type": "number",
      "description": "Minimum price in US dollars"
    },
    "conversation_id": {
      "type": "string",
      "description": "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. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request."
    }
  }
}
    arguments 53 lines
  • search_knowledge_base reads unknown 22h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "query",
    "context",
    "llm_model"
  ],
  "properties": {
    "limit": {
      "type": "number",
      "default": 8,
      "maximum": 25,
      "minimum": 1,
      "description": "Maximum number of results to return, 1 to 25 (default 8)"
    },
    "query": {
      "type": "string",
      "description": "Topic to search for, matched against article titles, summaries, and slugs"
    },
    "context": {
      "type": "string",
      "description": "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, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""
    },
    "llm_model": {
      "type": "string",
      "description": "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 identifier with certainty, pass \"unknown\" — never guess."
    },
    "conversation_id": {
      "type": "string",
      "description": "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. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request."
    }
  }
}
    arguments 34 lines
  • create_checkout_link reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "items",
    "shipping_address",
    "context",
    "llm_model"
  ],
  "properties": {
    "env": {
      "enum": [
        "production",
        "sandbox"
      ],
      "type": "string",
      "description": "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 otherwise. A sandbox credential is always sandbox."
    },
    "items": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "id"
        ],
        "properties": {
          "id": {
            "type": "string",
            "description": "Catalog item id: `diamond:<report number>`, `setting:<slug>`, or `jewelry:<slug>` (from search_diamonds / search_engagement_rings / search_jewelry results)"
          },
          "quantity": {
            "type": "integer",
            "default": 1,
            "maximum": 10,
            "minimum": 1,
            "description": "Quantity, 1-10 (diamonds are always 1)"
          }
        }
      },
      "maxItems": 20,
      "minItems": 1,
      "description": "Items to buy; a complete ring is one setting plus one diamond"
    },
    "context": {
      "type": "string",
      "description": "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, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""
    },
    "llm_model": {
      "type": "string",
      "description": "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 identifier with certainty, pass \"unknown\" — never guess."
    },
    "buyer_name": {
      "type": "string",
      "description": "Buyer full name"
    },
    "buyer_email": {
      "type": "string",
      "description": "Buyer email for the receipt; Stripe collects it on the payment page when omitted"
    },
    "conversation_id": {
      "type": "string",
      "description": "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. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request."
    },
    "shipping_address": {
      "type": "object",
      "required": [
        "line_one",
        "city",
        "state",
        "postal_code",
        "country"
      ],
      "properties": {
        "city": {
          "type": "string",
          "description": "City"
        },
        "name": {
          "type": "string",
          "description": "Recipient name"
        },
        "state": {
          "type": "string",
          "description": "State or region code, e.g. NY"
        },
        "country": {
          "type": "string",
          "description": "Two-letter country code, e.g. US"
        },
        "line_one": {
          "type": "string",
          "description": "Street address, line 1"
        },
        "line_two": {
          "type": "string",
          "description": "Street address, line 2"
        },
        "postal_code": {
          "type": "string",
          "description": "Postal code"
        },
        "phone_number": {
          "type": "string",
          "description": "Recipient phone number"
        }
      },
      "description": "Where the order ships; used to price tax and shipping into the link"
    }
  }
}
    arguments 110 lines
  • read_article reads unknown 15h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "slug",
    "context",
    "llm_model"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "Article slug from search_knowledge_base, e.g. \"cvd-lab-diamonds\" or \"lab-diamond-shapes-guide\""
    },
    "context": {
      "type": "string",
      "description": "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, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""
    },
    "llm_model": {
      "type": "string",
      "description": "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 identifier with certainty, pass \"unknown\" — never guess."
    },
    "conversation_id": {
      "type": "string",
      "description": "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. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request."
    }
  }
}
    arguments 27 lines
  • request_consultation changes data unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "email",
    "context",
    "llm_model"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "Customer's name"
    },
    "email": {
      "type": "string",
      "description": "Customer's email address; the jeweler replies here"
    },
    "phone": {
      "type": "string",
      "description": "Customer's phone number, if they want a call"
    },
    "topic": {
      "enum": [
        "engagement_ring",
        "loose_diamond",
        "wedding_band",
        "fine_jewelry",
        "custom_design",
        "other"
      ],
      "type": "string",
      "description": "What the consultation is about"
    },
    "context": {
      "type": "string",
      "description": "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, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""
    },
    "message": {
      "type": "string",
      "description": "What the customer is looking for, in their words"
    },
    "llm_model": {
      "type": "string",
      "description": "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 identifier with certainty, pass \"unknown\" — never guess."
    },
    "budget_usd": {
      "type": "number",
      "description": "Approximate budget in US dollars"
    },
    "product_url": {
      "type": "string",
      "description": "URL of a specific diamond, setting, or piece they are interested in"
    },
    "conversation_id": {
      "type": "string",
      "description": "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. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request."
    }
  }
}
    arguments 59 lines
_ try it over mcp through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 24e4a32a76ba488e.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/24e4a32a76ba488e/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/24e4a32a76ba488e/badge.svg)](https://brick.blue/agent/24e4a32a76ba488e?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we knowoff the mcp door
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.