Home / MCP registry index / wine.beyond/beyond-wine
Beyond Wine
wine.beyond/beyond-wine in the official MCP registry.
Endpoint https://beyond.wine/mcp.
The registry describes it as: Claims-based knowledge base for no/low ABV specialty beverages (producers, beverages, people).
We read its 11 tools on 2026-10-31. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Connect it
The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:
claude mcp add --transport http beyond-wine https://beyond.wine/mcp{
"mcpServers": {
"beyond-wine": {
"url": "https://beyond.wine/mcp"
}
}
}code --add-mcp '{"name":"beyond-wine","type":"http","url":"https://beyond.wine/mcp"}'Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.
Let Claude Code check servers as it adds them
With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.
claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-pluginsTools it advertises
search_claims get_claim search_producers get_producer search_beverages get_beverage get_entity list_entities get_context get_graph get_ontology
Tool changes
We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.
Fingerprint of its tools at our last full read (2026-10-31):
53bdc8d4b17609b0. A client can hash the tools it is served the same way and compare;
the full value and a hash per tool are in this page as JSON.
Run this server? Show the check in your README
The badge reflects the latest weekly read:
[](https://lazaretto.dev/mcp-registry/wine-beyond-beyond-wine)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.
Related
Memory and knowledge MCP servers
| pg.ddx.io: the PostgreSQL community's memory io.ddx.pg/archive | 125 tools, nothing matched 2026-10-27 |
| AgentMart ai.ciphyr.agentmart/agentmart | 112 tools, nothing matched 2026-10-21 |
| Wicked MCP io.github.choaticpixels/wicked-mcp | 108 tools, nothing matched 2026-10-26 |
| Wicked MCP io.github.WickedAPI/wicked-mcp | 108 tools, nothing matched 2026-10-27 |
| Anansi Haven io.github.kburrus64-max/anansi-haven | 89 tools, nothing matched 2026-10-29 |
| Webbersites x402 Data Api io.github.webberdesign/webbersites-x402-data-api | 78 tools, nothing matched 2026-10-22 |