com.htagai/htag-docs is an MCP server published by com.htagai, hosted at api.htagai.com. When last checked on 2026-11-22 it was working: it answers and lists its tools. It declares 8 tools, including list_guides, get_guide, get_pricing, list_mcp_servers, list_mcp_tools.
Public HTAG discovery for MCP tools, API endpoints, OpenAPI ops, and agents.
6 connections through 5 shared values. Tap any node.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
Inferred from the host name and headers: what a server runs on, not who runs it.
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.
No parameters.
{
"name": "list_guides",
"description": "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.",
"inputSchema": {
"type": "object",
"title": "list_guidesArguments",
"properties": {}
},
"outputSchema": {
"type": "object",
"title": "list_guidesOutput",
"required": [
"result"
],
"properties": {
"result": {
"type": "array",
"items": {
"type": "object",
"additionalProperties": true
},
"title": "Result"
}
}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| name * | string | Guide name: 'calling-htag', 'costs' or 'core-concepts'. 'guide://<name>' is also accepted. |
{
"name": "get_guide",
"description": "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.",
"inputSchema": {
"type": "object",
"title": "get_guideArguments",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"title": "Name",
"description": "Guide name: 'calling-htag', 'costs' or 'core-concepts'. 'guide://<name>' is also accepted."
}
}
},
"outputSchema": {
"type": "object",
"title": "get_guideOutput",
"required": [
"result"
],
"properties": {
"result": {
"type": "string",
"title": "Result"
}
}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}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.
No parameters.
{
"name": "get_pricing",
"description": "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.",
"inputSchema": {
"type": "object",
"title": "get_pricingArguments",
"properties": {}
},
"outputSchema": {
"type": "object",
"title": "get_pricingOutput",
"required": [
"result"
],
"properties": {
"result": {
"type": "object",
"title": "Result",
"additionalProperties": true
}
}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}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).
No parameters.
{
"name": "list_mcp_servers",
"description": "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).",
"inputSchema": {
"type": "object",
"title": "list_mcp_serversArguments",
"properties": {}
},
"outputSchema": {
"type": "object",
"title": "list_mcp_serversOutput",
"required": [
"result"
],
"properties": {
"result": {
"type": "array",
"items": {
"type": "object",
"additionalProperties": true
},
"title": "Result"
}
}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| server * | string | MCP server name as returned by `list_mcp_servers`, e.g. 'htag' or 'htag-docs'. |
{
"name": "list_mcp_tools",
"description": "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.",
"inputSchema": {
"type": "object",
"title": "list_mcp_toolsArguments",
"required": [
"server"
],
"properties": {
"server": {
"type": "string",
"title": "Server",
"description": "MCP server name as returned by `list_mcp_servers`, e.g. 'htag' or 'htag-docs'."
}
}
},
"outputSchema": {
"type": "object",
"title": "list_mcp_toolsOutput",
"required": [
"result"
],
"properties": {
"result": {
"type": "array",
"items": {
"type": "object",
"additionalProperties": true
},
"title": "Result"
}
}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| tag | any | Optional OpenAPI tag to filter by, case-insensitive exact match (e.g. 'Property', 'Address Geocode', 'Markets'). |
| query | any | Optional case-insensitive substring matched against the path, summary and operationId (e.g. 'sold', 'geocode'). |
{
"name": "list_api_endpoints",
"description": "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.",
"inputSchema": {
"type": "object",
"title": "list_api_endpointsArguments",
"properties": {
"tag": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "Tag",
"default": null,
"description": "Optional OpenAPI tag to filter by, case-insensitive exact match (e.g. 'Property', 'Address Geocode', 'Markets')."
},
"query": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "Query",
"default": null,
"description": "Optional case-insensitive substring matched against the path, summary and operationId (e.g. 'sold', 'geocode')."
}
}
},
"outputSchema": {
"type": "object",
"title": "list_api_endpointsOutput",
"required": [
"result"
],
"properties": {
"result": {
"type": "array",
"items": {
"type": "object",
"additionalProperties": true
},
"title": "Result"
}
}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| path * | string | Endpoint path exactly as listed by `list_api_endpoints`, without the /v1 prefix (e.g. '/property/sold/search'). |
| method * | string | HTTP method, case-insensitive (e.g. 'GET', 'POST'). |
{
"name": "get_api_endpoint",
"description": "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.",
"inputSchema": {
"type": "object",
"title": "get_api_endpointArguments",
"required": [
"path",
"method"
],
"properties": {
"path": {
"type": "string",
"title": "Path",
"description": "Endpoint path exactly as listed by `list_api_endpoints`, without the /v1 prefix (e.g. '/property/sold/search')."
},
"method": {
"type": "string",
"title": "Method",
"description": "HTTP method, case-insensitive (e.g. 'GET', 'POST')."
}
}
},
"outputSchema": {
"type": "object",
"title": "get_api_endpointOutput",
"required": [
"result"
],
"properties": {
"result": {
"anyOf": [
{
"type": "object",
"additionalProperties": true
},
{
"type": "null"
}
],
"title": "Result"
}
}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}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.
No parameters.
{
"name": "list_micro_agents",
"description": "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.",
"inputSchema": {
"type": "object",
"title": "list_micro_agentsArguments",
"properties": {}
},
"outputSchema": {
"type": "object",
"title": "list_micro_agentsOutput",
"required": [
"result"
],
"properties": {
"result": {
"type": "array",
"items": {
"type": "object",
"additionalProperties": true
},
"title": "Result"
}
}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}HtAG Documentation server (public, no API key). Use it to plan calls to the HtAG property data API and the HtAG MCP data servers before you make them. Call get_guide('calling-htag') before planning HtAG data calls (the same text is the resource guide://calling-htag). It covers call order for property questions (geocode with limit=1 and check the match, then get_property_summary, then a sold/rented search filtered by propertyType and bedrooms), cost rules (which operations bill per returned row and which per request; filter first; limit=1 to read total_count; no automatic pagination), paging and truncation fields (total, total_count, has_more, next_offset, _truncated), address keys and key spaces, and canonical property types. For HtAG membership discounts (an eligible active HtAG plan, not Starter, reduces rates on supported usage once linked), read get_guide('costs'); users link their plan in the developer portal themselves, so never ask for their HtAG password. Before a read that could return more than about 100 rows, or any paging loop, estimate it in AUD with get_pricing (or a limit=1 probe's `billing` receipt) and state the plan first. Tools: - list_guides: the available guides (name, title, summary, updated). - get_guide(name): full markdown of one guide: calling-htag, costs, core-concepts. - get_pricing: the rate card (AUD per unit by tier and monthly band, plan multipliers, free allowance, as-of date) and how to read the `billing` receipt. - list_api_endpoints(tag?, query?): find REST endpoints in the public OpenAPI spec. - get_api_endpoint(path, method): the full OpenAPI operation; check parameters here before calling. - list_mcp_servers: HtAG MCP servers and whether each is public. - list_mcp_tools(server): tools on one MCP server, with input schemas. - list_micro_agents: callable HtAG micro-agents. Resources: guide://calling-htag, guide://costs, guide://core-concepts (text/markdown); pricing://rate-card (application/json).
Names, descriptions and schemas were written by the server and are shown as data.
Pattern matches on what the server declares. They show what it says it can do, not what it does.
None yet. Changes appear after a server's second daily check.