Htag Docs

com.htagai由 htagai.com 发布官方发布者v1.0.0更新于 Oct 24, 2026

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

已验证Streamable HTTP可网页运行知识与记忆开发者工具

概览

AI 生成的概览

公开、无需认证的 HTAG 发现服务,让助手列出 HTAG 的 MCP 服务器、工具、REST 端点、OpenAPI 操作、微代理、指南与价格。

可以做什么
  • 列出 HTAG 的 MCP 服务器及每个服务器注册的工具,含描述与输入 schema
  • 浏览公开 REST 端点,并读取单个端点的完整 OpenAPI 操作
  • 列出可调用的 HTAG 微代理,例如 suburb-analysis、comprehensive-dd
  • 读取代理指南(calling-htag、costs、core-concepts)与数据 API 价目表
适用场景
当助手需要先了解 HTAG 有哪些房产情报能力再决定调用,或需要确认调用顺序、计费规则和端点参数时使用。它是发现层,本身不提供数据。
运行要求
远程 Streamable HTTP 端点 api.htagai.com;此 Docs 连接器无需认证、API 密钥或环境变量。
安装前请注意
只读且公开,但仅描述 HTAG 的其他连接器;Intelligence 与 Spatial 连接器需要 OAuth 2.0 或 x-api-key 请求头,并按单位计费,规划付费数据调用前应先查看价格指南。不要把 API 密钥提交到客户端配置文件中。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Htag Docs,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/com.htagai%2Fhtag-docs/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "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

来源:README.md,提交 9c58923

工具

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.

无需输入参数。

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.

输入参数name必填

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.

无需输入参数。

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).

无需输入参数。

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.

输入参数server必填

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.

输入参数tagquery

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.

输入参数path必填method必填

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.

无需输入参数。

版本历史

1
  1. v1.0.0最新Sep 16, 2026

评分

已满足适用检查项的 100%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

其他 Htagai 集成