Orange Peel
REMOTE · ORANGEPEEL.TO · SCANNED SEP 25
Cited Hermès price & resale market data as MCP tools, with attribution. Not affiliated.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security51
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 539 tokens (~89/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the Orange Peel MCP server?
Orange Peel is a hosted endpoint at https://orangepeel.to/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · orangepeel.to
claude mcp add --transport http to-orangepeel-orangepeel 'https://orangepeel.to/api/mcp'
{
"mcpServers": {
"to-orangepeel-orangepeel": {
"url": "https://orangepeel.to/api/mcp"
}
}
} {
"servers": {
"to-orangepeel-orangepeel": {
"type": "http",
"url": "https://orangepeel.to/api/mcp"
}
}
} [mcp_servers.to-orangepeel-orangepeel] url = "https://orangepeel.to/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"to-orangepeel-orangepeel": {
"type": "remote",
"url": "https://orangepeel.to/api/mcp",
"enabled": true
}
}
} openclaw mcp add to-orangepeel-orangepeel --url 'https://orangepeel.to/api/mcp' --transport streamable-http
mcp_servers:
to-orangepeel-orangepeel:
url: "https://orangepeel.to/api/mcp" {
"McpServers": {
"to-orangepeel-orangepeel": {
"Transport": "http",
"Url": "https://orangepeel.to/api/mcp"
}
}
} assistant mcp add to-orangepeel-orangepeel -t streamable-http -u 'https://orangepeel.to/api/mcp'
{
"mcpServers": {
"to-orangepeel-orangepeel": {
"type": "http",
"url": "https://orangepeel.to/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Sept 26 0
- Stability: 0.97 → pass security
- 4 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Sept 2026 · Probed https://orangepeel.to/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=orangepeel.to | CN=WE1,O=Google Trust Services,C=US | 9 Sept 2026 | 8 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | e4108b36453ab5440e4f851875b566f3 |
| SANs: orangepeel.to, *.orangepeel.to | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of orangepeel.to. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| to. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob:; font-src 'self' data:; connect-src 'self'; object-src 'none'; frame-ancestors 'none'; base-uri 'self'; form-action 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://orangepeel.to/api/mcp | Verified | 200 | |
| http (plaintext) | http://orangepeel.to/api/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
about_orange_peel ~34
What Orange Peel is, what data an agent may cite, and exactly how to attribute it. Call this first.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_bag_price ~96
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 | Type | Req | Description |
|---|---|---|---|
| model | string | yes | Bag model, e.g. "Birkin", "Kelly", "Constance". |
| size | string | yes | Numeric size, e.g. "25", "28", "18". |
No output schema declared.
No examples provided.
get_benchmark ~84
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 | Type | Req | Description |
|---|---|---|---|
| city | string | yes | City id, e.g. "nyc", "paris", "tokyo", "london". |
No output schema declared.
No examples provided.
get_market_median ~77
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 | Type | Req | Description |
|---|---|---|---|
| spec | string | yes | Supply spec key, e.g. "Birkin 25", "Kelly 28". |
No output schema declared.
No examples provided.
get_price_history ~109
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 | Type | Req | Description |
|---|---|---|---|
| spec | string | yes | Supply spec key, e.g. "Birkin 25". |
| timeframe | string | – | 1m | 6m | 1y | 5y | all (window over the live series). |
No output schema declared.
No examples provided.
get_price_increases ~66
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 | Type | Req | Description |
|---|---|---|---|
| brand | string | yes | hermes | chanel |
No output schema declared.
No examples provided.
What is the Orange Peel MCP server?
Orange Peel is an MCP server listed in the public MCP registry as to.orangepeel/orangepeel. Cited Hermès price & resale market data as MCP tools, with attribution. Not affiliated. This page covers its hosted endpoint (https://orangepeel.to/api/mcp).
Is the Orange Peel MCP server safe to use?
Orange Peel scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Orange Peel MCP server expose?
Orange Peel exposes 6 tools: get_bag_price, get_market_median, get_price_history, get_price_increases, get_benchmark, about_orange_peel. Their descriptions and schemas cost roughly 466 tokens of context every time the server is loaded.
Does the Orange Peel MCP server require authentication?
No. We connected to Orange Peel without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Orange Peel MCP server still maintained?
Orange Peel is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.