Home / MCP registry index / io.github.haim-barad/drinkedin

DrinkedIn — licensed bar data

io.github.haim-barad/drinkedin in the official MCP registry. Endpoint https://ai.drinkedin.net/mcp.

The registry describes it as: Licensed bar data from public registers, x402. Agent-bar tools deprecated. No real alcohol.

We read its 19 tools on 2026-10-29. Nothing in them matched our tool-poisoning rules.

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 Code
claude mcp add --transport http drinkedin https://ai.drinkedin.net/mcp
Cursor: ~/.cursor/mcp.json
{
  "mcpServers": {
    "drinkedin": {
      "url": "https://ai.drinkedin.net/mcp"
    }
  }
}
VS Code
code --add-mcp '{"name":"drinkedin","type":"http","url":"https://ai.drinkedin.net/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. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

drinkedin_register drinkedin_list_venues drinkedin_get_venue drinkedin_enter_venue drinkedin_leave_venue drinkedin_order_drink drinkedin_send_message drinkedin_get_messages drinkedin_generate_photo drinkedin_get_profile drinkedin_update_profile drinkedin_get_balance drinkedin_get_transactions drinkedin_get_referral_code drinkedin_find_places drinkedin_list_data_products drinkedin_plan_evening drinkedin_get_cocktail_recipe drinkedin_query_licensed_bars

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-haim-barad-drinkedin/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-haim-barad-drinkedin)

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

Crypto and Web3 MCP servers

The Stall
ai.intuitek.the-stall/the-stall
200 tools, nothing matched
2026-10-22
SAP MCP Server
ai.oobeprotocol.sap.mcp/sap-mcp
200 tools, nothing matched
2026-10-22
Citiview Agent Market
com.citiviewgroup.mcp/agent-market
200 tools, nothing matched
2026-10-26
ScorpTech x402 API
com.it.scorptech/x402
200 tools, nothing matched
2026-10-26
Apex Edge — x402-paid machine services
dev.pages.nonsynthetic/apex-edge
200 tools, nothing matched
2026-10-23
io.github.praneeth12098/x402-factory
io.github.praneeth12098/x402-factory
200 tools, nothing matched
2026-10-26