Digital Gemology: gem identification and gemstone properties
REMOTE · DIGITALGEMOLOGY.COM
Identify gemstones by refractive index, birefringence, SG, pleochroism and spectrum. Compare 7 gems
Available components
Last scanned (1 hour ago)
Scores higher than 62% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Health and Science
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 Usability65
- AI-judged instruction clarity (good).Pass
- 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. 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 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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.
- 5 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.
- 3 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.
- 2 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 1 Nov 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/gems
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/gems | Verified | 200 | |
| http (plaintext) | http://digitalgemology.com/mcp/gems | HTTPS enforced | 301 | https://digitalgemology.com/mcp/gems |
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 →
absorption_spectrum Absorption spectrum ~70
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.
| Name | Type | Req | Description |
|---|---|---|---|
| gemstone | string | yes | Gemstone, as its slug. |
No output schema declared.
No examples provided.
compare_gemstones Tell two gemstones apart ~113
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?'.
| Name | Type | Req | Description |
|---|---|---|---|
| gemstone_a | string | yes | The first gemstone, as its slug. |
| gemstone_b | string | yes | The second gemstone, as its slug. |
No output schema declared.
No examples provided.
gem_properties Gemstone properties ~99
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.
| Name | Type | Req | Description |
|---|---|---|---|
| gemstone | string | yes | Gemstone, as its slug. |
No output schema declared.
No examples provided.
identify_gem Match gem test readings ~273
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
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.
remote · digitalgemology.com
claude mcp add --transport http com-digitalgemology-gem-identification 'https://digitalgemology.com/mcp/gems'
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.