htag-docs MCP server
com.htagai/htag-docshtagai.comstreamable-httpv1.0.0Scanned
Public HTAG discovery for MCP tools, API endpoints, OpenAPI ops, and agents.
8 tools: 8 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the htag-docs MCP server can do
The htag-docs MCP server is published by htagai.com, a domain the MCP Registry verified. It has 8 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
1 tool brings in text other people can write (list_guides).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 10, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
8 tools
Only reads 8Show 8 read-only tools
get_api_endpointReturn the full OpenAPI operation for one HTAG REST endpoint — parameters, requestBody, responses, examples.No findings
Why it is in this group
- The name "get_api_endpoint" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_guideReturn 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, billi…No findings
Why it is in this group
- The name "get_guide" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_pricingThe 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 al…No findings
Why it is in this group
- The name "get_pricing" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_api_endpointsList HTAG public REST endpoints.No findings
Why it is in this group
- The name "list_api_endpoints" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_guidesList the HtAG agent guides: name, uri, title, summary, updated date and source URL.Reads text others writeNo findings
Why it is in this group
- The name "list_guides" says "list": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "list" and "uri": it reads web pages, which anyone can write.
Description, as the server wrote 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_mcp_serversList every MCP server HTAG currently exposes.No findings
Why it is in this group
- The name "list_mcp_servers" says "list": a word for reading.
Description, as the server wrote it 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).
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_mcp_toolsList every tool registered on a named MCP server.No findings
Why it is in this group
- The name "list_mcp_tools" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_micro_agentsList every callable HTAG micro-agent — turnkey agents that compose endpoint chains and apply HTAG methodology.No findings
Why it is in this group
- The name "list_micro_agents" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:40 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 0
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://api.htagai.com/.well-known/oauth-protected-resource
- Authorization servers
- https://api.htagai.com
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 added.+1 addedView diff
- Added:get_pricingOnly reads
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http htag-docs https://api.htagai.com/mcp/v1/servers/htag-docs/mcpclaude mcp add --transport http htag-docs https://api.htagai.com/mcp/v1/servers/htag-docs/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__htag-docs__list_guides",
"mcp__htag-docs__get_guide",
"mcp__htag-docs__get_pricing",
"mcp__htag-docs__list_mcp_servers",
"mcp__htag-docs__list_mcp_tools",
"mcp__htag-docs__list_api_endpoints",
"mcp__htag-docs__get_api_endpoint",
"mcp__htag-docs__list_micro_agents"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as htag-docs. Review it before you use it.
Capability tags behind 1 rule
- mcp__htag-docs__list_guides untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.htagai/htag-docs/verify?hash=1ddb4e65ab32f117889b59d161201f48dd2e3ccab88c87d7188c114280ce750d" | jq -e '.changed == false'Pinned hash 1ddb4e65ab32, from Nov 10, 2026, 18:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.htagai/htag-docs/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.htagai/htag-docs)Source: MCP Registry · repository. Synced Oct 21, 2026, 17:56 UTC.
htag-docs MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the htag-docs MCP server safe?
- No scan can promise that. What its definitions show: 8 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the htag-docs MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the htag-docs MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the htag-docs MCP server have?
- 8 tools: 8 read. list_guides, get_guide, get_pricing, list_mcp_servers, list_mcp_tools, list_api_endpoints, get_api_endpoint and list_micro_agents.
Does the htag-docs MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the htag-docs MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the htag-docs MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Oct 29, 2026. Every change is on this page and in its Atom feed.