Cellarion Wine Registry
REMOTE · CELLARION.APP
Public wine registry and guides: search wines, grapes, regions, appellations. No account.
Available components
Last scanned (2 hours ago)
Scores higher than 94% of remote servers
Reachable. Last reached 6 Nov 2026.
Category Entertainment and Games
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1242 tokens (~177/item across 7 items; 6 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management86
- Stability check failed: schema churn in the 30 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
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 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- Server version: 1.295.0 → 1.296.0 functional
- 5 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 1.294.0 → 1.295.0 functional
- Server version: 1.293.0 → 1.294.0 functional
- 2 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 1.292.0 → 1.293.0 functional
- 1 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 1.289.0 → 1.292.0 functional
- 31 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 1.286.0 → 1.289.0 functional
- 29 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 1.284.0 → 1.286.0 functional
- 28 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 1.281.0 → 1.284.0 functional
- 27 Oct 26 +62
- Stability: unverified → fail ▼ security
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Server version: 1.279.4 → 1.281.0 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 6 Nov 2026 · Probed https://cellarion.app/api/mcp/public
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=cellarion.app | CN=YE2,O=Let's Encrypt,C=US | 17 Oct 2026 | 15 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 65ff091aeab3a4c1173ca6dbf649f15188d |
| SANs: *.cellarion.app, cellarion.app | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of cellarion.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| app. | DS published | 23684 | 8 | Verified |
| cellarion.app. | No DS | 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=15552000; includeSubDomains |
| content-security-policy | default-src 'none';base-uri 'self';font-src 'self' https: data:;form-action 'self';frame-ancestors 'self';img-src 'self' data:;object-src 'none';script-src 'self';script-src-attr 'none';style-src 'self' https: 'unsafe-inline';upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://cellarion.app/api/mcp/public | Verified | 200 | |
| http (plaintext) | http://cellarion.app/api/mcp/public | HTTPS enforced | 301 | https://cellarion.app/api/mcp/public |
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 →
find_similar_wines Find similar wines ("more like this") ~216
Given a registry wine_id (or, on an authenticated connection, one of the user's bottle_ids), returns wines with the closest taste/style profile from the shared registry, using vector similarity over wine embeddings. Call for "more like this", "what else is like my favourite Barolo", or to seed purchase ideas from a wine the user loves. Only wines that have been embedded are searchable — an empty result does not mean nothing similar exists. Ids must be 24-hex Mongo ids from search_registry or search_bottles — a name or slug is not an id. Returns at most 10.
| Name | Type | Req | Description |
|---|---|---|---|
| bottle_id | string | – | Alternatively: one of the user's bottle ids (24-hex). Needs an authenticated connection — not available on the public endpoint. |
| limit | integer | – | How many to return (1-10, default 8; larger values are capped, not rejected) |
| wine_id | string | – | Registry wine id (24-hex) from search_registry or a bottle's wine |
No output schema declared.
No examples provided.
get_source_info About this Cellarion instance ~72
Returns what Cellarion is, the version this instance is running, the open-source repository, and the license. Call this when the user asks what Cellarion is, which version they are on, whether it is open source, where to find / contribute to the code — or how to support the project.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_wine Get one registry wine ~175
Full registry record for one wine: producer, region, appellation, classification, grapes, community rating, the AI tasting profile when the wine has been enriched, and the registry image (url + credit) when one is published — null means the wine has no public picture yet; to see the picture yourself, call get_photo with the wine_id. Vintage-neutral (bottles carry the vintage). For signed-in callers, pending_correction says whether a correction suggestion is awaiting review on this wine (one is allowed per wine, across all users), which fields it covers and whether it is the caller's own — check it before composing suggest_wine_correction. Call after search_registry when the user wants depth on a specific wine.
| Name | Type | Req | Description |
|---|---|---|---|
| wine_id | string | yes | Registry wine id from search_registry or a bottle's wine |
No output schema declared.
No examples provided.
list_guides List wine guides & articles ~112
Cellarion's published guides and blog articles (cellar management, drink windows, storage, buying) — title, slug, excerpt and tags. Call when the user wants a how-to or background reading; follow with read_guide for the full text.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many to return (1-20, default 10; larger values are capped, not rejected) |
| offset | integer | – | Skip this many (default 0) |
| tag | string | – | Filter by tag |
No output schema declared.
No examples provided.
read_guide Read a guide / article ~66
The full text of one published Cellarion guide or blog article, by slug (from list_guides). Public website content — quote or summarise freely, and link the public_url when pointing the user to it.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Article slug from list_guides |
No output schema declared.
No examples provided.
search_registry Search the shared wine registry ~142
Searches Cellarion's shared wine database (vintage-neutral wines, community data) by name, producer, region or grape. Returns up to 10 matches. Call to identify a wine the user mentions, before recommending, or to check whether a wine exists in the registry. This searches ALL known wines — use search_bottles for what the user owns. A signed-in user's own drinks that are not wine (beer, cider, soft drinks — hidden from the shared registry) are listed first with only_in_your_cellar: true, so they can add more of them.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Wine name, producer, appellation or grape |
No output schema declared.
No examples provided.
How do I install the Cellarion Wine Registry MCP server?
Cellarion Wine Registry is a hosted endpoint at https://cellarion.app/api/mcp/public, 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 · cellarion.app
claude mcp add --transport http app-cellarion-wine-registry 'https://cellarion.app/api/mcp/public'
What is the Cellarion Wine Registry MCP server?
Cellarion Wine Registry is an MCP server listed in the public MCP registry as app.cellarion/wine-registry. Public wine registry and guides: search wines, grapes, regions, appellations. No account. This page covers its hosted endpoint (https://cellarion.app/api/mcp/public).
Is the Cellarion Wine Registry MCP server safe to use?
Cellarion Wine Registry scores 87 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 Cellarion Wine Registry MCP server expose?
Cellarion Wine Registry exposes 6 tools: get_source_info, search_registry, get_wine, find_similar_wines, list_guides, read_guide. Their descriptions and schemas cost roughly 783 tokens of context every time the server is loaded.
Does the Cellarion Wine Registry MCP server require authentication?
No. We connected to Cellarion Wine Registry without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Cellarion Wine Registry MCP server still maintained?
Cellarion Wine Registry is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Cellarion Wine Registry MCP server?
VerifyMCP ran 13 checks on Cellarion Wine Registry, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.