LootCodes
REMOTE · WWW.LOOTCODES.COM
Search LootCodes game keys, gift cards and top-ups, compare prices and prepare a cart link.
Available components
Last scanned (17 hours ago)
Scores higher than 88% of remote servers
Reachable. Last reached 21 Nov 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 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1088 tokens (~181/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage92
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 77% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.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
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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 →
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 +1
- Stability: 0.97 → pass security
- 10 Nov 26 −1
- Stability: pass → 0.97 functional
- 9 Nov 26 +1
- Stability: 0.97 → pass security
- 6 Nov 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 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 21 Nov 2026 · Probed https://www.lootcodes.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=lootcodes.com | CN=WE1,O=Google Trust Services,C=US | 27 Oct 2026 | 25 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | b6c08b7263c3c9a2137008a7e0f95b26 |
| SANs: lootcodes.com, *.lootcodes.com | ||||||
| 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 www.lootcodes.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| lootcodes.com. | DS published | 2371 | 13 | Verified |
| www.lootcodes.com. | 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 |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=(), payment=(self), usb=(), magnetometer=(), gyroscope=(), accelerometer=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.lootcodes.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://www.lootcodes.com/api/mcp | HTTPS enforced | 301 | https://www.lootcodes.com/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 →
check_activation_country Check activation country ~196
Check live advisory activation evidence for one exact variant and an explicit country. An incompatible variant remains purchasable under the storefront policy; unknown is never compatible.
| Name | Type | Req | Description |
|---|---|---|---|
| countryCode | string | yes | Explicit ISO 3166-1 alpha-2 activation country; do not infer it from language. |
| currency | string | yes | ISO 4217 code such as USD, EUR, BRL or AUD. Prices come back in it, converted from the stored USD price at the verified storefront display rate (usdAmountMinor keeps the USD base); if no rate exists… |
| language | string | – | Language for product names and links (default en). |
| productSlug | string | yes | Product or variant slug from a catalogue result. |
| variantId | string | yes | Exact variant UUID; platform, edition and region are never silently substituted. |
No output schema declared.
No examples provided.
create_cart_link Create a cart link for the buyer ~145
Create a lootcodes.com link that opens the buyer's cart review with exact variants and quantities (1 to 5 each, up to 10 items) chosen from get_product_options. The buyer sees each item, confirms, then pays on the site; this tool adds nothing to any cart, reserves no stock and creates no order. Items that are unavailable or need the product page (top-ups, custom amounts, several platforms) are returned in rejected.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | ISO 4217 code for the unit prices shown in the answer (default USD). |
| items | array | yes | – |
| language | string | – | Language for names and links (default en). |
No output schema declared.
No examples provided.
get_activation_guide Get the official activation page ~200
Return the existing verified official activation destination for an exact variant, without reading or embedding any purchased code. Detailed product instructions remain on the product page; ambiguous products return unknown.
| Name | Type | Req | Description |
|---|---|---|---|
| countryCode | string | yes | Explicit ISO 3166-1 alpha-2 activation country; do not infer it from language. |
| currency | string | yes | ISO 4217 code such as USD, EUR, BRL or AUD. Prices come back in it, converted from the stored USD price at the verified storefront display rate (usdAmountMinor keeps the USD base); if no rate exists… |
| language | string | – | Language for product names and links (default en). |
| productSlug | string | yes | Product or variant slug from a catalogue result. |
| variantId | string | yes | Exact variant UUID; platform, edition and region are never silently substituted. |
No output schema declared.
No examples provided.
get_product_options Get product options and prices ~191
Read fresh product variants, exact edition/platform/region, stock and explicit currency prices. Activation is advisory and unknown stays unknown; checkout revalidates prices and stock.
| Name | Type | Req | Description |
|---|---|---|---|
| countryCode | string | yes | Explicit ISO 3166-1 alpha-2 activation country; do not infer it from language. |
| currency | string | yes | ISO 4217 code such as USD, EUR, BRL or AUD. Prices come back in it, converted from the stored USD price at the verified storefront display rate (usdAmountMinor keeps the USD base); if no rate exists… |
| language | string | – | Language for product names and links (default en). |
| limit | integer | – | – |
| page | integer | – | – |
| productSlug | string | yes | Product or variant slug from a catalogue result. |
No output schema declared.
No examples provided.
get_store_information Get store information and policies ~54
Read how LootCodes sells and delivers: what it sells, delivery, support contact and links to the terms, refund policy, privacy policy and FAQ.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Language for names and links (default en). |
No output schema declared.
No examples provided.
search_catalog Search the LootCodes catalogue ~190
Find bounded public catalogue variants. Indexed stock and prices are snapshots (converted from USD like the storefront shows them); call get_product_options for fresh prices and stock before create_cart_link. This never confirms activation eligibility.
| Name | Type | Req | Description |
|---|---|---|---|
| countryCode | string | yes | Explicit ISO 3166-1 alpha-2 activation country; do not infer it from language. |
| currency | string | yes | ISO 4217 code such as USD, EUR, BRL or AUD. Prices come back in it, converted from the stored USD price at the verified storefront display rate (usdAmountMinor keeps the USD base); if no rate exists… |
| language | string | – | Language for product names and links (default en). |
| limit | integer | – | – |
| page | integer | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
How do I install the LootCodes MCP server?
LootCodes is a hosted endpoint at https://www.lootcodes.com/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 · www.lootcodes.com
claude mcp add --transport http com-lootcodes-catalog 'https://www.lootcodes.com/api/mcp'
What is the LootCodes MCP server?
LootCodes is an MCP server listed in the public MCP registry as com.lootcodes/catalog. Search LootCodes game keys, gift cards and top-ups, compare prices and prepare a cart link. This page covers its hosted endpoint (https://www.lootcodes.com/api/mcp).
Is the LootCodes MCP server safe to use?
LootCodes scores 86 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 LootCodes MCP server expose?
LootCodes exposes 6 tools: search_catalog, get_product_options, check_activation_country, get_activation_guide, create_cart_link, get_store_information. Their descriptions and schemas cost roughly 976 tokens of context every time the server is loaded.
Does the LootCodes MCP server require authentication?
No. We connected to LootCodes without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the LootCodes MCP server still maintained?
LootCodes 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 LootCodes MCP server?
VerifyMCP ran 13 checks on LootCodes, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 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.