area_stock_profile — MarketCode MCP Tool
area_stock_profile
(area stock profile) is one of 106 tools on the
MarketCode
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call area_stock_profile from your client
- Claude Code MarketCode area_stock_profile run in your project directory
- Claude Desktop MarketCode area_stock_profile ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor MarketCode area_stock_profile ~/.cursor/mcp.json
- VS Code MarketCode area_stock_profile .vscode/mcp.json
- Zed MarketCode area_stock_profile ~/.config/zed/settings.json
- Windsurf MarketCode area_stock_profile ~/.codeium/windsurf/mcp_config.json
- Cline MarketCode area_stock_profile ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI MarketCode area_stock_profile ~/.gemini/settings.json
- Grok MarketCode area_stock_profile .mcp.json (in your project root)
- ChatGPT MarketCode area_stock_profile Settings → Connectors → Advanced → Developer mode
- Claude.ai MarketCode area_stock_profile Settings → Connectors → Add custom connector
- LangChain MarketCode area_stock_profile pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http marketcode https://mcp.marketcode.ai/mcpOther tools on this server
- entity_search_capabilities
- lookup_entities
- ask_question
- search_entities
- search_summary
- market_profile
- entity_relationships
- actor_network
- actor_path
- address_autocomplete
- address_resolve
- address_by_uprn
- address_by_postcode
- property_lookup
- property_reconcile
- market_facts
- market_ranking
- market_volume_series
- market_index_series
- market_yields
- market_forecast
- supply_demand
- time_adjustment
- commercial_index_series
- commercial_rent_index_series
- market_volume_ranking
- transactions_by_uprn
- property_summary
- property_history
- property_comps
- property_flood_risk
- valuation_estimate
- valuation_full
- property_lease
- property_lease_batch
- property_risk_report
- property_risk_report_batch
- comps_adjustments
- valuation_comparables
- valuation_rent_comparables
- subject_transaction_anchor
- valuation_accuracy
- planning_designations
- planning_check
- planning_applications
- constraints_for_geometry
- strategic_sites
- policy_context
- lpa_profile
- planning_appeals
- grid_capacity
- site_access
- area_resolve
- area_reverse_geocode
- ownership_by_title
- ownership_by_company
- auction_lots
- auction_stats
- distressed_assets
- cost_index
- site_appraisal
- mortgage_rates
- lha_rate
- council_tax_band
- auction_discount
- auction_comps
- epc_certificates
- energy_profile
- retrofit_candidates
- solar_potential
- agent_activity
- listing_history
- equity_estimate
- long_held_high_equity
- owner_profile
- building_physical
- mixed_use_buildings
- plot_utilisation
- h3_density
- sourcing_search
- sourcing_owners
- query_semantic
- asking_price_index_series
- asking_rent_index_series
- listing_market_series
- listing_stock_series
- property_planning_history
- property_planning_history_batch
- commercial_property
- build_cost
- data_coverage
- sourcing_strategies
- sourcing_live_listings
- sourcing_offmarket_owners
- land_assembly
- planning_precedents
- commercial_market
- sourcing_commercial
- parcel_lookup
- changes_since
- property_rental_estimate
- property_energy_retrofit
- property_report
- area_report
- property_media
This list was read from the server itself, by connecting to it and calling tools/list on 5 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.