Orange Peel
Server Details
Cited Hermès price & resale market data as MCP tools, with attribution. Not affiliated.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- AndyVoCo/orangepeel-mcp
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
6 toolsabout_orange_peelInspect
What Orange Peel is, what data an agent may cite, and exactly how to attribute it. Call this first.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
get_bag_priceInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| size | Yes | Numeric size, e.g. "25", "28", "18". | |
| model | Yes | Bag model, e.g. "Birkin", "Kelly", "Constance". |
get_benchmarkInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| city | Yes | City id, e.g. "nyc", "paris", "tokyo", "london". |
get_market_medianInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| spec | Yes | Supply spec key, e.g. "Birkin 25", "Kelly 28". |
get_price_historyInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| spec | Yes | Supply spec key, e.g. "Birkin 25". | |
| timeframe | No | 1m | 6m | 1y | 5y | all (window over the live series). |
get_price_increasesInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| brand | Yes | hermes | chanel |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!