VYKA Diamonds
REMOTE · VYKA-DIAMONDS-MCP.SAIMMEHMUDKHAN.WORKERS.DEV
Search VYKA's certified natural and lab-grown diamonds and get GIA or IGI report-check links.
Available components
Last scanned (21 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 21 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 Security63
- 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability60
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1624 tokens (~324/item across 5 items; 5 tools + 0 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 Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 57% of tool parameters carry a description.Partial
- 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 17 Nov 26 63
First indexed and scored.
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 21 Nov 2026 · Probed https://vyka-diamonds-mcp.saimmehmudkhan.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=saimmehmudkhan.workers.dev | CN=YE1,O=Let's Encrypt,C=US | 15 Oct 2026 | 13 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6f1502b121560e2177bedb235492a12e928 |
| SANs: *.saimmehmudkhan.workers.dev, saimmehmudkhan.workers.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 vyka-diamonds-mcp.saimmehmudkhan.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| workers.dev. | No DS | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://vyka-diamonds-mcp.saimmehmudkhan.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://vyka-diamonds-mcp.saimmehmudkhan.workers.dev/mcp | Inconclusive | 405 |
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 →
check_report Get a lab report-check link ~161
Returns the web address of the grading laboratory's own report-check page for a GIA or IGI report number, after checking that the number has that laboratory's format. Use this when the user wants to verify a diamond's grading report themselves. Limits: it only builds the link; it does not open, read or confirm the report, and only GIA and IGI are supported. For an IGI number starting with LG it also notes that such reports are normally for lab-grown diamonds.
| Name | Type | Req | Description |
|---|---|---|---|
| lab | string | yes | The laboratory that issued the report. |
| report_number | string | yes | The report number printed on the report (GIA: 7–10 digits; IGI: 7–10 digits, lab-grown reports may start with LG). |
| Name | Type | Req | Description |
|---|---|---|---|
| lab | string | yes | – |
| note | string | – | A reading tip about the number's format; the report itself is the authority. |
| report_check_url | string | yes | – |
| report_number | string | yes | – |
No examples provided.
get_diamond Get one VYKA diamond ~240
Returns one diamond from VYKA's diamond inventory by its certificate (report) number or VYKA stone code (VYK-…), with the details its page on vykadiamonds.com shows: grades, measurements, AED price (plus an indicative currency), photo, its page link and the laboratory's report-check link. Use this when the user gives a report number or VYK code, or to re-check a stone from search_diamonds before they decide or contact VYKA. Limits: only stones VYKA currently lists can be found. found is false when VYKA does not list that number now (it may have sold, or VYKA may never have listed it); that says nothing about whether the report is genuine, and report_check_links then gives the laboratory's own check. It does not verify the report itself.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | A GIA or IGI report number (e.g. 2141438171) or a VYKA stone code (e.g. VYK-I-612345678). |
| currency | string | – | Currency for the indicative price beside the AED price. |
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The report number that was looked up. |
| diamonds | array | yes | Usually one; more when two laboratories used the same number. |
| found | boolean | yes | – |
| report_check_links | array | – | Only when found is false: the laboratory report-check pages this number's format fits. The links are only built, not opened. |
No examples provided.
search_diamonds Search VYKA diamonds ~495
Returns loose diamonds currently listed on vykadiamonds.com (VYKA, Dubai), natural or lab-grown, with the same selection, order and prices as the website's diamond pages. Use this when the user wants to find or compare diamonds VYKA sells, by shape, carat, colour, clarity or budget. Only stones with a laboratory grading report are returned (natural: GIA, IGI or HRD; lab-grown: also GCAL). Unless the user sets a value, the website's own starting filters apply: natural 0.5 ct and up, colour D–H, clarity VS2 or better, Excellent or Ideal cut where the laboratory grades cut, Very Good or Excellent polish and symmetry; lab-grown 1.0 ct and up, colour D–F, clarity VS1 or better, Excellent or Ideal cut where graded, Excellent polish and symmetry; both: eye-clean, no tinge, returnable, with photo and 360° view, lowest price first. Any value the user gives replaces that default. Limits: at most 10 stones per call; stock changes quickly and a listed stone can sell at any time; AED prices are the charged prices, other currencies are indicative. Does not cover ring settings, finished rings, gemstones or fancy-colour diamonds, and cannot reserve or buy a stone.
| Name | Type | Req | Description |
|---|---|---|---|
| carat_max | number | – | Largest carat weight (20 = no upper limit). |
| carat_min | number | – | Smallest carat weight. |
| clarity_highest | string | – | Highest clarity grade to include (FL is the highest). |
| clarity_lowest | string | – | Lowest clarity grade to include, e.g. VS1 for 'VS1 or better'. |
| colour_highest | string | – | Highest colour grade to include (D is the highest). |
| colour_lowest | string | – | Lowest colour grade to include, e.g. G for 'G or better'. |
| currency | string | – | Currency of max_price and of the indicative price shown beside the AED price. |
| limit | integer | – | How many stones to return (1–10). |
| max_price | number | – | Highest price, in `currency`. |
| shape | array | – | One or more shapes. Leave out for every shape. |
| sort | string | – | – |
| type | string | yes | natural = mined diamonds; lab = lab-grown diamonds. |
| Name | Type | Req | Description |
|---|---|---|---|
| browse_link | string | yes | The matching diamond page on vykadiamonds.com. |
| count | integer | yes | – |
| currency_note | string | yes | – |
| diamonds | array | yes | – |
| type | string | yes | – |
No examples provided.
talk_to_jeweller Contact a VYKA jeweller on WhatsApp ~172
Returns a WhatsApp link to VYKA's sales line (+971 52 273 1161) with a pre-written first message, about a stone (report number or VYK code) or a vykadiamonds.com product page, in English or Arabic. Use this only when the user asks to contact VYKA, speak to a jeweller or enquire on WhatsApp. Limits: nothing is sent; the user opens the link, can edit the message and sends it themselves. No personal details are asked for or kept.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Language of the message and the website link. |
| product_url | string | – | Optional: a product page on vykadiamonds.com. |
| stone | string | – | Optional: the stone's report number or VYK code. |
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | yes | – |
| message | string | yes | The pre-written text the user can edit before sending. |
| phone | string | yes | – |
| stone_found | boolean|null | yes | For a stone: whether it is still listed. Null when no stone was given. |
| website_link | string|null | yes | The stone or product page the message refers to. |
| whatsapp_url | string | yes | – |
No examples provided.
vyka_score Get a VYKA Score ~354
Returns VYKA's 0–100 quality score for a diamond and how it was calculated. Use this when the user asks for the VYKA Score of a stone in VYKA's inventory (give its report number or VYK code) or wants a diamond they describe scored on VYKA's scale (give type, shape, carat, colour and clarity, and any of cut, polish, symmetry, fluorescence, lab, eye-clean and proportions). Limits: it is VYKA's own guide computed from the report figures, not a laboratory grade; natural and lab-grown diamonds are scored on separate scales that do not compare; only white diamonds in the ten main shapes are scored; figures left out make the score less certain (figures_used shows how many were used).
| Name | Type | Req | Description |
|---|---|---|---|
| carat | number | – | – |
| clarity | string | – | – |
| code | string | – | A report number or VYK code of a stone VYKA lists. Use either this or the specs below. |
| colour | string | – | – |
| crown_angle | number | – | – |
| cut | string | – | – |
| depth_percent | number | – | – |
| eye_clean | boolean | – | True when the listing says the stone is eye-clean, false when it says it is not. Leave out when unknown. |
| fluorescence | string | – | – |
| lab | string | – | The grading laboratory, if known. |
| length_mm | number | – | – |
| pavilion_angle | number | – | – |
| polish | string | – | – |
| shape | string | – | – |
| symmetry | string | – | – |
| table_percent | number | – | – |
| type | string | – | – |
| width_mm | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| figures_total | number|null | yes | – |
| figures_used | number|null | yes | – |
| kind | string | yes | – |
| method_url | string | yes | How the score works, on vykadiamonds.com. |
| note | string | yes | – |
| parts | – | yes | – |
| scale | string | yes | – |
| score | number | yes | 0–100. |
| stone | – | yes | – |
| strengths | array | yes | – |
| summary | string|null | yes | – |
| tier | string | yes | Exceptional 90+, Excellent 80s, Very good 70s, Good 60s, Fair below 60. |
| tradeoffs | array | yes | – |
No examples provided.
How do I install the VYKA Diamonds MCP server?
VYKA Diamonds is a hosted endpoint at https://vyka-diamonds-mcp.saimmehmudkhan.workers.dev/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 · vyka-diamonds-mcp.saimmehmudkhan.workers.dev
claude mcp add --transport http com-vykadiamonds-vyka-diamonds 'https://vyka-diamonds-mcp.saimmehmudkhan.workers.dev/mcp'
What is the VYKA Diamonds MCP server?
VYKA Diamonds is an MCP server listed in the public MCP registry as com.vykadiamonds/vyka-diamonds. Search VYKA's certified natural and lab-grown diamonds and get GIA or IGI report-check links. This page covers its hosted endpoint (https://vyka-diamonds-mcp.saimmehmudkhan.workers.dev/mcp).
Is the VYKA Diamonds MCP server safe to use?
VYKA Diamonds scores 65 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 VYKA Diamonds MCP server expose?
VYKA Diamonds exposes 5 tools: search_diamonds, get_diamond, check_report, talk_to_jeweller, vyka_score. Their descriptions and schemas cost roughly 1,422 tokens of context every time the server is loaded.
Does the VYKA Diamonds MCP server require authentication?
No. We connected to VYKA Diamonds without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the VYKA Diamonds MCP server still maintained?
VYKA Diamonds is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the VYKA Diamonds MCP server?
VerifyMCP ran 12 checks on VYKA Diamonds, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about VYKA Diamonds: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.