Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.htagai/htag-docs

REMOTE · API.HTAGAI.COM

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

Available components

0 this week 85 Trust /100

Last scanned (18 hours ago)

Scores higher than 86% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Developer Tools

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability85
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1341 tokens (~111/item across 12 items; 8 tools + 4 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 22 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: pass → fail ▼ functional
    • Tool coverage: 0% → 100% ▲ functional
    • First check of Schema quality: 100 functional
    • Schema quality: good → excellent functional
    • New resource “calling-htag” functional
    • New resource “core-concepts” functional
    • New resource “costs” functional
    • New resource “pricing” functional
    • New tool “get_guide” functional
    • New tool “get_pricing” functional
    • New tool “list_guides” functional
    • “get_api_endpoint” reworded the description of “method” cosmetic
    • “get_api_endpoint” reworded the description of “path” cosmetic
    • “list_api_endpoints” reworded the description of “query” cosmetic
    • “list_api_endpoints” reworded the description of “tag” cosmetic
    • “list_mcp_tools” reworded the description of “server” cosmetic
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://api.htagai.com/mcp/v1/servers/htag-docs/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=developer.prod.htagai.com CN=Amazon RSA 2048 M04,O=Amazon,C=US 30 Aug 2026 15 Mar 2027 RSA 2048 SHA256-RSA 86417255ab9a07079d525b53967aca5
SANs: developer.prod.htagai.com, api.htagai.com, api.prod.htagai.com, agent.htagai.com, developer.htagai.com, agent.prod.htagai.com
CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) CN=Amazon Root CA 1,O=Amazon,C=US 23 Aug 2022 23 Aug 2030 RSA 2048 SHA256-RSA 773124f2a952e3ed18a58bdb85d1bc0ce5f27
CN=Amazon Root CA 1,O=Amazon,C=US (CA) CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US 25 May 2015 31 Dec 2037 RSA 2048 SHA256-RSA 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.htagai.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
htagai.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.htagai.com/mcp/v1/servers/htag-docs/mcp Verified 200
http (plaintext) http://api.htagai.com/mcp/v1/servers/htag-docs/mcp HTTPS enforced 301 https://api.htagai.com/mcp/v1/servers/htag-docs/mcp
MCP tools · 8 exposed · ~702 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_api_endpoint ~113

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.

NameTypeReqDescription
methodstringyesHTTP method, case-insensitive (e.g. 'GET', 'POST').
pathstringyesEndpoint path exactly as listed by `list_api_endpoints`, without the /v1 prefix (e.g. '/property/sold/search').
NameTypeReqDescription
result–yes–

No examples provided.

get_guide ~129

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.

NameTypeReqDescription
namestringyesGuide name: 'calling-htag', 'costs' or 'core-concepts'. 'guide://<name>' is also accepted.
NameTypeReqDescription
resultstringyes–

No examples provided.

get_pricing ~96

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultobjectyes–

No examples provided.

list_api_endpoints ~124

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.

NameTypeReqDescription
query––Optional case-insensitive substring matched against the path, summary and operationId (e.g. 'sold', 'geocode').
tag––Optional OpenAPI tag to filter by, case-insensitive exact match (e.g. 'Property', 'Address Geocode', 'Markets').
NameTypeReqDescription
resultarrayyes–

No examples provided.

list_guides ~51

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes–

No examples provided.

list_mcp_servers ~44

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

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes–

No examples provided.

list_mcp_tools ~80

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.

NameTypeReqDescription
serverstringyesMCP server name as returned by `list_mcp_servers`, e.g. 'htag' or 'htag-docs'.
NameTypeReqDescription
resultarrayyes–

No examples provided.

list_micro_agents ~65

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes–

No examples provided.

Install

How do I install the com.htagai/htag-docs MCP server?

com.htagai/htag-docs is a hosted endpoint at https://api.htagai.com/mcp/v1/servers/htag-docs/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.htagai.com

# add to Claude Code
claude mcp add --transport http com-htagai-htag-docs 'https://api.htagai.com/mcp/v1/servers/htag-docs/mcp'
Common questions

What is the com.htagai/htag-docs MCP server?

com.htagai/htag-docs is an MCP server listed in the public MCP registry as com.htagai/htag-docs. Public HTAG discovery for MCP tools, API endpoints, OpenAPI ops, and agents. This page covers its hosted endpoint (https://api.htagai.com/mcp/v1/servers/htag-docs/mcp).

Is the com.htagai/htag-docs MCP server safe to use?

com.htagai/htag-docs scores 85 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the com.htagai/htag-docs MCP server expose?

com.htagai/htag-docs exposes 8 tools: list_guides, get_guide, get_pricing, list_mcp_servers, list_mcp_tools, and 3 more. Their descriptions and schemas cost roughly 702 tokens of context every time the server is loaded.

Does the com.htagai/htag-docs MCP server require authentication?

No. We connected to com.htagai/htag-docs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the com.htagai/htag-docs MCP server still maintained?

com.htagai/htag-docs is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the com.htagai/htag-docs MCP server?

VerifyMCP ran 13 checks on com.htagai/htag-docs, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.