LivaGlow Shop
REMOTE · LIVAGLOW.DE · SCANNED SEP 25
Personalised ceramic mugs from Germany: prices, delivery, FAQ search, mug-design tool with preview.
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 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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 Usability55
- 17% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1032 tokens (~60/item across 17 items; 11 tools + 6 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
- Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
- Structured output schemas are declared (9% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
- Supports UI / widget rendering.Pass
How do I install the LivaGlow Shop MCP server?
LivaGlow Shop is a hosted endpoint at https://livaglow.de/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 · livaglow.de
claude mcp add --transport http de-livaglow-livaglow-shop 'https://livaglow.de/api/mcp'
{
"mcpServers": {
"de-livaglow-livaglow-shop": {
"url": "https://livaglow.de/api/mcp"
}
}
} {
"servers": {
"de-livaglow-livaglow-shop": {
"type": "http",
"url": "https://livaglow.de/api/mcp"
}
}
} [mcp_servers.de-livaglow-livaglow-shop] url = "https://livaglow.de/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"de-livaglow-livaglow-shop": {
"type": "remote",
"url": "https://livaglow.de/api/mcp",
"enabled": true
}
}
} openclaw mcp add de-livaglow-livaglow-shop --url 'https://livaglow.de/api/mcp' --transport streamable-http
mcp_servers:
de-livaglow-livaglow-shop:
url: "https://livaglow.de/api/mcp" {
"McpServers": {
"de-livaglow-livaglow-shop": {
"Transport": "http",
"Url": "https://livaglow.de/api/mcp"
}
}
} assistant mcp add de-livaglow-livaglow-shop -t streamable-http -u 'https://livaglow.de/api/mcp'
{
"mcpServers": {
"de-livaglow-livaglow-shop": {
"type": "http",
"url": "https://livaglow.de/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.
- 25 Sept 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
- 24 Sept 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.
- 22 Sept 26 +1
- Tool “get_delivery_estimate” rewrote its description, which is the text the model reads security
- Schema quality: excellent → good functional
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 0
- Tool “get_page_markdown” rewrote its description, which is the text the model reads security
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 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.
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 25 Sept 2026 · Probed https://livaglow.de/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=livaglow.de | CN=WE1,O=Google Trust Services,C=US | 23 Aug 2026 | 21 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 819c5a802a5d91390e69f9720b50ca26 |
| SANs: livaglow.de, *.livaglow.de | ||||||
| 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 livaglow.de. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| de. | present | 26755 | 8 | Verified |
| livaglow.de. | 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 |
| content-security-policy | base-uri 'self'; object-src 'none'; form-action 'self'; frame-ancestors 'none'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), usb=(), magnetometer=(), accelerometer=(), gyroscope=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://livaglow.de/api/mcp | Verified | 200 | |
| http (plaintext) | http://livaglow.de/api/mcp | HTTPS enforced | 302 | https://livaglow.de/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 →
calculate_price Price quote ~66
Exact price for a number of mugs in EUR: first mug full price, every additional mug discounted (also across different designs), shipping cost or free shipping, total. Same maths as the shop checkout, before any promo code.
| Name | Type | Req | Description |
|---|---|---|---|
| quantity | integer | yes | Number of mugs in one order |
No output schema declared.
No examples provided.
create_design_link Create a mug design draft ~254
Turns a design description into a link that opens the LivaGlow designer with the finished draft (texts, cliparts, background, photo placeholder, optional template). Nothing is stored or ordered: the customer opens the link, checks the 3D preview, uploads their photo if a placeholder is present, and orders. Texts are placed automatically (centred column) unless x/y are given; with a template, texts replace the template's text slots in order. Photos cannot be passed; use photo:{shape} to reserve a placeholder. Call get_design_options first for valid fonts, cliparts and templates.
| Name | Type | Req | Description |
|---|---|---|---|
| background | – | – | Background preset id (e.g. "creme", "sonnenuntergang") or {kind:"solid",color:"#rrggbb"} or {kind:"gradient",from:"#rrggbb",to:"#rrggbb",angle:135} |
| items | array | – | Texts and cliparts in top-to-bottom order |
| layout | string | – | Column for automatically placed items (default: opposite the photo, else center) |
| photo | – | – | Reserve a photo placeholder the customer fills in the designer |
| template | string | – | Template id from get_design_options (optional) |
| Name | Type | Req | Description |
|---|---|---|---|
| elementCount | integer | – | – |
| hasPhotoPlaceholder | boolean | yes | – |
| locale | string | yes | – |
| next | string | – | – |
| previewNote | string | – | – |
| previewUrl | string | yes | PNG of the flat print area |
| price | object | yes | – |
| summary | string | yes | – |
| url | string | yes | Designer link with the draft |
| warnings | array | yes | – |
No examples provided.
get_care_and_safety Care and safety ~39
Care instructions and safety warnings for the mug (dishwasher, microwave, thermal shock, damage) as published on the product safety page.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_delivery_estimate Delivery estimate ~47
Expected delivery window for an order placed now (Germany, UPS or DHL): production start rule (cutoff 14:00 Berlin time on business days), earliest and latest delivery date.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_design_options Design options ~52
Everything an agent needs before create_design_link: available fonts with style hints, text size range, background presets, photo shapes, clipart ids by category, templates with their text slots, print-area geometry and limits.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_page_markdown Page as Markdown ~113
Full content of a LivaGlow page as Markdown. Supported paths: /, /custom, /faq, /ratgeber, /ratgeber/:slug, /tasse/:slug, /mug/:slug, /vorlagen, /vorlagen/:slug, /produktsicherheit, /partnerprogramm (e.g. /faq, /ratgeber/tasse-spuelmaschinenfest, /tasse/geburtstag, /mug/birthday).
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Path starting with / |
No output schema declared.
No examples provided.
get_shop_overview Shop overview ~49
Facts about LivaGlow and its single product, the personalised ceramic mug: specs, fixed prices, volume discount, shipping (Germany only), delivery, returns policy, photo requirements and key URLs.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_store_rating Store rating ~29
Current Trustpilot rating of the shop (TrustScore and number of reviews) with the profile URL.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_occasions Occasions and templates ~49
Occasion landing pages with ready-made templates (photo mug, birthday, couples, pet, Mother's Day, Christmas) with German and English URLs and the designer deep link that preselects the templates.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_faq Search FAQ ~59
Keyword search over the shop FAQ and the occasion-page FAQs (German): designer usage, image quality, payment, shipping, returns, care. Returns the best matching questions with full answers.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search words, German or English |
No output schema declared.
No examples provided.
search_guides Search guide articles ~75
Find LivaGlow guide articles (German) about printed mugs: dishwasher safety, porcelain vs ceramic, photo resolution, printing costs, print durability, gift ideas. Returns title, direct answer and URL.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search words, German or English (e.g. "spülmaschinenfest", "photo resolution") |
No output schema declared.
No examples provided.
What is the LivaGlow Shop MCP server?
LivaGlow Shop is an MCP server listed in the public MCP registry as de.livaglow/livaglow-shop. Personalised ceramic mugs from Germany: prices, delivery, FAQ search, mug-design tool with preview. This page covers its hosted endpoint (https://livaglow.de/api/mcp).
Is the LivaGlow Shop MCP server safe to use?
LivaGlow Shop scores 76 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 LivaGlow Shop MCP server expose?
LivaGlow Shop exposes 11 tools: get_shop_overview, calculate_price, get_delivery_estimate, list_occasions, search_faq, and 6 more. Their descriptions and schemas cost roughly 832 tokens of context every time the server is loaded.
Does the LivaGlow Shop MCP server require authentication?
No. We connected to LivaGlow Shop without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the LivaGlow Shop MCP server still maintained?
LivaGlow Shop is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.