skimguard_my_earnings — skimguard MCP Tool
skimguard_my_earnings
(skimguard my earnings) is one of 17 tools on the
skimguard
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call skimguard_my_earnings from your client
- Claude Code skimguard skimguard_my_earnings run in your project directory
- Claude Desktop skimguard skimguard_my_earnings ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor skimguard skimguard_my_earnings ~/.cursor/mcp.json
- VS Code skimguard skimguard_my_earnings .vscode/mcp.json
- Zed skimguard skimguard_my_earnings ~/.config/zed/settings.json
- Windsurf skimguard skimguard_my_earnings ~/.codeium/windsurf/mcp_config.json
- Cline skimguard skimguard_my_earnings ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI skimguard skimguard_my_earnings ~/.gemini/settings.json
- Grok skimguard skimguard_my_earnings .mcp.json (in your project root)
- ChatGPT skimguard skimguard_my_earnings Settings → Connectors → Advanced → Developer mode
- Claude.ai skimguard skimguard_my_earnings Settings → Connectors → Add custom connector
- LangChain skimguard skimguard_my_earnings pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http skimguard https://mcp.skimguard.io/mcp
Other tools on this server
- skimguard_get_location_status
- skimguard_find_nearby_activity
- skimguard_lookup_bluetooth_manufacturer
- skimguard_search_locations
- skimguard_route_risk
- skimguard_coverage_stats
- skimguard_about
- skimguard_my_locations
- skimguard_my_stale_locations
- skimguard_location_devices
- skimguard_my_scanner_health
- skimguard_my_merchants
- skimguard_regional_risk
- skimguard_device_prevalence
- skimguard_inspection_stats
- skimguard_training_stats
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.