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