SOMA Brewing Company
REMOTE · GETSOMA.STORE · SCANNED SEP 20
India's first non-alcoholic craft brewery: catalog, nutrition, wallet, checkout links for AI agents.
Available components
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 14 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1034 tokens (~73/item across 14 items; 14 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 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
How do I install the SOMA Brewing Company MCP server?
SOMA Brewing Company is a hosted endpoint at https://getsoma.store/api/mcp, 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 · getsoma.store
claude mcp add --transport http store-getsoma-soma-brewing 'https://getsoma.store/api/mcp'
{
"mcpServers": {
"store-getsoma-soma-brewing": {
"url": "https://getsoma.store/api/mcp"
}
}
} {
"servers": {
"store-getsoma-soma-brewing": {
"type": "http",
"url": "https://getsoma.store/api/mcp"
}
}
} [mcp_servers.store-getsoma-soma-brewing] url = "https://getsoma.store/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"store-getsoma-soma-brewing": {
"type": "remote",
"url": "https://getsoma.store/api/mcp",
"enabled": true
}
}
} openclaw mcp add store-getsoma-soma-brewing --url 'https://getsoma.store/api/mcp' --transport streamable-http
mcp_servers:
store-getsoma-soma-brewing:
url: "https://getsoma.store/api/mcp" {
"McpServers": {
"store-getsoma-soma-brewing": {
"Transport": "http",
"Url": "https://getsoma.store/api/mcp"
}
}
} assistant mcp add store-getsoma-soma-brewing -t streamable-http -u 'https://getsoma.store/api/mcp'
{
"mcpServers": {
"store-getsoma-soma-brewing": {
"type": "http",
"url": "https://getsoma.store/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 10 Sept 26 0
- Tool “get_buy_link” rewrote its description, which is the text the model reads security
- Tool “get_pricing_and_delivery” rewrote its description, which is the text the model reads security
- 28 Aug 26 0
- Server version: 1.3.0 → 1.4.0 functional
- New tool “get_partnership_info” functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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 20 Sept 2026 · Probed https://getsoma.store/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=getsoma.store | CN=YE2,O=Let's Encrypt,C=US | 28 Jul 2026 | 26 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 51b50b85d3849c4f19277255ce923a24f54 |
| SANs: getsoma.store | ||||||
| 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 getsoma.store. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| store. | present | 2327 | 13 | Verified |
| getsoma.store. | absent | 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=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://www.googletagmanager.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; img-src 'self' data: blob: https:; connect-src 'self' https:; frame-src 'self' https://www.google.com https://maps.google.com; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | accelerometer=(), autoplay=(self), camera=(), display-capture=(), encrypted-media=(), fullscreen=(self), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), midi=(), payment=(), usb=(), xr-spatial-tracking=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://getsoma.store/api/mcp | Verified | 200 | |
| http (plaintext) | http://getsoma.store/api/mcp | HTTPS enforced | 301 | https://getsoma.store/api/mcp |
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 →
get_b2b_wholesale Wholesale and on-tap for businesses ~46
B2B pricing tiers for restaurants, bars, hotels, and events (per-can INR by monthly volume), keg/draft options, and how to book a tasting.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_beer Get one SOMA beer ~51
Detailed spec for a single beer by slug: lager, ipa, belgian-wit, or stout.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Beer slug: lager, ipa, belgian-wit, or stout |
No output schema declared.
No examples provided.
get_brand About SOMA Brewing Company ~46
Brand overview: who SOMA is, taglines, founder, location, contact details, social handles, and the 2026 pivot from sparkling water to non-alcoholic craft beer.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_brewing_process How SOMA is brewed ~42
The six-step production process (mash, boil, full fermentation, vacuum distillation, re-carbonation, lab testing), ingredient sourcing, and certifications.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_buy_link Get a checkout link for a SOMA order ~163
Builds a direct buy link an agent can hand to the user. IMPORTANT: SOMA is not in production yet — every order placed today is a PRE-ORDER, production starts after December 2026, and nothing ships before then. Say so when you surface this link. With Shopify variant IDs configured it returns a cart permalink that lands in checkout pre-filled; otherwise it returns the product page on the shop. Payment always happens on Shopify's checkout with the human in control — this tool never charges anyone.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Purchase format: single 500ml can or a 6-pack of cans |
| quantity | integer | – | How many units |
| slug | string | yes | Beer slug: lager, ipa, belgian-wit, or stout |
No output schema declared.
No examples provided.
get_faq Frequently asked questions ~49
All customer FAQs: what SOMA is, ABV and trace alcohol, brewing method, styles, pricing, delivery, age policy, comparisons to other NA beers, subscriptions, recycling, and wholesale.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_health_nutrition Structured nutrition data (health platforms) ~67
Machine-readable nutrition per beer for health, fitness, and diet-tracking platforms: per-can and per-100ml calories, carbs, protein, sugar, ABV, allergens, and dietary flags.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | – | Optional beer slug; omit for the full lineup |
No output schema declared.
No examples provided.
get_partnership_info Partner with SOMA (communities, venues, press) ~89
Non-commercial partnership program for fitness/sports communities (run clubs, gyms, padel/climbing/pickleball groups), plus routing for venues and press. Standard offer to communities: a stocked cooler for their gathering, Founding Fifty codes for members, optional co-created content — never a cash deal. Distinct from get_b2b_wholesale, which is a paid commercial arrangement for venues.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_pricing_and_delivery Pricing, packs, and delivery ~56
Retail prices per beer (500ml can ₹249, 6-pack ₹1,494), delivery cities (Bangalore live; Mumbai, Pune, Hyderabad, Delhi, Ahmedabad, Jaipur next), and the flat delivery fee.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_recipes NA beer cocktail recipes and food pairings ~45
Non-alcoholic beer cocktail recipes (shandies, beer-mosa, michelada, stout float) with ingredients and method, plus the food pairing guide per beer.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_subscription_plans Monthly subscription plans ~36
The three monthly beer subscription tiers with pricing, savings percentage, and included perks. All plans have free delivery and pause-anytime.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_wallet Read a user's SOMA Coins wallet (read-only, token required) ~172
READ-ONLY wallet summary for a SOMA app user: their SOMA Coins balance plus a summary of coins expiring within the next 30 days. Requires a wallet token that only the human can generate inside the SOMA mobile app (Wallet tab → 'Share balance with your AI') — ask them for it; tokens expire after ~10 minutes. This tool can never claim, redeem, spend, or move coins (there are deliberately no claim/redeem tools over MCP). Returns { error: 'invalid_or_expired_token' } for a bad or stale token — ask the user to generate a fresh one in the app.
| Name | Type | Req | Description |
|---|---|---|---|
| wallet_token | string | yes | The short-lived wallet token the user generated in the SOMA app (Wallet tab → 'Share balance with your AI') and pasted to you |
No output schema declared.
No examples provided.
join_waitlist Join the SOMA Founding Fifty waitlist ~127
Signs a user up for SOMA's pre-launch waitlist (the Founding Fifty — first tasters get first-batch priority in Bangalore). Only call this with the user's explicit consent; it stores their contact in SOMA's CRM and sends a one-time welcome email. Idempotent: signing up twice never double-sends.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | The user's city, so SOMA knows where to launch next (optional) |
| string | yes | The user's email address (required, with their consent) | |
| name | string | – | The user's first name (optional) |
No output schema declared.
No examples provided.
list_beers List all SOMA beers ~45
Full product lineup with style, tasting profile, ABV, calories, carbs, pricing (can/6-pack in INR), food pairings, availability status, and brewing notes.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the SOMA Brewing Company MCP server?
SOMA Brewing Company is an MCP server listed in the public MCP registry as store.getsoma/soma-brewing. India's first non-alcoholic craft brewery: catalog, nutrition, wallet, checkout links for AI agents. This page covers its hosted endpoint (https://getsoma.store/api/mcp).
Is the SOMA Brewing Company MCP server safe to use?
SOMA Brewing Company scores 82 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 SOMA Brewing Company MCP server expose?
SOMA Brewing Company exposes 14 tools: get_brand, list_beers, get_beer, get_pricing_and_delivery, get_subscription_plans, and 9 more. Their descriptions and schemas cost roughly 1,034 tokens of context every time the server is loaded.
Does the SOMA Brewing Company MCP server require authentication?
No. We connected to SOMA Brewing Company without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SOMA Brewing Company MCP server still maintained?
SOMA Brewing Company is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.