# 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

- Trust score: 74/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `digitalgemology.com`: 74/100 (this document), [markdown](https://verifymcp.io/servers/com-digitalgemology-cut-library/digitalgemology.md), [page](https://verifymcp.io/servers/com-digitalgemology-cut-library/digitalgemology)

## Channel facts

- Endpoint: `https://digitalgemology.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.2`

## 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-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - 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**: 66/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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.
- **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 9 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).

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-digitalgemology-cut-library 'https://digitalgemology.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-digitalgemology-cut-library": {
      "url": "https://digitalgemology.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-digitalgemology-cut-library": {
      "type": "http",
      "url": "https://digitalgemology.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-digitalgemology-cut-library]
url = "https://digitalgemology.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-digitalgemology-cut-library": {
      "type": "remote",
      "url": "https://digitalgemology.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-digitalgemology-cut-library --url 'https://digitalgemology.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-digitalgemology-cut-library:
    url: "https://digitalgemology.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-digitalgemology-cut-library": {
      "Transport": "http",
      "Url": "https://digitalgemology.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-digitalgemology-cut-library -t streamable-http -u 'https://digitalgemology.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-digitalgemology-cut-library": {
      "type": "http",
      "url": "https://digitalgemology.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-11-04 (score 74, +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.

### 2026-11-02 (score 73, +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.

### 2026-11-01 (score 72, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 1042 → 1381
- [functional improvement] Stability: unverified → 0.03
- [functional] New tool “compare_cuts”
- [functional] New tool “recommend_cut”

### 2026-10-31 (score 72)

First indexed and scored.

## MCP tools (8)

### `search_cuts` (~264 tokens)

Search the cut library

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.

Input parameters:

- `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.

### `get_cut` (~113 tokens)

Get one cut

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.

Input parameters:

- `cut` (string, required): 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.

### `best_cuts_for_gemstone` (~84 tokens)

Best cuts for a gemstone

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.

Input parameters:

- `gemstone` (string, required): Gemstone, as its slug.
- `kind` (string): brilliants (round cuts), jewelry (fancy and step shapes) or both.

### `cut_in_gemstone` (~82 tokens)

One cut in one gemstone

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?'.

Input parameters:

- `cut` (string, required): The cut's slug or name.
- `gemstone` (string, required): Gemstone, as its slug.

### `list_gemstones` (~43 tokens)

List the gemstones

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.

### `get_cut_scores` (~208 tokens)

Cut Performance Index scores

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.

Input parameters:

- `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.

### `compare_cuts` (~131 tokens)

Compare two cuts

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?'.

Input parameters:

- `cut_a` (string, required): The first cut's slug or name, for example 'oval'.
- `cut_b` (string, required): The second cut's slug or name, for example 'pear'.
- `gemstone` (string): The stone to compare them in; diamond if left out.

### `recommend_cut` (~181 tokens)

Recommend a cut

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.

Input parameters:

- `category` (string): Only this family: brilliants, jewelry, historic or house. All if left out.
- `gemstone` (string, required): 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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-digitalgemology-cut-library/digitalgemology#diagnostics

## Score history

- 2026-11-05: 74
- 2026-11-04: 74
- 2026-11-03: 73
- 2026-11-02: 73
- 2026-11-01: 72
- 2026-10-31: 72

## Common questions

### 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.

## Links

- Remote endpoint: https://digitalgemology.com/mcp
- Repository: https://github.com/cultrodistro/digitalgemology-mcp
- Website: https://digitalgemology.com/about/agents
- Changelog RSS feed: https://verifymcp.io/servers/com-digitalgemology-cut-library/digitalgemology.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-digitalgemology-cut-library/digitalgemology.json
- HTML version of this page: https://verifymcp.io/servers/com-digitalgemology-cut-library/digitalgemology