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