# Digital Gemology: gem identification and gemstone properties (remote · digitalgemology.com)

Identify gemstones by refractive index, birefringence, SG, pleochroism and spectrum. Compare 7 gems

- 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-gem-identification/mcp-gems.md), [page](https://verifymcp.io/servers/com-digitalgemology-gem-identification/mcp-gems)

## Channel facts

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

## 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**: 65/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 734 tokens (~183/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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: gem identification and gemstone properties MCP server?

Digital Gemology: gem identification and gemstone properties is a hosted endpoint at https://digitalgemology.com/mcp/gems, 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-gem-identification 'https://digitalgemology.com/mcp/gems'
```

### Cursor

```json
{
  "mcpServers": {
    "com-digitalgemology-gem-identification": {
      "url": "https://digitalgemology.com/mcp/gems"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-digitalgemology-gem-identification": {
      "type": "http",
      "url": "https://digitalgemology.com/mcp/gems"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-digitalgemology-gem-identification]
url = "https://digitalgemology.com/mcp/gems"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-digitalgemology-gem-identification --url 'https://digitalgemology.com/mcp/gems' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-digitalgemology-gem-identification:
    url: "https://digitalgemology.com/mcp/gems"
```

### Netclaw

```json
{
  "McpServers": {
    "com-digitalgemology-gem-identification": {
      "Transport": "http",
      "Url": "https://digitalgemology.com/mcp/gems"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-digitalgemology-gem-identification -t streamable-http -u 'https://digitalgemology.com/mcp/gems'
```

### Other

```json
{
  "mcpServers": {
    "com-digitalgemology-gem-identification": {
      "type": "http",
      "url": "https://digitalgemology.com/mcp/gems"
    }
  }
}
```

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-05 (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-03 (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-02 (score 72, 0)

- [functional improvement] Stability: unverified → 0.03

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

First indexed and scored.

## MCP tools (4)

### `gem_properties` (~99 tokens)

Gemstone properties

Everything Digital Gemology measures about one gemstone: refractive index (both rays for doubly refractive stones), birefringence, dispersion, specific gravity, hardness, crystal system, critical angle, what a refractometer, polariscope and dichroscope show, its pleochroic colors and the lines and bands a hand spectroscope shows, with links to the free tools.

Input parameters:

- `gemstone` (string, required): Gemstone, as its slug.

### `identify_gem` (~273 tokens)

Match gem test readings

Match a stone's test readings against the seven gemstones Digital Gemology covers and rank them, saying which reading fits and which does not. Give any of: refractive index, birefringence, specific gravity, optic character, pleochroism, a spectrum line, or that the refractometer read over the limit. A match is a lead among seven stones only, not an identification.

Input parameters:

- `birefringence` (number): The difference between the two readings, for example 0.008; 0 for a singly refractive stone.
- `optic_character` (string): From the polariscope: singly refractive (stays dark) or doubly refractive (blinks light and dark).
- `over_the_limit` (boolean): True if the refractometer showed no reading because the stone is above about 1.81.
- `pleochroism` (string): What the dichroscope shows: none, weak, distinct or strong.
- `refractive_index` (number): A refractometer reading, for example 1.765.
- `specific_gravity` (number): Specific gravity, for example 4.0.
- `spectrum_line_nm` (number): A line or band seen in a hand spectroscope, in nanometres, for example 694.

### `compare_gemstones` (~113 tokens)

Tell two gemstones apart

Two gemstones side by side, and the tests that tell them apart: refractive index, birefringence (doubling of back facets, polariscope), specific gravity, dispersion (fire), hardness, pleochroism and spectrum, each with the free tool that shows it. For questions like 'how do I tell diamond from moissanite?'.

Input parameters:

- `gemstone_a` (string, required): The first gemstone, as its slug.
- `gemstone_b` (string, required): The second gemstone, as its slug.

### `absorption_spectrum` (~70 tokens)

Absorption spectrum

What a hand spectroscope shows for one gemstone: each absorption line and band with its position in nanometres, its cause (for example Cr3+ in ruby) and what it looks like, from Digital Gemology's Spectroscope.

Input parameters:

- `gemstone` (string, required): Gemstone, as its slug.

## Diagnostics

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

## Score history

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

## Common questions

### What is the Digital Gemology: gem identification and gemstone properties MCP server?

Digital Gemology: gem identification and gemstone properties is an MCP server listed in the public MCP registry as com.digitalgemology/gem-identification. Identify gemstones by refractive index, birefringence, SG, pleochroism and spectrum. Compare 7 gems. This page covers its hosted endpoint (https://digitalgemology.com/mcp/gems).

### Is the Digital Gemology: gem identification and gemstone properties MCP server safe to use?

Digital Gemology: gem identification and gemstone properties 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: gem identification and gemstone properties MCP server expose?

Digital Gemology: gem identification and gemstone properties exposes 4 tools: gem_properties, identify_gem, compare_gemstones, absorption_spectrum. Their descriptions and schemas cost roughly 555 tokens of context every time the server is loaded.

### Does the Digital Gemology: gem identification and gemstone properties MCP server require authentication?

No. We connected to Digital Gemology: gem identification and gemstone properties without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Digital Gemology: gem identification and gemstone properties MCP server still maintained?

Digital Gemology: gem identification and gemstone properties 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/gems
- Repository: https://github.com/cultrodistro/digitalgemology-mcp
- Website: https://digitalgemology.com/about/agents
- Changelog RSS feed: https://verifymcp.io/servers/com-digitalgemology-gem-identification/mcp-gems.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-digitalgemology-gem-identification/mcp-gems.json
- HTML version of this page: https://verifymcp.io/servers/com-digitalgemology-gem-identification/mcp-gems