target_check — McpStamp Time Tracker MCP Tool
target_check
(target check) is one of 20 tools on the
McpStamp Time Tracker
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call target_check from your client
- Claude Code McpStamp Time Tracker target_check run in your project directory
- Claude Desktop McpStamp Time Tracker target_check ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor McpStamp Time Tracker target_check ~/.cursor/mcp.json
- VS Code McpStamp Time Tracker target_check .vscode/mcp.json
- Zed McpStamp Time Tracker target_check ~/.config/zed/settings.json
- Windsurf McpStamp Time Tracker target_check ~/.codeium/windsurf/mcp_config.json
- Cline McpStamp Time Tracker target_check ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI McpStamp Time Tracker target_check ~/.gemini/settings.json
- Grok McpStamp Time Tracker target_check .mcp.json (in your project root)
- ChatGPT McpStamp Time Tracker target_check Settings → Connectors → Advanced → Developer mode
- Claude.ai McpStamp Time Tracker target_check Settings → Connectors → Add custom connector
- LangChain McpStamp Time Tracker target_check pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http time-tracker-timesheet-billable-hours https://mcp.zovo.one/mcp/time-trackerOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 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.