SkinGrind
REMOTE · CLOUD.SKINGRIND.COM · SCANNED SEP 20
CS2 skin prices, case odds and ROI, Armory value, and Trade Up contracts.
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1628 tokens (~180/item across 9 items; 9 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the SkinGrind MCP server?
SkinGrind is a hosted endpoint at https://cloud.skingrind.com/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 · cloud.skingrind.com
claude mcp add --transport http com-skingrind-skingrind 'https://cloud.skingrind.com/mcp'
{
"mcpServers": {
"com-skingrind-skingrind": {
"url": "https://cloud.skingrind.com/mcp"
}
}
} {
"servers": {
"com-skingrind-skingrind": {
"type": "http",
"url": "https://cloud.skingrind.com/mcp"
}
}
} [mcp_servers.com-skingrind-skingrind] url = "https://cloud.skingrind.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-skingrind-skingrind": {
"type": "remote",
"url": "https://cloud.skingrind.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-skingrind-skingrind --url 'https://cloud.skingrind.com/mcp' --transport streamable-http
mcp_servers:
com-skingrind-skingrind:
url: "https://cloud.skingrind.com/mcp" {
"McpServers": {
"com-skingrind-skingrind": {
"Transport": "http",
"Url": "https://cloud.skingrind.com/mcp"
}
}
} assistant mcp add com-skingrind-skingrind -t streamable-http -u 'https://cloud.skingrind.com/mcp'
{
"mcpServers": {
"com-skingrind-skingrind": {
"type": "http",
"url": "https://cloud.skingrind.com/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.
- 27 Aug 26 0
- Stability: 0.97 → pass security
- 26 Aug 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
- 25 Aug 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.
- 23 Aug 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.
- 11 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
- 4 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_tradeup_preview” rewrote its description, which is the text the model reads security
- Schema quality: 159 → 180 ▼ functional
- Schema quality: good → excellent functional
- 31 Jul 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
- 30 Jul 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
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 20 Sept 2026 · Probed https://cloud.skingrind.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=cloud.skingrind.com | CN=YE2,O=Let's Encrypt,C=US | 5 Aug 2026 | 3 Nov 2026 | ECDSA 384 | ECDSA-SHA384 | 6a8d52115075a1ced13cb95a74a9ef42ae2 |
| SANs: cloud.skingrind.com, www.cloud.skingrind.com | ||||||
| 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 cloud.skingrind.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| skingrind.com. | 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 |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://cloud.skingrind.com/mcp | Verified | 200 | |
| http (plaintext) | http://cloud.skingrind.com/mcp | HTTPS enforced | 301 | https://cloud.skingrind.com/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 →
browse_bargains Browse cheap CS2 skins ~106
Find cheap Counter-Strike 2 skins grouped into price-threshold pages, for example AK-47 skins under 10 dollars or the cheapest knives. Without a slug it lists every available page; with a slug it returns the skins on that page with their current cheapest listing price.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | – | Bargain page slug, for example "ak-47-skins-under-10-dollars" or "cheapest-knives". Omit to list every available page. |
No output schema declared.
No examples provided.
browse_cases Browse CS2 cases ~167
List Counter-Strike 2 cases, capsules and souvenir packages, or get one container with its contents plus its drop odds and expected opening value. Odds use the standard CS2 tier weights and are renormalised over the tiers actually present.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number. |
| per_page | integer | – | Results per page, 1 to 25. |
| search | string | – | Free-text container name search. |
| slug | string | – | Container slug. When set, returns that container with its contents and opening odds instead of the list. |
| sort | string | – | List ordering: newest, oldest or name. For a single container the contents order: rarity, name, price_asc or price_desc. |
| type | string | – | Filter the list by container type. |
No output schema declared.
No examples provided.
browse_collections Browse CS2 collections ~197
List Counter-Strike 2 collections, or get one collection with its contents. Optionally includes the collection Trade Up map: which rarity tiers exist in the collection and what each tier can produce. That map is catalog contract math, not scanner output.
| Name | Type | Req | Description |
|---|---|---|---|
| include_tradeup_map | boolean | – | Only with slug. Adds the collection Trade Up map showing each rarity tier and its possible outputs. |
| page | integer | – | Page number. |
| per_page | integer | – | Results per page, 1 to 25. |
| search | string | – | Free-text collection name search. |
| slug | string | – | Collection slug. When set, returns that collection with its contents instead of the list. |
| sort | string | – | List ordering: newest, oldest or name. For a single collection the contents order: rarity, name, price_asc or price_desc. |
| type | string | – | Filter the list by what the collection contains. |
No output schema declared.
No examples provided.
get_armory_roi Get CS2 Armory rotation value ~88
List the current Counter-Strike 2 Armory rotation tiles with their credit cost and expected value, or get one tile with every item it can produce and the rarity weighting. Use this to compare what Armory credits are worth across the current rotation.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | – | Armory tile slug. When set, returns that tile with its full item list instead of the rotation overview. |
No output schema declared.
No examples provided.
get_case_roi_ranking Get CS2 case ROI ranking ~68
Rank Counter-Strike 2 cases by expected return on opening. Each entry gives the case price, expected value, return in basis points and the chance of an opening being profitable, all computed from current listing prices plus the key price. Cases whose contents are not sufficiently priced are excluded.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_skin_detail Get CS2 skin detail ~121
Get one Counter-Strike 2 skin with its float range, per-wear prices, collections and cases. Optionally includes the catalog Trade Up context: which rarity tier the skin sits in and what it can be traded up into.
| Name | Type | Req | Description |
|---|---|---|---|
| include_tradeup_context | boolean | – | Include the catalog Trade Up context for this skin. This is contract math derived from the collection, not scanner output. |
| skin_slug | string | yes | Skin slug, for example "redline". |
| weapon_slug | string | yes | Weapon slug, for example "ak-47". |
No output schema declared.
No examples provided.
get_tradeup_preview Get CS2 Trade Up preview ~145
Get the free preview of the SkinGrind Trade Up scanner: the featured Trade Ups with their full recipes, the number of contracts currently active, and locked teasers for recent finds showing their economics and when they unlock. Every input has to be bought at or below its target float, and the costs are hourly price estimates, so the response carries execution_notes explaining what to verify before buying. Full recipes for the whole feed need a SkinGrind account and the authenticated server.
| Name | Type | Req | Description |
|---|---|---|---|
| type | string | – | Which Trade Up feed to preview: "profitable" for contract Trade Ups, "knife" for knife and glove Trade Ups, or "all". Defaults to all. |
No output schema declared.
No examples provided.
search_cosmetics Search CS2 cosmetic items ~141
Search Counter-Strike 2 cosmetic items that are not weapon skins: stickers, charms, agents, patches, graffiti and music kits. Returns names and cheapest listing prices, or one item with its full detail including per-marketplace prices.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | Which kind of cosmetic item to search. |
| page | integer | – | Page number. |
| per_page | integer | – | Results per page, 1 to 25. |
| search | string | – | Free-text item name search. |
| slug | string | – | Item slug. When set, returns that single item with full detail. |
| sort | string | – | Result ordering. Defaults to name. |
No output schema declared.
No examples provided.
search_skins Search CS2 skins ~255
Search and filter Counter-Strike 2 weapon skins by name, weapon, rarity, collection or case. Returns skin names, rarities, wear ranges and the cheapest current listing price in cents. Use get_skin_detail for a single skin with per-wear prices.
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | – | Collection slug. |
| crate | string | – | Case or capsule slug. |
| page | integer | – | Page number. |
| per_page | integer | – | Results per page, 1 to 25. Defaults to 10. |
| rarity | string | – | Rarity name, for example "Covert", "Classified", "Restricted", "Mil-Spec Grade". |
| search | string | – | Free-text skin name search, for example "Redline". Used alone it also returns matching weapons; combined with any other argument it filters the paginated skin list instead. |
| sort | string | – | Result ordering. Defaults to name. "popularity" ranks by listing quantity. |
| souvenir | boolean | – | Only skins available as Souvenir. |
| stattrak | boolean | – | Only skins available as StatTrak. |
| weapon | string | – | Weapon slug, for example "ak-47" or "desert-eagle". |
No output schema declared.
No examples provided.
What is the SkinGrind MCP server?
SkinGrind is an MCP server listed in the public MCP registry as com.skingrind/skingrind. CS2 skin prices, case odds and ROI, Armory value, and Trade Up contracts. This page covers its hosted endpoint (https://cloud.skingrind.com/mcp).
Is the SkinGrind MCP server safe to use?
SkinGrind scores 77 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 SkinGrind MCP server expose?
SkinGrind exposes 9 tools: search_skins, get_skin_detail, browse_collections, browse_cases, get_case_roi_ranking, and 4 more. Their descriptions and schemas cost roughly 1,288 tokens of context every time the server is loaded.
Does the SkinGrind MCP server require authentication?
No. We connected to SkinGrind without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SkinGrind MCP server still maintained?
SkinGrind is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.