base_image_check — Sighttrue MCP Tool
base_image_check
(base image check) is one of 31 tools on the
Sighttrue
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call base_image_check from your client
- Claude Code Sighttrue base_image_check run in your project directory
- Claude Desktop Sighttrue base_image_check ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Sighttrue base_image_check ~/.cursor/mcp.json
- VS Code Sighttrue base_image_check .vscode/mcp.json
- Zed Sighttrue base_image_check ~/.config/zed/settings.json
- Windsurf Sighttrue base_image_check ~/.codeium/windsurf/mcp_config.json
- Cline Sighttrue base_image_check ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Sighttrue base_image_check ~/.gemini/settings.json
- Grok Sighttrue base_image_check .mcp.json (in your project root)
- ChatGPT Sighttrue base_image_check Settings → Connectors → Advanced → Developer mode
- Claude.ai Sighttrue base_image_check Settings → Connectors → Add custom connector
- LangChain Sighttrue base_image_check pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http sighttrue https://sighttrue.com/api/mcpOther tools on this server
- check_before_install
- check_package
- check_stack
- search_repositories
- compare_repositories
- find_model
- check_eol
- check_provider
- list_readings
- who_can_publish
- package_weight_history
- withdrawn_but_installed
- typosquat_check
- funding_gap
- time_to_fix
- advisory_severity
- runtime_deadlines
- registry_health
- provider_incidents
- provider_transparency
- provider_terms_changed
- model_price_history
- model_withdrawn
- help_availability
- audit_manifest
- diff_since
- watch_add
- watch_changes
- explain_finding
- domain_risk
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.