Digital Gemology cut library
com.digitalgemology/cut-librarydigitalgemology.comstreamable-httpv1.0.0Scanned
Gem cuts with ray-traced brilliance, fire and scintillation in 7 stones, plus 3D and faceting files.
6 tools: 2 change things and 4 only read.
- Reads private data · 1
- Reads text others write · 0
- Can send data out · 0
- No findings
Anlyon alternative
2 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
6 tools
Changes things 2Claude Code: ask
best_cuts_for_gemstoneThe 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.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Best cuts for a gemstone
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
cut_in_gemstoneHow 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.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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?'.
Annotations the server declares
- title: One cut in one gemstone
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 4Show 4 read-only tools
get_cutEverything 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, …No findings
Why it is in this group
- The name "get_cut" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get one cut
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_cut_scoresScores 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 s…No findings
Why it is in this group
- The name "get_cut_scores" says "get": a word for reading.
Description, as the server wrote it 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 and in moissanite, 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. Cuts not yet scored come with the reason.
Annotations the server declares
- title: Cut Performance Index scores
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_gemstonesThe 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.No findings
Why it is in this group
- The name "list_gemstones" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: List the gemstones
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
search_cutsSearch 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').Reads private dataNo findings
Why it is in this group
- The name "search_cuts" says "search": a word for reading.
What it can reach
- private-dataThe input names a file (input.cutting_files), and the tool reads: it reads files.
Description, as the server wrote it 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.
Annotations the server declares
- title: Search the cut library
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http cut-library https://digitalgemology.com/mcpclaude mcp add --transport http cut-library https://digitalgemology.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__cut-library__search_cuts",
"mcp__cut-library__get_cut",
"mcp__cut-library__list_gemstones",
"mcp__cut-library__get_cut_scores"
],
"ask": [
"mcp__cut-library__best_cuts_for_gemstone",
"mcp__cut-library__cut_in_gemstone"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as cut-library. Review it before you use it.
Capability tags behind 1 rule
- mcp__cut-library__search_cuts private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://anlyon.dev/api/v1/servers/com.digitalgemology/cut-library/verify?hash=c832d7e099dab8e5ad38bc445285d07b05a06e93ee65c76efd96d99402c7ba5a" | jq -e '.changed == false'Pinned hash c832d7e099da, from Oct 31, 2026, 20:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://anlyon.dev/servers/com.digitalgemology/cut-library/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://anlyon.dev/servers/com.digitalgemology/cut-library)Source: MCP Registry. Synced Oct 31, 2026, 20:17 UTC.