Skip to content
External endpointresponds

SkinGrind

CS2 skin prices, case odds and ROI, Armory value, and Trade Up contracts.

Endpoint URL
https://cloud.skingrind.com/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:00 AM UTC
Check
MCP initialize · 8s limit
Latency
593 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
com.skingrind/skingrind

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
SkinGrind
Version
1.0.0
Capability keys
tools, resources, prompts
Tool names
search_skins, get_skin_detail, browse_collections, browse_cases, get_case_roi_ranking, get_armory_roi, browse_bargains, search_cosmetics, get_tradeup_preview
Instructions excerpt

SkinGrind is a Counter-Strike 2 skin database and market analysis service. This server exposes read-only reference data: skins and their prices, collections, cases with their drop odds and expected return, Armory rotation tiles, cheap-skin bargain listings, and cosmetic items (stickers, charms, agents, patches, graffiti, music kits). Prices come from CSFloat listings and are refreshed hourly. All money values are integer cents. Rates are basis points where a field name ends in _bps. Case odds follow the standard CS2 tier weights. Trade Up data on this server is limited to the free preview: the featured Trade Ups and locked teasers for recent finds. Full recipes require a SkinGrind account and are served by the authenticated server at /mcp/pro. A Trade Up recipe is not just a list of skins. Every input carries a target_float and has to be bought at a float at or below it, since a higher float moves the contract average and can drop the outcome into a worse wear. Every price is the c

Reported Aug 17, 2026, 05:00 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 420ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 893ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 613ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 593ms