GemstoneAI
Analyze jewelry photos, see comparable listings and sales, and save the piece to a collection.
Installation
Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).
claude mcp add --transport http gemstoneai 'https://api.gemstoneaiapp.com/mcp'
{
"mcpServers": {
"gemstoneai": {
"type": "http",
"url": "https://api.gemstoneaiapp.com/mcp"
}
}
}
Documentation
Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.
Sommaire
GemstoneAI for Agents
GemstoneAI is a hosted remote MCP server that lets an AI assistant help someone with a piece of jewelry they own. The assistant can:
- analyze 1 to 5 photos of the piece and give a preliminary identification, with its alternatives, unknowns and the evidence that would settle them
- show photographed comparable listings and sales, each labelled as an asking price or a realized sale
- save the piece to the person's GemstoneAI collection, so it opens in the GemstoneAI app on their phone
https://api.gemstoneaiapp.com/mcp
There is nothing to install or run. Product page: gemstoneaiapp.com/agents.
Connect
Add the URL as a remote (Streamable HTTP) MCP server in any client that supports one. The client discovers sign-in on its own. The person signs in with the email they use in the GemstoneAI app, so the collection is the same; a new email gets a free account. Each new analysis uses a scan from that account's plan, the same as in the app.
Claude Code, as a plugin (adds the server and a jewelry-research skill):
/plugin marketplace add Iveye-Inc/gemstoneai-agents
/plugin install gemstoneai@gemstoneai
Claude Code, server only:
claude mcp add --transport http gemstoneai https://api.gemstoneaiapp.com/mcp
Then run /mcp in Claude Code to sign in.
Other clients (Claude on the web and desktop, ChatGPT developer mode, Cursor, VS Code, MCP Inspector): add a remote MCP server with the URL above and sign in when prompted.
Client support is listed on the product page. A client is marked tested only after the full journey (photo, analysis, comparables, save, reopen in the app) has passed in it.
Tools
| Tool | What it does | Annotations |
|---|---|---|
analyze_jewelry | Preliminary analysis of 1 to 5 photos of one piece. Takes photos (attached files) or image_urls (public https), and an optional idempotency_key. With no photos it returns an upload link the person opens on their phone. | writes, not destructive, idempotent, open world |
get_jewelry_analysis | Status or completed result of an analysis. Waits up to about 40 seconds while it is processing. | read-only |
find_jewelry_comparables | Photographed market listings and sales with source, link, price, price type, date found and the material differences from this piece. | read-only, open world |
save_collection_item | Saves the analyzed piece to the signed-in person's collection and returns a link that opens it in the app. | writes, not destructive, idempotent |
Results never carry numeric confidence. Uncertainty comes as alternatives, unknowns and next evidence. When GemstoneAI's own reads disagree about what the stone is, price context is withheld with the reason. When no priced comparables are found, the answer is "none found", never a value of zero.
Protocol and authentication
- Streamable HTTP, stateless, JSON responses. Initialize-based clients (protocol 2024-11-05 to 2025-11-25) and 2026-07-28 clients are supported.
- OAuth 2.1 with PKCE (S256). Discovery:
/.well-known/oauth-protected-resource/mcpand/.well-known/oauth-authorization-serveronapi.gemstoneaiapp.com. - Clients register with Client ID Metadata Documents or dynamic client registration. Loopback redirects may use any port.
- Tokens are bound to one person, one client and this server (RFC 8707). Access tokens last an hour; refresh tokens rotate.
- Scopes:
jewelry:analyzeandcollection:write.
Latency and limits
- An analysis typically takes 20 to 45 seconds.
analyze_jewelrywaits up to about 40 seconds, then returnsprocessingwith a retry interval. Comparables usually follow within a minute. - Repeating the same photos, or the same
idempotency_key, returns the same analysis and is not charged twice. - During the pilot there are daily evaluation limits per account and per integration. Developers can request pilot access on the product page.
What it is not
Results are preliminary analyses from photographs. They are not appraisals and do not establish authenticity, treatment, origin or certified value. The server never buys, sells, lists or contacts anyone, and it saves to a collection only when asked.
Privacy
Photos are used to analyze the piece and are kept with it in the person's GemstoneAI account, like a scan in the app. Location data is removed from every photo. See the Privacy Policy and Terms.
Repository layout
.claude-plugin/marketplace.json,plugins/gemstoneai/: the Claude Code plugin (MCP server config and the jewelry-research skill)openai/: the ChatGPT plugin package source;python scripts/build_openai_zip.pybuilds the ZIPserver.json: the entry in the official MCP Registry, published withscripts/publish_registry.py
Support
gemstoneaiapp@gmail.com
Questions fréquentes
Qu'est-ce que GemstoneAI ?
Analyze jewelry photos, see comparable listings and sales, and save the piece to a collection.
Comment installer GemstoneAI ?
Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http gemstoneai 'https://api.gemstoneaiapp.com/mcp'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.
Faut-il une clé API pour GemstoneAI ?
Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.
GemstoneAI est-il open source ?
Son code est public sur GitHub, mais le dépôt ne déclare pas de licence standard.
Qui maintient GemstoneAI ?
Il est publié par Iveye-Inc. AI.tn le référence sans le maintenir ni le recommander.
Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.