Energy Drink Ratings
REMOTE · ENERGYDRINKRATINGS.COM
Label facts (caffeine, sugar, ingredients) and community ratings for 1,000+ energy drinks.
Available components
Last scanned (14 hours ago)
Scores higher than 84% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Health and Science
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- 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 Usability67
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 753 tokens (~188/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 91% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Nov 26 +1
- 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 21 Nov 2026 · Probed https://energydrinkratings.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=energydrinkratings.com | CN=YE2,O=Let's Encrypt,C=US | 18 Oct 2026 | 16 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6357ac51ec7468bf7f5573cef0e934c784e |
| SANs: energydrinkratings.com, www.energydrinkratings.com | ||||||
| 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 energydrinkratings.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| energydrinkratings.com. | No DS | 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=31536000 |
| content-security-policy | frame-ancestors 'self' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(self), microphone=(), geolocation=(), usb=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://energydrinkratings.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://energydrinkratings.com/api/mcp | HTTPS enforced | 301 | https://energydrinkratings.com/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 →
compare_drinks Compare drinks side by side ~55
Side-by-side facts for 2-4 drinks by slug. Slugs not found in the catalog are reported, not silently dropped.
| Name | Type | Req | Description |
|---|---|---|---|
| slugs | array | yes | 2-4 EDR drink slugs to compare |
No output schema declared.
No examples provided.
find_drinks Find drinks matching criteria ~340
Filters the catalog by caffeine, sugar, sweetener type, flavor family, carbonation and extras, with the same filters as energydrinkratings.com/find. Returns only available drinks, ranked by real community rating where rated, then by name, along with the total number of matches.
| Name | Type | Req | Description |
|---|---|---|---|
| caffeine | array | – | Caffeine bands (OR'd together): le100 (≤100 mg), 100-199 (101–199 mg), 200-299 (200–299 mg), 300plus (300+ mg) |
| extras | array | – | Required ingredient tags (AND'd together): preworkout (Pre-workout), focus (Focus) |
| fizz | string | – | – |
| flavors | array | – | Flavor families (OR'd together): citrus (Citrus), berry (Berry), tropical (Tropical), stone_fruit (Stone Fruit), cherry (Cherry), grape (Grape), melon (Melon), apple_pear (Apple & Pear), fruit_punch… |
| limit | integer | – | Maximum results to return (max 10) |
| sugar | string | – | 'zero' = 0g, 'low' = <=5g |
| sweetener | string | – | 'no-artificial' excludes artificial sweeteners; 'natural' requires a plant-based one (Plant-based sweeteners). Sweetener categories: sugar=Sugar, artificial=Artificial sweeteners, natural=Plant-based… |
No output schema declared.
No examples provided.
get_drink Get drink facts ~105
Full label facts for one drink identified by its EDR slug: caffeine, sugar, calories, serving size, sweetener and flavor info, availability, the community rating with its count and, when there are enough written reviews, a one-line summary of what raters say. Also returns links to the drink page, to rate the drink and to a free caffeine tracker.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The drink's EDR slug, e.g. 'bang-purple-haze' |
No output schema declared.
No examples provided.
search_drinks Search energy drinks ~94
Text search over energy drink names and brands. Returns up to 10 matching drinks with caffeine, sugar and a link to each drink page, or no results when EnergyDrinkRatings has no entry for the name.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum results to return (max 10) |
| query | string | yes | Drink name or brand to search for, e.g. 'Bang Purple Haze' or 'Celsius' |
No output schema declared.
No examples provided.
How do I install the Energy Drink Ratings MCP server?
Energy Drink Ratings is a hosted endpoint at https://energydrinkratings.com/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 · energydrinkratings.com
claude mcp add --transport http com-energydrinkratings-energy-drink-ratings 'https://energydrinkratings.com/api/mcp'
What is the Energy Drink Ratings MCP server?
Energy Drink Ratings is an MCP server listed in the public MCP registry as com.energydrinkratings/energy-drink-ratings. Label facts (caffeine, sugar, ingredients) and community ratings for 1,000+ energy drinks. This page covers its hosted endpoint (https://energydrinkratings.com/api/mcp).
Is the Energy Drink Ratings MCP server safe to use?
Energy Drink Ratings scores 84 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 Energy Drink Ratings MCP server expose?
Energy Drink Ratings exposes 4 tools: search_drinks, get_drink, compare_drinks, find_drinks. Their descriptions and schemas cost roughly 594 tokens of context every time the server is loaded.
Does the Energy Drink Ratings MCP server require authentication?
No. We connected to Energy Drink Ratings without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Energy Drink Ratings MCP server still maintained?
Energy Drink Ratings is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Energy Drink Ratings MCP server?
VerifyMCP ran 13 checks on Energy Drink Ratings, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.