Origine Paris
com.origineparis/mcp · 0.9.0
Origine Paris MCP server: house, founders, catalogue. Recycled 18-carat gold, lab-grown diamonds.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 45 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 0 of 15 | The registry entry declares no key. That is what it declares, not a finding that it has no protection. |
| Latest connection test reached it | 20 of 20 |
Where it answers
https://mcp.origineparis.com/mcpstreamable-http
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 4 tools.
- Protocol
- 2025-06-18
- Calls itself
- origineparis 0.9.0
- Handshake time
- 80 ms
- HTTP status
- 200
The tools it lists (4, as of 2 days ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
get_maisonDescribes the house Origine Paris and its two founders, one section at a time, in French or English. Sections: overview (identity, SIREN, positioning, address, contacts, official profiles, how orders are placed), founders (roles, Wikidata QIDs, short biographies), person (one founder's referenced career, roles, education, citizenship), entity_graph (sourced nodes and edges), jsonld (the site's blocks in that language), agent_context (an orientation for agents) and llms_txt (the site llms.txt). Do not use it for pieces, prices or collections: search_catalogue, get_product_detail and list_collec
get_product_detailReturns the full published record of one piece of the Origine Paris catalogue, in French or English. Use it once a piece is chosen, from a search result or a product URL: the description exactly as published and never parsed, the price published on the site at the date of reading, variants and published sizes with the size guide, images, and the published statements on lead time, delivery, returns and care, each with its source URL and date. Do not use it to find or compare pieces (search_catalogue), to see the collections (list_collections) or for the house and its founders (get_maison). hand
search_catalogueFinds pieces in the published Origine Paris catalogue from free text, filters or both, in French or English. Every result carries its score and the reasons behind it, collections come back as facets with counts, and pages are stateless through limit (default 10, at most 50) and cursor. Parameters are hard filters, never relaxed; what the query text carries is soft: a jewellery type detected in the text is a tier, so a piece of another type never precedes one of the requested type, and the other types are served, with a notice, when nothing of that type matches; a price cap detected in the text
list_collectionsLists the published collections of the Origine Paris catalogue with the pieces this server serves in each, in French or English. Use it to see the catalogue by collection before searching: every visible collection carries its title, handle, page URL, number of pieces, published price range, the jewellery types it holds and the page where its description is published; the list is complete, unpaginated and alphabetical by title. Do not use it to find a piece (search_catalogue, whose collection filter takes a handle from this list), for the record of one piece (get_product_detail) or for the hous
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
com.origineparis/mcp, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 27 days ago. The registry entry · origineparis.com