What a Winevery tool call shares.

Inputs Winevery receives

Claude sends a protocol request and the arguments of the tool it selects. These can include a wine name, producer, grape, region, country, wine ID, dish description, heat preference, budget, currency or pagination. Winevery also receives normal connection metadata needed to deliver the request. Avoid putting sensitive personal information into these fields.

Winevery does not receive your general Claude conversations, unrelated files, Claude memory or the contents of other connectors. It only receives what your MCP client includes in a request to this endpoint.

Data the connector can return

The four tools return public wine profiles, recorded taste structure, available review summaries, food-family matches, similar-wine and pairing shortlists, matching reasons, optional price snapshots and links to Winevery pages. Missing values remain unknown. Price snapshots are not live offers or stock information.

The connector does not use account cookies or bearer tokens to authorise additional access. It has no account, cellar, journal, photo, Passport, payment or write tools. A website demo account does not change this public access scope.

Anthropic and other providers

Tool results are sent back to Anthropic when you use the connector in Claude. Anthropic handles those results under its own privacy practices and your Claude account settings. Other MCP clients have their own providers and policies.

The connector reads local Winevery data and runs local matching code. A tool call does not itself contact OpenAI, Stripe, PostShiba, LogSnag or Pirsch. Railway hosts the endpoint and can process infrastructure metadata and application logs. Opening a Winevery page from a result is a separate website visit covered by the website policy.

Use, storage and retention

Winevery processes the supplied arguments to perform the requested lookup or recommendation. The MCP application does not persist those arguments or create user profiles from them. Application diagnostics record tool name, success or failure and execution duration, without raw queries, dish text, account identifiers or conversation content.

A hash derived from a forwarded source-address hint is held in process memory for throttling. Its one-minute window expires automatically; entries are removed on later requests or process restart. The hash is not durably stored or logged by the MCP code. A global request limit also applies.

Hosting infrastructure can record request metadata under Railway’s configured operational retention. Diagnostic records are used for security, abuse prevention, reliability and support. Winevery does not sell MCP request content or use it to create advertising profiles.

Stopping access and asking for help

Disable the tools or disconnect Winevery in Claude to stop future calls through that connection. No Winevery OAuth token needs revoking because the catalogue endpoint does not require sign-in. Anthropic may retain responses already received according to its own settings and policies.

For privacy or security requests, contact the Winevery team at hello@winevery.com. Give the approximate request time and tool name where possible. Do not send your password, payment details or complete Claude conversation. See security reporting and connector documentation.