Digital Gemology: gemstone and diamond cut library
REMOTE · DIGITALGEMOLOGY.COM
Gemstone and diamond cuts: ray-traced brilliance, fire and sparkle in 7 gems, 3D and faceting files
Available components
Last scanned (12 minutes ago)
Scores higher than 62% 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 Usability66
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1381 tokens (~172/item across 8 items; 8 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 Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
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 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).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.
- 4 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.
- 2 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.
- 1 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 1042 → 1381 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- New tool “compare_cuts” functional
- New tool “recommend_cut” functional
- 31 Oct 26 72
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 5 Nov 2026 · Probed https://digitalgemology.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=digitalgemology.com | CN=WE1,O=Google Trust Services,C=US | 24 Sept 2026 | 23 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 5d433931b1fbdda10eeac109fcf2467e |
| SANs: digitalgemology.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of digitalgemology.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| digitalgemology.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; includeSubDomains; preload |
| content-security-policy | default-src 'none'; frame-ancestors 'none'; base-uri 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://digitalgemology.com/mcp | Verified | 200 | |
| http (plaintext) | http://digitalgemology.com/mcp | HTTPS enforced | 301 | https://digitalgemology.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 →
best_cuts_for_gemstone Best cuts for a gemstone ~84
The top ten brilliants and the top ten jewelry cuts in one gemstone, ranked by brilliance, fire and scintillation added together, with the stone's optical constants.
| Name | Type | Req | Description |
|---|---|---|---|
| gemstone | string | yes | Gemstone, as its slug. |
| kind | string | – | brilliants (round cuts), jewelry (fancy and step shapes) or both. |
No output schema declared.
No examples provided.
compare_cuts Compare two cuts ~131
Two cuts side by side in one gemstone: overall, brilliance, fire, scintillation, tilt, face-up spread and leakage from the Cut Performance Index, each cut's place in that stone, facets and size, and the products with prices and checkout links. For questions like 'oval or pear for my sapphire?'.
| Name | Type | Req | Description |
|---|---|---|---|
| cut_a | string | yes | The first cut's slug or name, for example 'oval'. |
| cut_b | string | yes | The second cut's slug or name, for example 'pear'. |
| gemstone | string | – | The stone to compare them in; diamond if left out. |
No output schema declared.
No examples provided.
cut_in_gemstone One cut in one gemstone ~82
How one cut performs in one gemstone: its headline, eight measured scores against the T73 round brilliant in the same stone, and its pros and cons. For questions like 'is an oval a good cut for sapphire?'.
| Name | Type | Req | Description |
|---|---|---|---|
| cut | string | yes | The cut's slug or name. |
| gemstone | string | yes | Gemstone, as its slug. |
No output schema declared.
No examples provided.
get_cut Get one cut ~113
Everything about one cut: what it is, measured specifications (facets, angles, depth, size, index gear), brilliance, fire and scintillation in all seven gemstones against the T73, the products with prices and checkout links, its questions and answers, and its page.
| Name | Type | Req | Description |
|---|---|---|---|
| cut | string | yes | The cut's slug or name, for example 'asscher', 'T73' or 'Old European'. |
| gemstone | string | – | Optional: also return the pros and cons of this cut in this stone. |
No output schema declared.
No examples provided.
get_cut_scores Cut Performance Index scores ~208
Scores from the Digital Gemology Cut Performance Index for every cut we sell: overall, brilliance, fire, scintillation, tilt, symmetry, spread, shape-norm and leakage, ray traced separately in diamond, moissanite, cubic zirconia, ruby, sapphire, emerald and amethyst, with each cut's place in its material. Filter by cut, category or material; with no filter, every row. Figures are unrounded. Never compare or rank scores across materials. Ruby and sapphire share one refractive index, so the same figures. Cuts not yet scored come with the reason.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | brilliants, jewelry, historic, house or platonic. |
| cut | string | – | The cut's slug or name, for example 'oval' or 'DG-M5'. |
| material | string | – | One stone (diamond, moissanite, cubic-zirconia, ruby, sapphire, emerald or amethyst); leave it out for all seven. |
No output schema declared.
No examples provided.
list_gemstones List the gemstones ~43
The seven gemstones every cut is measured in, with refractive index, critical angle, dispersion, hardness and specific gravity, and the three best cuts of each kind.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
recommend_cut Recommend a cut ~181
The best cuts in one gemstone for what matters to the buyer: overall light performance, brilliance, fire, scintillation (sparkle), spread (looks bigger for its weight), tilt (stays bright when tilted) or leakage (least light lost). Filter by family or outline. Returns a ranked short list with each cut's page and checkout links.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Only this family: brilliants, jewelry, historic or house. All if left out. |
| gemstone | string | yes | Gemstone, as its slug. |
| limit | integer | – | How many cuts to return, 1 to 20; 5 if left out. |
| priority | string | – | What to rank by; leakage ranks the least light lost first. overall if left out. |
| shape | string | – | Only cuts with this outline. All if left out. |
No output schema declared.
No examples provided.
search_cuts Search the cut library ~264
Search Digital Gemology's gem cuts and Platonic solids by name, style, shape or use (for example 'square step cut', 'round brilliant for moissanite', 'historic cushion', 'pear'). Returns each match with its page, facets, size, price and checkout links. Give a gemstone to add the cut's brilliance, fire and scintillation in that stone and to sort by them.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | brilliants, jewelry (fancy and step cuts), historic, house (our own designs) or platonic (solids, 3D files only). |
| cutting_files | boolean | – | Only cuts that are also sold as GemCad cutting files. |
| gemstone | string | – | Gemstone, as its slug. |
| limit | integer | – | How many cuts to return, 1 to 50; 10 if left out. |
| query | string | – | Free text. Leave it out to list every cut that fits the filters. |
| shape | string | – | Outline of the cut. |
| sort | string | – | relevance (default with a query), total (brilliance + fire + scintillation, the default with a gemstone and no query), brilliance, fire, scintillation, facets (most first) or name. |
No output schema declared.
No examples provided.
How do I install the Digital Gemology: gemstone and diamond cut library MCP server?
Digital Gemology: gemstone and diamond cut library is a hosted endpoint at https://digitalgemology.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 · digitalgemology.com
claude mcp add --transport http com-digitalgemology-cut-library 'https://digitalgemology.com/mcp'
What is the Digital Gemology: gemstone and diamond cut library MCP server?
Digital Gemology: gemstone and diamond cut library is an MCP server listed in the public MCP registry as com.digitalgemology/cut-library. Gemstone and diamond cuts: ray-traced brilliance, fire and sparkle in 7 gems, 3D and faceting files. This page covers its hosted endpoint (https://digitalgemology.com/mcp).
Is the Digital Gemology: gemstone and diamond cut library MCP server safe to use?
Digital Gemology: gemstone and diamond cut library scores 74 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 Digital Gemology: gemstone and diamond cut library MCP server expose?
Digital Gemology: gemstone and diamond cut library exposes 8 tools: search_cuts, get_cut, best_cuts_for_gemstone, cut_in_gemstone, list_gemstones, and 3 more. Their descriptions and schemas cost roughly 1,106 tokens of context every time the server is loaded.
Does the Digital Gemology: gemstone and diamond cut library MCP server require authentication?
No. We connected to Digital Gemology: gemstone and diamond cut library without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Digital Gemology: gemstone and diamond cut library MCP server still maintained?
Digital Gemology: gemstone and diamond cut library 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.