check_against_bumping — PricingLab MCP Tool Read-only
check_against_bumping
(check against bumping) is one of 5 tools on the
PricingLab
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call check_against_bumping from your client
- Claude Code PricingLab check_against_bumping run in your project directory
- Claude Desktop PricingLab check_against_bumping ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor PricingLab check_against_bumping ~/.cursor/mcp.json
- VS Code PricingLab check_against_bumping .vscode/mcp.json
- Zed PricingLab check_against_bumping ~/.config/zed/settings.json
- Windsurf PricingLab check_against_bumping ~/.codeium/windsurf/mcp_config.json
- Cline PricingLab check_against_bumping ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI PricingLab check_against_bumping ~/.gemini/settings.json
- Grok PricingLab check_against_bumping .mcp.json (in your project root)
- ChatGPT PricingLab check_against_bumping Settings → Connectors → Advanced → Developer mode
- Claude.ai PricingLab check_against_bumping Settings → Connectors → Add custom connector
- LangChain PricingLab check_against_bumping pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http pricinglab https://mypricinglab.com/lab/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 10 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.