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.

Karved Concepts custom drinkware quotes

REMOTE · KARVED-DESIGNS.ALFREDAI2026.WORKERS.DEV

Instant prices, mockups and quote requests for custom UV-printed and laser-engraved drinkware.

+4 this week 68 Trust /100

Last scanned (23 hours ago)

Scores higher than 52% 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 Security63
  • 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 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
Schema Quality & AI Usability66
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 871 tokens (~145/item across 6 items; 6 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 Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 61% 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
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 7 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
What we tested

Checks we ran (12)

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

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

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.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 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.

  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 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.

  • 14 Nov 26 0
    • Tool “search_designs” rewrote its description, which is the text the model reads security
  • 13 Nov 26 0
    • “create_design” added an optional parameter “wrap_height” cosmetic

    1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.

  • 12 Nov 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.

  • 11 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
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://karved-designs.alfredai2026.workers.dev/api/v2/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=alfredai2026.workers.dev CN=YE2,O=Let's Encrypt,C=US 16 Nov 2026 14 Feb 2027 ECDSA 256 ECDSA-SHA384 691e23c69f04d227b8b5de597945017fa10
SANs: *.alfredai2026.workers.dev, alfredai2026.workers.dev
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 karved-designs.alfredai2026.workers.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
workers.dev. 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://karved-designs.alfredai2026.workers.dev/api/v2/mcp Verified 200
http (plaintext) http://karved-designs.alfredai2026.workers.dev/api/v2/mcp Inconclusive 405
MCP tools · 6 exposed · ~682 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
create_design ~207

Put the customer's logo (and up to 2 text lines) on a cup. Returns design_id, design_version, an artwork check (preflight) and a mockup_url. Upload the customer's own file as base64 (PNG, JPG, SVG or PDF, up to 25 MB). Partner agent keys may pass an idempotency_key so a retry does not make a second design.

NameTypeReqDescription
artworkobjectyes–
blank_shape_idstringyesFrom list_cups
colourstringyesA colour slug from list_cups for that cup
coveragestringyesPrint coverage offered on that cup (list_cups)
idempotency_keystring––
text_linesarray––
wrap_heightstring–full_wrap on a cup with grip ribs (20oz Ringneck, 16oz Pint): above_ribs (default, the ribs stay the cup colour) or to_base (over the ribs)

No output schema declared.

No examples provided.

get_mockup ~80

A mockup image URL of the design on the cup, optionally in another colour of the same cup. A preview, not a proof.

NameTypeReqDescription
colourstring–Colour slug from list_cups
design_idstringyesThe dsn_ id create_design returned
design_versionintegeryesThe design version create_design returned

No output schema declared.

No examples provided.

get_quote ~89

The posted price for a quantity of this design (cups + art prep fee, no shipping). For 50 or more, full wraps not sold online, or business accounts it returns quote_required: then use request_quote.

NameTypeReqDescription
design_idstringyesThe dsn_ id create_design returned
design_versionintegeryesThe design version create_design returned
qtyintegeryes–

No output schema declared.

No examples provided.

list_cups ~34

The cups you can design on: blank_shape_id, name, colours, print coverages and fonts. Call this first.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

request_quote ~134

Send this design, quantity and the customer's contact to Karved for a quote and proof. Only call it after the customer agreed. Our team replies by email within one business day. Nothing is charged or ordered.

NameTypeReqDescription
companystring––
customer_emailstringyes–
customer_namestringyes–
design_idstringyesThe dsn_ id create_design returned
design_versionintegeryesThe design version create_design returned
needed_bystring–The date or event, in the customer's words
notestring––
qtyintegeryes–

No output schema declared.

No examples provided.

search_designs ~138

Karved's own ready-made cup designs (gifts, hobbies, jobs, holidays, full wraps) matching the words given. Returns title, product page url, price per cup, image and a short description. The art is fixed; many designs take an optional name on the product page, and the name is included in the price. We email a proof before printing and it ships in 5 business days. Send the customer the url to buy.

NameTypeReqDescription
limitinteger–Default 8
querystringyesWhat the customer wants, e.g. "nurse gift", "camo", "funny golf"

No output schema declared.

No examples provided.

Install

How do I install the Karved Concepts custom drinkware quotes MCP server?

Karved Concepts custom drinkware quotes is a hosted endpoint at https://karved-designs.alfredai2026.workers.dev/api/v2/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 · karved-designs.alfredai2026.workers.dev

# add to Claude Code
claude mcp add --transport http karvedconcepts-karved-quotes 'https://karved-designs.alfredai2026.workers.dev/api/v2/mcp'
Common questions

What is the Karved Concepts custom drinkware quotes MCP server?

Karved Concepts custom drinkware quotes is an MCP server listed in the public MCP registry as io.github.KarvedConcepts/karved-quotes. Instant prices, mockups and quote requests for custom UV-printed and laser-engraved drinkware. This page covers its hosted endpoint (https://karved-designs.alfredai2026.workers.dev/api/v2/mcp).

Is the Karved Concepts custom drinkware quotes MCP server safe to use?

Karved Concepts custom drinkware quotes scores 68 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 Karved Concepts custom drinkware quotes MCP server expose?

Karved Concepts custom drinkware quotes exposes 6 tools: search_designs, list_cups, create_design, get_quote, get_mockup, request_quote. Their descriptions and schemas cost roughly 682 tokens of context every time the server is loaded.

Does the Karved Concepts custom drinkware quotes MCP server require authentication?

No. We connected to Karved Concepts custom drinkware quotes without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Karved Concepts custom drinkware quotes MCP server still maintained?

Karved Concepts custom drinkware quotes 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 Karved Concepts custom drinkware quotes MCP server?

VerifyMCP ran 12 checks on Karved Concepts custom drinkware quotes, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Karved Concepts custom drinkware quotes: HTTPS. 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.