io.github.pratikgajjar/sf-beverage-skus
REMOTE · SF-BEVERAGE-SKUS.LUFF.WORKERS.DEV
SF coffee, matcha, and chai catalog API: 439 SKUs across 13 merchants, prices in cents.
Available components
Last scanned (3 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 18 Oct 2026.
Category E-commerce
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 Security46
- 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 3 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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 220 tokens (~73/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage73
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 20% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 33. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +2
No change was recorded against any check on this day. Stability & Change Management went from 17 to 27. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 17. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 2 Oct 26 55
First indexed and scored.
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 18 Oct 2026 · Probed https://sf-beverage-skus.luff.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=luff.workers.dev | CN=WE1,O=Google Trust Services,C=US | 1 Oct 2026 | 30 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 8f991ed4a96446f713e911acebbd984e |
| SANs: luff.workers.dev, *.luff.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of sf-beverage-skus.luff.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://sf-beverage-skus.luff.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://sf-beverage-skus.luff.workers.dev/mcp | Inconclusive | 405 |
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_sku ~55
Full detail for one SKU: item, merchant, location, and every option group with choices and price deltas (cents).
| Name | Type | Req | Description |
|---|---|---|---|
| sku_id | string | yes | e.g. starbucks--matcha-latte--short |
No output schema declared.
No examples provided.
price_order ~61
Compute an order total: total_cents = sku.price_cents + SUM(option.price_delta_cents). Validates option_ids against the SKU; rejects unknown or inapplicable options.
| Name | Type | Req | Description |
|---|---|---|---|
| option_ids | array | – | – |
| sku_id | string | yes | – |
No output schema declared.
No examples provided.
search_skus ~104
Search SF beverage SKUs by item name, with optional category filter and geo search. Returns sku_id, merchant, distance, size, and price in integer cents.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| lat | number | – | – |
| limit | integer | – | – |
| lon | number | – | – |
| max_miles | number | – | – |
| q | string | – | item name substring, e.g. 'matcha latte' |
| sort | string | – | – |
No output schema declared.
No examples provided.
How do I install the io.github.pratikgajjar/sf-beverage-skus MCP server?
io.github.pratikgajjar/sf-beverage-skus is a hosted endpoint at https://sf-beverage-skus.luff.workers.dev/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 · sf-beverage-skus.luff.workers.dev
claude mcp add --transport http pratikgajjar-sf-beverage-skus 'https://sf-beverage-skus.luff.workers.dev/mcp'
What is the io.github.pratikgajjar/sf-beverage-skus MCP server?
io.github.pratikgajjar/sf-beverage-skus is an MCP server listed in the public MCP registry as io.github.pratikgajjar/sf-beverage-skus. SF coffee, matcha, and chai catalog API: 439 SKUs across 13 merchants, prices in cents. This page covers its hosted endpoint (https://sf-beverage-skus.luff.workers.dev/mcp).
Is the io.github.pratikgajjar/sf-beverage-skus MCP server safe to use?
io.github.pratikgajjar/sf-beverage-skus scores 62 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 io.github.pratikgajjar/sf-beverage-skus MCP server expose?
io.github.pratikgajjar/sf-beverage-skus exposes 3 tools: search_skus, get_sku, price_order. Their descriptions and schemas cost roughly 220 tokens of context every time the server is loaded.
Does the io.github.pratikgajjar/sf-beverage-skus MCP server require authentication?
No. We connected to io.github.pratikgajjar/sf-beverage-skus without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.pratikgajjar/sf-beverage-skus MCP server still maintained?
io.github.pratikgajjar/sf-beverage-skus is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.