Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

LivaGlow Shop

REMOTE · LIVAGLOW.DE

Personalised ceramic mugs from Germany: prices, delivery, FAQ search, mug-design tool with preview.

Available components

0 this week 85 Trust /100

Last scanned (19 hours ago)

Scores higher than 86% of remote servers

Reachable. Last reached 21 Nov 2026.

Category E-commerce

Trust breakdown (7 categories)

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 Security83
  • 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
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 (excellent).Pass
  • Tool/resource definitions use about 1351 tokens (~79/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 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
  • 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
What we tested

Checks we ran (14)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol
  • Capabilities

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 →

Changelog

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.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 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
  • 3 Nov 26 0
    • Tool “get_page_markdown” rewrote its description, which is the text the model reads security
  • 24 Oct 26 0
    • Tool “get_delivery_estimate” rewrote its description, which is the text the model reads security
  • 19 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
Diagnostics

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://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 21 Oct 2026 19 Jan 2027 ECDSA 256 ECDSA-SHA256 3ec3546c24d37b9e137172df555406cb
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 secure

Validation of livaglow.de. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
de. DS published 26755 8 Verified
livaglow.de. DS published 2371 13 Verified
livaglow.de. Verified address RRset verified with the apex keys
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=(self), 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
MCP tools · 11 exposed · ~1,043 tokens

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 →

Tool Tokens
calculate_price ~79

Use this when the user asks what one or more mugs cost, with or without shipping. Exact price 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.

NameTypeReqDescription
quantityintegeryesNumber of mugs in one order

No output schema declared.

No examples provided.

create_design_link ~354

Use this when the user wants a mug designed or personalised. Turns a design description into a link that opens the LivaGlow designer with the finished draft (texts, cliparts, background, photo placeholder, optional template). If the user already gave a text or an occasion, build the draft with sensible defaults; they can change it afterwards. Nothing is stored or ordered: the customer opens the link, checks the 3D preview, uploads their photo if a placeholder is present, and orders. Everything is placed automatically: with a photo, texts and cliparts form a column next to it, otherwise a centred column. A template only fits its own text slots, which replace in order: for your own wording, extra texts or cliparts leave template out and use items with photo. Photos cannot be passed; use photo:{shape} to reserve a placeholder. Call get_design_options first for valid fonts, cliparts and templates. Do not use it for hateful, harassing or illegal print content.

NameTypeReqDescription
background––Background: preset id (e.g. "schwarz", "nacht", "creme", "sonnenuntergang"), a colour "#rrggbb", {kind:"solid",color:"#rrggbb"} or {kind:"gradient",from:"#rrggbb",to:"#rrggbb",angle:135}. Text colour…
itemsarray–Texts and cliparts in top-to-bottom order
layoutstring–Column for automatically placed items (default: opposite the photo, else center)
photo––Reserve a photo placeholder the customer fills in the designer
templatestring–Template id from get_design_options (optional)
NameTypeReqDescription
elementCountinteger––
hasPhotoPlaceholderbooleanyes–
localestringyes–
nextstring––
previewNotestring––
previewUrlstringyesPNG of the flat print area
priceobjectyes–
summarystringyes–
urlstringyesDesigner link with the draft
warningsarrayyes–

No examples provided.

get_care_and_safety ~44

Whether the mug and its print are dishwasher and microwave safe, plus care instructions and safety warnings (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 ~108

Use this when the user asks when a mug would arrive. Expected delivery window for an order placed now (Germany, DPD, UPS or DHL): production start rule (cutoff 14:00 Berlin time on business days), earliest and latest delivery date, plus the current workload (normal / elevated / high) with the estimated processing time until dispatch and the recent real average. Checkout also accepts a preferred date (arrive by / ship from), so a gift can be held back.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_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 ~126

Full content of a LivaGlow page as Markdown. Supported paths: /, /custom, /faq, /ratgeber, /ratgeber/:slug, /tasse/:slug, /mug/:slug, /vorlagen, /vorlagen/:slug, /produktsicherheit, /partnerprogramm, /partnerprogramm/:slug, /presse, /status (e.g. /faq, /ratgeber/tasse-spuelmaschinenfest, /tasse/geburtstag, /mug/birthday).

NameTypeReqDescription
pathstringyesPath starting with /

No output schema declared.

No examples provided.

get_shop_overview ~65

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. For a quote use calculate_price, for delivery dates use get_delivery_estimate.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_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 ~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 ~62

Keyword search over the shop FAQ and the occasion-page FAQs (German): designer usage, image quality, payment, shipping and shipping countries, returns, care. Returns the best matching questions with full answers.

NameTypeReqDescription
querystringyesSearch words, German or English

No output schema declared.

No examples provided.

search_guides ~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.

NameTypeReqDescription
querystringyesSearch words, German or English (e.g. "spülmaschinenfest", "photo resolution")

No output schema declared.

No examples provided.

Install

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

# add to Claude Code
claude mcp add --transport http de-livaglow-livaglow-shop 'https://livaglow.de/api/mcp'
Common questions

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 85 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 1,043 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 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 LivaGlow Shop MCP server?

VerifyMCP ran 14 checks on LivaGlow Shop, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 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.