Convert mouse sensitivity across 16 FPS engines (Valorant, CS2, BF6) and inspect pro settings.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Convert mouse sensitivity and DPI across 16 competitive FPS engines (valorant, cs2, bf6, rivals, deadlock, apex, ow2, cod, r6, finals, fortnite, pubg, rust, tarkov, quake, halo) with exact cm/360 physical distance.
Target game slug (e.g. bf6, cs2, valorant, rivals, deadlock)
Source game slug (e.g. valorant, cs2, bf6, apex, ow2)
In-game sensitivity in source game
Mouse DPI in target game (default same as from_dpi)
Mouse DPI in source game (default 800)
This tool isn't marked read-only, so it may change something on the server or in an account you connected.
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
Run in a terminal
claude mcp add --transport http fps-sensitivity-lab https://esportcalc.com/mcp
Convert mouse sensitivity and DPI across 16 competitive FPS engines (valorant, cs2, bf6, rivals, deadlock, apex, ow2, cod, r6, finals, fortnite, pubg, rust, tarkov, quake, halo) with exact cm/360 physical distance.
| Argument | Type | Description |
|---|---|---|
| to_dpi | number | Mouse DPI in target game (default same as from_dpi) |
| to_game* | string | Target game slug (e.g. bf6, cs2, valorant, rivals, deadlock) |
| from_dpi | number | Mouse DPI in source game (default 800) |
| from_game* | string | Source game slug (e.g. valorant, cs2, bf6, apex, ow2) |
| sensitivity* | number | In-game sensitivity in source game |
{
"type": "object",
"required": [
"from_game",
"to_game",
"sensitivity"
],
"properties": {
"to_dpi": {
"type": "number",
"description": "Mouse DPI in target game (default same as from_dpi)"
},
"to_game": {
"type": "string",
"description": "Target game slug (e.g. bf6, cs2, valorant, rivals, deadlock)"
},
"from_dpi": {
"type": "number",
"description": "Mouse DPI in source game (default 800)"
},
"from_game": {
"type": "string",
"description": "Source game slug (e.g. valorant, cs2, bf6, apex, ow2)"
},
"sensitivity": {
"type": "number",
"description": "In-game sensitivity in source game"
}
}
}Retrieve publicly reported mouse DPI, sensitivity, eDPI, cm/360 turn distance, crosshair code, and hardware snapshot for competitive FPS pros.
| Argument | Type | Description |
|---|---|---|
| player_slug* | string | Pro player slug (e.g. tenz, s1mple, donk, zywoo, aspas, proper) |
{
"type": "object",
"required": [
"player_slug"
],
"properties": {
"player_slug": {
"type": "string",
"description": "Pro player slug (e.g. tenz, s1mple, donk, zywoo, aspas, proper)"
}
}
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Nov 11, 2026.
No readOnlyHint / destructiveHint annotations, so clients can't tell a read from a write without asking.
Fix: Add annotations to each tool, e.g. { readOnlyHint: true } for tools that only read.