who_should_care — DFX Real Estate Intelligence MCP Tool
who_should_care
(who should care) is one of 89 tools on the
DFX Real Estate Intelligence
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call who_should_care from your client
- Claude Code DFX Real Estate Intelligence who_should_care run in your project directory
- Claude Desktop DFX Real Estate Intelligence who_should_care ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor DFX Real Estate Intelligence who_should_care ~/.cursor/mcp.json
- VS Code DFX Real Estate Intelligence who_should_care .vscode/mcp.json
- Zed DFX Real Estate Intelligence who_should_care ~/.config/zed/settings.json
- Windsurf DFX Real Estate Intelligence who_should_care ~/.codeium/windsurf/mcp_config.json
- Cline DFX Real Estate Intelligence who_should_care ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI DFX Real Estate Intelligence who_should_care ~/.gemini/settings.json
- Grok DFX Real Estate Intelligence who_should_care .mcp.json (in your project root)
- ChatGPT DFX Real Estate Intelligence who_should_care Settings → Connectors → Advanced → Developer mode
- Claude.ai DFX Real Estate Intelligence who_should_care Settings → Connectors → Add custom connector
- LangChain DFX Real Estate Intelligence who_should_care pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http us-property-parcel-real-estate-debt https://exchange-production-9123.up.railway.app/mcpOther tools on this server
- resolve_address
- resolve_organization
- get_occupancy
- get_property_record
- search_property_events
- search_bank_cre_exposure
- search_subsidised_housing
- search_parcels
- what_can_dfx_answer
- changes_since
- debt_maturity_schedule
- dfx_coverage
- search_family_offices
- get_family_office
- search_family_office_investments
- search_independent_sponsors
- get_independent_sponsor
- search_sponsor_capital_providers
- search_private_companies
- search_sponsor_deals
- search_pending_ownership_changes
- search_vc_firms
- get_vc_firm
- search_vc_investments
- search_vc_funds
- search_pe_firms
- get_pe_firm
- search_pe_funds
- get_pe_fund
- search_pe_transactions
- search_pe_platforms
- find_pe_buyers_for_company
- find_pe_companies_for_buyer
- find_pe_addons_for_platform
- search_ria
- get_ria_firm
- get_ria_advisor
- resolve_ria_advisor
- search_ria_funds
- search_ria_advisor_moves
- search_ria_teams
- search_ria_ma
- search_ria_changes
- get_ria_trends
- get_ria_capital_links
- get_ria_practice
- search_ria_practices
- search_ria_anomalies
- search_ria_offices
- search_private_credit
- get_credit_provider
- get_bdc_portfolio
- get_borrower_capital_structure
- get_credit_facility
- search_credit_maturities
- search_sponsor_lender
- find_lenders_for_financing
- search_private_credit_changes
- search_allocators
- get_allocator
- search_allocator_commitments
- search_re_fund_managers
- get_re_fund_manager
- search_re_fund_vehicles
- get_re_fund_vehicle
- get_re_fund_trends
- get_capital_paths
- get_commitments
- get_borrower_facilities
- get_sponsor_lenders
- search_capital_changes
- search_entities
- resolve_name
- get_entity
- search_people
- search_relationships
- relationship_path
- search_events
- verify
- find_capital_for_opportunity
- find_opportunities_for_capital
- explain_match
- why_now
- search_documents
- find_real_estate_lenders
- search_cmbs_loans
- search_signals
- search_opportunities
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.