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.

KodShop catalog

REMOTE · KODSHOP.CLOUD · SCANNED OCT 3

Read-only catalog of gift cards, service top-ups and travel eSIMs sold by KodShop.

Available components

0 this week 79 Trust /100
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
Transport & Reachability100
Schema Quality & AI Usability72
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 582 tokens (~194/item across 3 items; 3 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 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
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 4 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
Install

How do I install the KodShop catalog MCP server?

KodShop catalog is a hosted endpoint at https://kodshop.cloud/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 · kodshop.cloud

# add to Claude Code
claude mcp add --transport http cloud-kodshop-catalog 'https://kodshop.cloud/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "cloud-kodshop-catalog": {
      "url": "https://kodshop.cloud/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "cloud-kodshop-catalog": {
      "type": "http",
      "url": "https://kodshop.cloud/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.cloud-kodshop-catalog]
url = "https://kodshop.cloud/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloud-kodshop-catalog": {
      "type": "remote",
      "url": "https://kodshop.cloud/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add cloud-kodshop-catalog --url 'https://kodshop.cloud/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  cloud-kodshop-catalog:
    url: "https://kodshop.cloud/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "cloud-kodshop-catalog": {
      "Transport": "http",
      "Url": "https://kodshop.cloud/mcp"
    }
  }
}
# add to Vellum
assistant mcp add cloud-kodshop-catalog -t streamable-http -u 'https://kodshop.cloud/mcp'
// mcp.json
{
  "mcpServers": {
    "cloud-kodshop-catalog": {
      "type": "http",
      "url": "https://kodshop.cloud/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 28 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
  • 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
  • 10 Sept 26 +1
    • Stability: 0.97 → pass security
  • 8 Sept 26 +1

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

  • 6 Sept 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.

  • 28 Aug 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: pass → fail ▼ functional
    • New tool “buy_product” functional
  • 26 Aug 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
  • 12 Aug 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 3 Oct 2026 · Probed https://kodshop.cloud/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=kodshop.cloud CN=YE1,O=Let's Encrypt,C=US 8 Sept 2026 7 Dec 2026 ECDSA 256 ECDSA-SHA384 67bbbc62df47924fbc076371ac53cddb07d
SANs: kodshop.cloud
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
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 kodshop.cloud. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
cloud. present 7041 13 Verified
kodshop.cloud. 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=31536000; includeSubDomains; preload
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://kodshop.cloud/mcp Verified 200
http (plaintext) http://kodshop.cloud/mcp HTTPS enforced 308 https://kodshop.cloud/mcp
MCP tools · 3 exposed · ~492 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
buy_product ~306

Buy a gift card, service top-up or travel eSIM and receive the delivery. Paid in USDC on Base (x402), no account and no browser. Call it twice: first with the order arguments to get payment requirements and an order_id (nothing is charged), then with that order_id plus the signed x402 payment payload to settle and receive the code.

NameTypeReqDescription
account_numberstring–Only for products where get_product reported requires_account: the recipient account the top-up credits.
amountnumber–Only for products where get_product reported requires_amount; send instead of item_id.
emailstring–Delivery address. The code, eSIM profile or number is emailed here, and it is the only identity the order has. Required on the first call.
item_idinteger–Denomination id from get_product items[].
order_idstring–Second call only: the order_id returned by the first call.
payment_payloadobject–Second call only: the signed x402 PaymentPayload built from the requirements the first call returned.
product_idinteger–Product id from search_catalog.
product_typestring–giftcard = voucher, topup = service recharge. eSIM data plans from search_catalog are bought as giftcard too — the value names the order shape, not the goods.
quantityinteger–Copies to buy. Defaults to 1 — send it only to buy several.

No output schema declared.

No examples provided.

get_product ~46

Get one catalog product by id: available denominations with prices, required order inputs, and any countries where the code cannot be redeemed.

NameTypeReqDescription
idintegeryesProduct id from search_catalog.

No output schema declared.

No examples provided.

search_catalog ~140

Search the store catalog of gift cards, service top-ups and eSIM data plans. Returns matching products with their price, availability and product page URL.

NameTypeReqDescription
countrystring–ISO-3166-1 alpha-2 country code the product is issued for, e.g. US, TR.
limitinteger–Max products to return (default 10, max 50).
querystring–Free text matched against product name and brand, e.g. "steam" or "playstation".
typestring–voucher = gift card, recharge_fixed / recharge = top-up, e_sim = eSIM data plan.

No output schema declared.

No examples provided.

Common questions

What is the KodShop catalog MCP server?

KodShop catalog is an MCP server listed in the public MCP registry as cloud.kodshop/catalog. Read-only catalog of gift cards, service top-ups and travel eSIMs sold by KodShop. This page covers its hosted endpoint (https://kodshop.cloud/mcp).

Is the KodShop catalog MCP server safe to use?

KodShop catalog scores 79 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 KodShop catalog MCP server expose?

KodShop catalog exposes 3 tools: search_catalog, get_product, buy_product. Their descriptions and schemas cost roughly 492 tokens of context every time the server is loaded.

Does the KodShop catalog MCP server require authentication?

No. We connected to KodShop catalog without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the KodShop catalog MCP server still maintained?

KodShop catalog is still listed as active in the MCP registry. We last reached this channel on 3 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.