Model Context Protocol

    Agent-facing tools, ordered by what agents usually need first.

    Forecast tools lead, then asset discovery, canonical data queries, and benchmark evaluation. Every tool reuses the same contracts and credential boundaries as REST.

    See working calls Match REST operations
    HTTP tools
    44
    stdio tools
    44
    tool groups
    5
    Recommended sequence

    Discover, verify, then query.

    1. 1
      Discover

      List assets or schemas before choosing a dataset.

    2. 2
      Check policy

      Read provenance and training eligibility from the asset card.

    3. 3
      Query

      Request forecasts, observations, panels, or benchmark scores.

    Discovery and verification

    Human-readable proof and machine-readable metadata live on the same domain.

    Use this page as the public homepage for Homecastr MCP, and use the well-known discovery files as the machine-readable source of truth for installation and registry indexing.

    Remote endpoint

    The live streamable HTTP MCP endpoint used by remote clients and registry checks.

    /api/mcp/mcp

    Well-known server metadata

    Canonical machine-readable MCP metadata for installation and automatic discovery.

    /.well-known/mcp/server.json

    Server card

    Static discovery document for registries that validate remote MCP servers before listing them.

    /.well-known/mcp/server-card.json

    Smithery listing

    Public listing target and vendor-verification backlink for the Homecastr remote MCP surface.

    https://smithery.ai/servers/danielhardestylewis/homecastr
    Common calls

    Start with a small, complete request

    Forecast an address
    forecast_by_address
    {
  "address": "1000 Brickell Ave Miami FL",
  "year": 2028
}
    Read panel lineage
    get_panel_lineage
    {
  "panel_id": "panel.acs_nationwide"
}
    Find official source links
    list_data_sources
    {
  "source_family": "assessor_tax",
  "panel_id": "panel.hcad_houston"
}
    Load source coverage geography
    get_source_coverage_map
    {}
    Audit reference-boundary coverage
    list_source_coverage_index
    {
  "coverage_feature_id": "coverage.arizona_phoenix_maricopa_pinal",
  "coverage_geometry_role": "reference_boundary"
}
    Read benchmark scores
    get_backtest_scores
    {
  "benchmark_id": "acs_cutoff2016_horizon8_maricopa_realized_acs",
  "target": "total_population"
}
    Complete tool catalog

    All 44 tools

    Extended-only tools are listed last.

    Forecasts

    Start here for ordinary property and market questions. Inputs mirror the corresponding REST geography endpoints.

    • forecast_by_address
    • forecast_by_parcel
    • forecast_by_unit
    • forecast_by_tabblock
    • forecast_by_tract
    • forecast_by_zcta
    • forecast_by_zip3
    • forecast_by_county
    • forecast_by_state
    • forecast_by_h3_cell

    Data discovery and trust

    Discover assets and contracts before requesting records, and preserve policy and provenance metadata in agent use.

    • list_data_assets
    • get_data_asset
    • list_data_sources
    • get_data_source
    • get_panel_lineage
    • get_data_coverage
    • list_source_coverage_index
    • get_source_coverage_map
    • list_data_schemas
    • get_data_schema
    • get_entity
    • get_geography_crosswalk
    • get_provenance
    • get_data_artifact

    Versioned evaluation records

    Read published forecast vintages and benchmark results with pinned provenance and evaluation metadata.

    • get_forecast_vintage
    • get_benchmark_result

    Benchmark compatibility

    Convenience tools for the benchmark-first namespace and its public vintages and score tables.

    • list_benchmark_datasets
    • get_benchmark_dataset
    • get_public_forecast_vintage
    • get_backtest_scores

    Extended stdio tools

    Outlook, training-run, and analytics tools available only on the extended stdio server with their existing credential gates.

    • get_county_outlook
    • list_training_runs
    • get_analytics_events

    Transport

    The app exposes streamable HTTP through /api/mcp. The package also supports stdio for local agent runtimes.

    Authorization

    MCP cannot return a field the same credential could not obtain through REST. Metadata-only and restricted responses stay explicit.

    Errors

    Tool failures preserve stable API error codes, retryability, and documentation links instead of returning unstructured text.

    Documentation

    Start with the job you need to do, then move into the complete interface reference.

    Start and build

    Choose a task before choosing a protocol.

    Start HereForecastsData CatalogBenchmarks

    Interfaces

    REST, MCP, and typed client references.

    REST QuickstartFull API ReferenceMCP ToolsTypeScript SDKPython SDK

    Trust and operations

    Contracts, methodology, and live health.

    Schema ReferenceStatusMethodology