{
"mcpServers": {
"option-beverage-mcp-server": {
"command": "<see-readme>",
"args": []
}
}
}No install config available. Check the server's README for setup instructions.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
License not specified.
Is it maintained?
Last commit 201 days ago.
Will it work with my client?
Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
No automated test available for this server. Check the GitHub README for setup instructions.
No known vulnerabilities.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationHave you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Persistent memory using a knowledge graph
Privacy-first. MCP is the protocol for tool access. We're the virtualization layer for context.
Pre-build reality check. Scans GitHub, HN, npm, PyPI, Product Hunt — returns 0-100 signal.
Monitor browser logs directly from Cursor and other MCP compatible IDEs.
MCP Security Weekly
Get CVE alerts and security updates for Option Beverage Mcp Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A Model Context Protocol (MCP) server that provides access to beverage data with 33 different beverages from around the world.
# Pull the latest image
docker pull ghcr.io/bdiep6/beverage-mcp-server:latest
# Run the server
docker run -p 8080:8080 -d --name beverage-server ghcr.io/bdiep6/beverage-mcp-server:latest
# Clone the repository
git clone https://github.com/bdiep6/beverage-mcp-server.git
cd beverage-mcp-server
# Build the Docker image
docker build -t beverage-mcp-server:latest .
# Run the container
docker run -p 8080:8080 -d --name beverage-server beverage-mcp-server:latest
Once running, the server provides these REST API endpoints:
GET /health - Health checkGET /api/beverages - Get all beveragesGET /api/beverages/{id} - Get beverage by IDGET /api/beverages/name/{name} - Search by nameGET /api/beverages/type/{type} - Search by typeGET /api/beverages/ingredient/{ingredient} - Search by ingredientGET /api/beverages/origin/{origin} - Search by originGET /api/beverages/calories/{calories} - Search by caloriesGET /api/beverages/count - Get total countusing var httpClient = new HttpClient();
var response = await httpClient.GetAsync("http://localhost:8080/api/beverages");
var json = await response.Content.ReadAsStringAsync();
const response = await fetch('http://localhost:8080/api/beverages');
const beverages = await response.json();
console.log(beverages);
import requests
response = requests.get('http://localhost:8080/api/beverages')
beverages = response.json()
print(beverages)
# Get all beverages
curl http://localhost:8080/api/beverages
# Search for tea beverages
curl http://localhost:8080/api/beverages/type/Tea
# Get beverage by ID
curl http://localhost:8080/api/beverages/1
The server contains 33 beverages including:
dotnet run
docker build -t beverage-mcp-server .
docker run -p 8080:8080 beverage-mcp-server
Visit these URLs after starting the server:
Also available on Docker Hub:
docker pull YOUR_DOCKERHUB_USERNAME/beverage-mcp-server:latest
MIT License