Htag Docs

com.htagaiPublished by htagai.comOfficial publisherv1.0.0Updated Oct 24, 2026

Public HTAG discovery for MCP tools, API endpoints, OpenAPI ops, and agents.

VerifiedStreamable HTTPWeb executableKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Public, no-auth HTAG discovery server that lets an assistant list HTAG MCP servers, tools, REST endpoints, OpenAPI operations, micro-agents, guides and pricing.

What you can do
  • List HTAG MCP servers and the tools registered on each, with descriptions and input schemas
  • Browse public REST endpoints and read the full OpenAPI operation for one endpoint
  • List callable HTAG micro-agents such as suburb-analysis or comprehensive-dd
  • Read agent guides (calling-htag, costs, core-concepts) and the data API rate card
When to use it
Use it when an assistant needs to find out what HTAG property-intelligence capabilities exist before calling them, or to check call order, cost rules and endpoint parameters. It is a discovery layer, not the data itself.
Requirements
Remote Streamable HTTP endpoint at api.htagai.com; no authentication, API key or environment variables are required for this Docs connector.
Before you install
Read-only and public, but it only describes HTAG's other connectors; the Intelligence and Spatial connectors need OAuth 2.0 or an x-api-key header and are billed per unit, so check the pricing guide before planning paid data calls. Do not commit API keys to client config files.

Installation

In SourceWeft

  1. Open Htag Docs in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.htagai%2Fhtag-docs/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "htag-docs": {
      "type": "http",
      "url": "https://api.htagai.com/mcp/v1/servers/htag-docs/mcp"
    }
  }
}

README

HTAG Property Intelligence MCP

HTAG Property Intelligence MCP gives AI agents read-only access to Australian property intelligence: address standardisation, property summaries and estimates, sold/rented listing search, suburb/LGA market metrics, demographics, economics, geographic concordance, and H3 spatial layers.

This repository publishes the metadata for HTAG's public Model Context Protocol (MCP) servers - 70+ read-only public tools across three connectors - so they can be discovered, evaluated, and configured by AI clients, MCP directories, and integration partners.

[HTAG]


What agents can do with this

  • Standardise and enrich an address. Resolve free-text Australian addresses to canonical form, then pull property summary, demographics, and environment for that location.
  • Estimate value and rent. Get current price and rent estimates for a property, plus market context (growth, scores, trends) for its suburb or LGA.
  • Search comparable sales and rentals. Query sold and rented listings filtered by location, attributes, and time window to support comps and rental benchmarking.
  • Profile a suburb, LGA, or postcode. Combine market metrics, demographics, census medians, and economic indicators (CPI, cash rate) for a single locality view.
  • Reason over spatial layers. Pull H3 hex-indexed price/rent/yield surfaces, socio-environmental indicators, and risk layers; convert between H3 cells and administrative boundaries.
  • Discover capabilities at runtime. List available MCP servers, tools, REST endpoints, and micro-agents via the public Docs connector - no credentials required.

Connectors

ConnectorRegistry nameEndpointToolsAuth
HTAG Intelligencecom.htagai/htag-intelligencehttps://api.htagai.com/mcp/v1/servers/htag/mcp59 read-onlyOAuth 2.0 or x-api-key
HTAG Spatialcom.htagai/htag-spatialhttps://api.htagai.com/mcp/v1/servers/htag-spatial/mcp6 read-onlyOAuth 2.0 or x-api-key
HTAG Docscom.htagai/htag-docshttps://api.htagai.com/mcp/v1/servers/htag-docs/mcp5 read-onlyPublic (no auth)

All connectors use Streamable HTTP transport.

HTAG Intelligence

Read-only property intelligence tools covering address standardisation, property summaries and estimates, sold/rented listing search, suburb and LGA market metrics, market trends, demographics, economics, and geographic concordance across HTAG's property dataset.

HTAG Spatial

Read-only H3 spatial tools for hex-indexed price, rent and yield surfaces, socio-environmental indicators, risk layers, H3 geometry and resolution utilities, and H3-to-administrative concordance.

HTAG Docs

Public capability-discovery connector for listing HTAG MCP servers and their tools, REST API endpoints and OpenAPI operations, and micro-agents. No authentication required.


Endpoints

All endpoints accept MCP requests over HTTPS using Streamable HTTP:

https://api.htagai.com/mcp/v1/servers/htag/mcphttps://api.htagai.com/mcp/v1/servers/htag-spatial/mcphttps://api.htagai.com/mcp/v1/servers/htag-docs/mcp

Authentication

  • OAuth 2.0 - recommended for end-user / interactive agents. Authorization server metadata is discovered directly from each MCP URL; clients that support Dynamic Client Registration with authorization-code + PKCE can sign the user in without any pre-created OAuth client or API key.
  • x-api-key header - optional alternate for server-to-server / headless agents. Issue keys from the Developer Portal and pass as a request header.
  • Public - HTAG Docs requires no credentials.

Never commit API keys to client config files in source control. Store them in your client's secrets store or environment variables.


Scope & Security

  • Public-only scope. This repo documents the three connectors that are safe to expose externally (Intelligence, Spatial, Docs). Internal / non-public connectors are intentionally omitted from this listing.
  • Read-only. All connectors are read-only; no HTAG data is mutated by these MCP servers.
  • HTTPS only. Requests and responses traverse HTTPS only.
  • No pre-provisioning for interactive clients. OAuth 2.0 metadata is discovered directly from the MCP URL and supports Dynamic Client Registration with authorization-code + PKCE, so MCP-capable clients can complete sign-in without a pre-created OAuth client or API key. API keys remain an optional alternate for headless use and are issued from the HTAG Developer Portal; never commit them to MCP client config in source control.
  • Metadata only. This is a metadata repository - no server source code, per-tool schemas, or operational details are published here. Live tool inventories are authoritative via each server's tools/list response and the API reference.
  • Identity and audit. API keys identify the caller for rate limiting, quota, and audit; rotate keys via the Developer Portal.
  • Terms. For acceptable use, data retention, and redistribution of property data, see the Developer Portal.

Not Included in This Public Listing

  • Internal / non-public HTAG connectors.
  • Per-tool input/output schemas - see live tools/list responses or the API reference.
  • Internal routing, infrastructure, and implementation details.

Links


License

MIT (c) HTAG Analytics

Source: README.md at commit 9c58923

Tools

8

list_guides

List the HtAG agent guides: name, uri, title, summary, updated date and source URL. Read 'calling-htag' with `get_guide` before planning HtAG data calls.

Takes no parameters.

get_guide

Return the full markdown of one HtAG agent guide: 'calling-htag' (call order, cost rules, paging, address keys, property types; read it first), 'costs' (billing units, rates, billing headers) or 'core-concepts' (place lookup, address keys and key spaces, levels, dates, null handling). The same content is served as the guide://<name> resources.

Parametersnamerequired

get_pricing

The HtAG data API rate card: list AUD per unit for each tier (Reference, Standard, Enhanced, Premium, Restricted) and each monthly volume band, linked-plan multipliers, the free allowance and an as-of date, plus how to read the `billing` receipt on htag tool results. Use it to estimate a call before making it: units x rate x plan multiplier. Also served as pricing://rate-card.

Takes no parameters.

list_mcp_servers

List every MCP server HTAG currently exposes. Each entry includes the server name, a short description, its mount path, and whether it is public (no auth required).

Takes no parameters.

list_mcp_tools

List every tool registered on a named MCP server. Use `list_mcp_servers` first to discover server names. Each entry includes the tool name, its description, and the JSON-Schema input.

Parametersserverrequired

list_api_endpoints

List HTAG public REST endpoints. Optional `tag` (e.g. 'Markets', 'Property', 'Spatial') and `query` (substring against path / summary) filters. Returns path, method, operationId, tags, and summary for each match.

Parameterstagquery

get_api_endpoint

Return the full OpenAPI operation for one HTAG REST endpoint — parameters, requestBody, responses, examples. Use this BEFORE recommending an endpoint so your parameter hints match the live spec. Returns null if the endpoint is not in the catalogue.

Parameterspathrequiredmethodrequired

list_micro_agents

List every callable HTAG micro-agent — turnkey agents that compose endpoint chains and apply HTAG methodology. Examples: 'suburb-analysis', 'suburb-comparison', 'comprehensive-dd'. Useful when a use case is best served by an existing agent rather than raw endpoint composition.

Takes no parameters.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Htagai integrations