get_bid_check_result — TenderCrest AI MCP Tool Read-only
get_bid_check_result
(get bid check result) is one of 14 tools on the
TenderCrest AI
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_bid_check_result from your client
- Claude Code TenderCrest AI get_bid_check_result run in your project directory
- Claude Desktop TenderCrest AI get_bid_check_result ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor TenderCrest AI get_bid_check_result ~/.cursor/mcp.json
- VS Code TenderCrest AI get_bid_check_result .vscode/mcp.json
- Zed TenderCrest AI get_bid_check_result ~/.config/zed/settings.json
- Windsurf TenderCrest AI get_bid_check_result ~/.codeium/windsurf/mcp_config.json
- Cline TenderCrest AI get_bid_check_result ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI TenderCrest AI get_bid_check_result ~/.gemini/settings.json
- Grok TenderCrest AI get_bid_check_result .mcp.json (in your project root)
- ChatGPT TenderCrest AI get_bid_check_result Settings → Connectors → Advanced → Developer mode
- Claude.ai TenderCrest AI get_bid_check_result Settings → Connectors → Add custom connector
- LangChain TenderCrest AI get_bid_check_result pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http tendercrest-ai https://www.tendercrestai.com/mcpOther 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.