com.htagai/htag-docs
REMOTE · API.HTAGAI.COM · SCANNED SEP 22
Public HTAG discovery for MCP tools, API endpoints, OpenAPI ops, and agents.
Available components
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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 310 tokens (~62/item across 5 items; 5 tools + 0 resources), lean.Pass
- 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 Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
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
claude mcp add --transport http com-htagai-htag-docs 'https://api.htagai.com/mcp/v1/servers/htag-docs/mcp'
{
"mcpServers": {
"com-htagai-htag-docs": {
"url": "https://api.htagai.com/mcp/v1/servers/htag-docs/mcp"
}
}
} {
"servers": {
"com-htagai-htag-docs": {
"type": "http",
"url": "https://api.htagai.com/mcp/v1/servers/htag-docs/mcp"
}
}
} [mcp_servers.com-htagai-htag-docs] url = "https://api.htagai.com/mcp/v1/servers/htag-docs/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-htagai-htag-docs": {
"type": "remote",
"url": "https://api.htagai.com/mcp/v1/servers/htag-docs/mcp",
"enabled": true
}
}
} openclaw mcp add com-htagai-htag-docs --url 'https://api.htagai.com/mcp/v1/servers/htag-docs/mcp' --transport streamable-http
mcp_servers:
com-htagai-htag-docs:
url: "https://api.htagai.com/mcp/v1/servers/htag-docs/mcp" {
"McpServers": {
"com-htagai-htag-docs": {
"Transport": "http",
"Url": "https://api.htagai.com/mcp/v1/servers/htag-docs/mcp"
}
}
} assistant mcp add com-htagai-htag-docs -t streamable-http -u 'https://api.htagai.com/mcp/v1/servers/htag-docs/mcp'
{
"mcpServers": {
"com-htagai-htag-docs": {
"type": "http",
"url": "https://api.htagai.com/mcp/v1/servers/htag-docs/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 26 Aug 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 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
- 7 Aug 26 0
- The server no longer declares the “experimental” capability functional
- 6 Aug 26 0
- Authorization: unverified → partial ▲ security
- Schema quality: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → pass ▲ functional
- Schema quality: unverified → good ▲ functional
- First check of Tool coverage: 0 functional
- First check of Tool coverage: 100 functional
- New tool “get_api_endpoint” functional
- New tool “list_api_endpoints” functional
- New tool “list_mcp_servers” functional
- New tool “list_mcp_tools” functional
- New tool “list_micro_agents” functional
- 31 Jul 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
- 30 Jul 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
- 27 Jul 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
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 22 Sept 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. | present | 19718 | 13 | Verified |
| htagai.com. | absent | 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 |
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 →
get_api_endpoint ~71
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.
| Name | Type | Req | Description |
|---|---|---|---|
| method | string | yes | – |
| path | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
list_api_endpoints ~73
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | – | – | – |
| tag | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
list_mcp_tools ~57
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.
| Name | Type | Req | Description |
|---|---|---|---|
| server | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
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 82 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 5 tools: list_mcp_servers, list_mcp_tools, list_api_endpoints, get_api_endpoint, list_micro_agents. Their descriptions and schemas cost roughly 310 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 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.