mcp server
Orange Peel
Cited Hermès price & resale market data as MCP tools, with attribution. Not affiliated.
Description as published by the maintainer. Source
- version 1.0.0
- active
active — Registry entry last updated 2026-07-20.
What this server can do
6 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
about_orange_peel- What Orange Peel is, what data an agent may cite, and exactly how to attribute it. Call this first.
get_bag_price(size, model)- Current cited US retail list price and estimated pristine secondary-market (resale) price for a Hermès bag, plus the resale-over-retail premium. Figures are documented/estimated and cited — never an appraisal. Required: model, size.
get_benchmark(city)- The community-reported pre-spend BENCHMARK for a city: the median pre-spend ratio (cumulative boutique spend ÷ bag retail) at which buyers reported being offered a bag. Community-reported, position not probability. Required: city.
get_market_median(spec)- Live cross-site median of CURRENT ASKING prices for a bag spec across tracked resale marketplaces, with the count of listings (n) and the retrieval date. Median of ASKS, never sold — asking prices only. Required: spec.
get_price_history(spec, timeframe)- The LIVE weekly median-ASK series for a bag spec (our own cross-site measurement, public depth) within a timeframe. Archived (2015–2019 Internet-Archive) and cited SOLD anchors are partner-tier depth and are teased, not returned. Required: spec.
get_price_increases(brand)- The cited retail price-increase ledger for a brand (Hermès or Chanel): a dated record of verified past increases, each with source + retrieved date. A history of facts — never a forecast of the next hike. Required: brand.
Last successful function declaration observed on . Source: https://orangepeel.to/api/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://orangepeel.to/api/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-20 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-07-20 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 6 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | orangepeel.to | |
| mcp endpoint status | ok | The server listed 6 functions when asked. | as of probe | orangepeel.to |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json