htsapi.dev MCP server
dev.htsapi/mcphtsapi.devstreamable-httpv1.0.0Scanned
HTS with its legal notes, 222,000+ CBP rulings with status, what they quote on a heading. Keyless.
8 tools: 6 change things and 2 only read.
- Reads private data · 1
- Reads text others write · 0
- Can send data out · 0
- 4 findings
Tools listed without sign-in. Remote posture
With Anlyon
6 tools here change things. Govern them.
- 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 htsapi.dev MCP server can do
The htsapi.dev MCP server is published by htsapi.dev, a domain the MCP Registry verified. It has 8 tools. It can create or change data (6 tools: lookup_hts_code, importers_paid, get_notes, heading_scope and 2 more), but cannot delete data. 2 tools only read.
1 tool reads private data (get_notes).
The fixed checks matched 4 findings (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 19, 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
Changes things 6Claude Code: ask
classify_productClassify a product to a US HTS code.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Classify a product to a US HTS code. COSTS 1 CREDIT (refunded if it fails). Takes 10-60 s. Read `answer` first. `answer.code` is as deep as the facts given decide (10 digits when they do). When they do not, `answer.options` are the codes it could be, each with its `condition`, base rate and `importers_paid`, and `answer.question` is the fact that decides: ask the user, then call again with the answer added to the description (a new call, 1 credit). `candidates` carry the reasoning and the CBP rulings behind each code.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
get_notesThe legal text that decides between headings, from the official US schedule.Reads private data1 finding
Why it is in this group
- The name "get_notes" says "get": a word for reading.
- The input takes a statement or command to run (input.code), which can change anything it can reach.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- private-dataThe name "get_notes" says "get" and "note": it reads notes.
Findings
- Warn
The server marks "get_notes" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "get_notes" says "get": a word for reading.
Description, as the server wrote it The legal text that decides between headings, from the official US schedule. With a code: its section's notes and its chapter's notes, subheading notes, Additional U.S. Notes and statistical notes. These have legal force (GRI 1): they exclude goods from a chapter ("this chapter does not cover...") and define terms. Without a code: the General Rules of Interpretation and the Additional U.S. Rules of Interpretation. The WCO Explanatory Notes are not included (copyrighted); heading_scope gives the passages CBP rulings quote from them.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
heading_scopeWhat CBP's rulings quote and decide on a heading: for deciding whether a product falls in it.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it What CBP's rulings quote and decide on a heading: for deciding whether a product falls in it. Give the product to get what decides for it first. `passages`: the lines rulings quote when deciding (mostly from the WCO Explanatory Notes, not published free; fragments, not the whole note), each with the rulings that quote it: their goods, HQ or NY, date, status and what CBP concluded; `exclusion` marks text on what the heading does not cover. `notes_applied`: the legal notes rulings applied to the heading. `cited_without_quote`: rulings that relied on its explanatory note without quoting it. Each passage is as a ruling quotes it.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
importers_paidWhat importers from a country actually paid on a code in the latest 3 months Census has published: base rate plus Chapter 99 duties (Section 301, 232 and the like), as a percent of…1 finding
Why it is in this group
- The input takes a statement or command to run (input.code), which can change anything it can reach.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "importers_paid" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input takes a statement or command to run (input.code), which can change anything it can reach.
Description, as the server wrote it What importers from a country actually paid on a code in the latest 3 months Census has published: base rate plus Chapter 99 duties (Section 301, 232 and the like), as a percent of value, by month. Not the duty a shipment will owe today (Census is about 2 months behind and the rules change), and anti-dumping/countervailing duties are not included. For "what will this cost", not for classifying.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
lookup_hts_codeThe tariff schedule, one level at a time, the way a classifier reads it.1 finding
Why it is in this group
- The name "lookup_hts_code" says "lookup": a word for reading.
- The input takes a statement or command to run (input.code), which can change anything it can reach.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "lookup_hts_code" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "lookup_hts_code" says "lookup": a word for reading.
Description, as the server wrote it The tariff schedule, one level at a time, the way a classifier reads it. No code: the 22 sections and their chapters, for goods no ruling covers. A chapter (82) lists its headings with their legal text; a heading (8205) lists its subheadings in words; a subheading or line gives its path from the heading (an "Other" line says what it is not), base rates with the special-rate programs named, the 10-digit lines under it and the newest current CBP rulings under it. A code no longer in the schedule falls back to the nearest level that is. What importers paid is a separate tool, importers_paid.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
rulings_under_codeEvery CBP ruling that classifies goods under a code: for checking a code someone already has.1 finding
Why it is in this group
- The input takes a statement or command to run (input.code), which can change anything it can reach.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "rulings_under_code" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input takes a statement or command to run (input.code), which can change anything it can reach.
Description, as the server wrote it Every CBP ruling that classifies goods under a code: for checking a code someone already has. `rulings` are current (not revoked), newest first, or closest to `product` first, each with what its goods were; `moved_away` are rulings CBP revoked off this code and the codes the revoking ruling put the goods under. If similar goods were moved away, the code is in doubt.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 2Show 2 read-only tools
get_rulingOne CBP ruling: its full text, HTS codes, status and, when revoked or modified, the ruling that did it, the codes it moved the goods to, and the sentence that says so.No findings
Why it is in this group
- The name "get_ruling" says "get": a word for reading.
Description, as the server wrote it One CBP ruling: its full text, HTS codes, status and, when revoked or modified, the ruling that did it, the codes it moved the goods to, and the sentence that says so. Codes the current schedule no longer has are listed in `obsolete_codes`. `cites`: the explanatory notes, legal notes and GRIs it relies on (heading_scope shows what rulings say a heading covers).
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
search_rulingsCBP rulings for a product described in plain words, by meaning.No findings
Why it is in this group
- The name "search_rulings" says "search": a word for reading.
Description, as the server wrote it CBP rulings for a product described in plain words, by meaning. Each ruling comes with its HTS codes, its status (current, modified, superseded) and the product facts CBP classified. `by_code` lists the subheadings current rulings point to, in the order of the rulings, each with its HQ rulings, newest ruling and `lines`: the full codes under it with the rulings for each, which is where the facts that decide between lines show.
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 untrusted-input or outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- 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 19, 2026, 17:19 UTC, unchanged since Nov 19, 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
- 6
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 6 tools that change things (6 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://htsapi.dev/mcp: tools/list returned 8 tools to an anonymous client, including lookup_hts_code (write), importers_paid (write), get_notes (write), heading_scope (write), rulings_under_code (write) and 1 more
Findings
Matches of fixed checks, with the text they matched.
- Warnlookup_hts_code
The server marks "lookup_hts_code" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "lookup_hts_code" says "lookup": a word for reading.
- Warnimporters_paid
The server marks "importers_paid" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input takes a statement or command to run (input.code), which can change anything it can reach.
- Warnget_notes
The server marks "get_notes" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "get_notes" says "get": a word for reading.
The server marks "rulings_under_code" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input takes a statement or command to run (input.code), which can change anything it can reach.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http htsapi https://htsapi.dev/mcpclaude mcp add --transport http htsapi https://htsapi.dev/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__htsapi__search_rulings",
"mcp__htsapi__get_ruling"
],
"ask": [
"mcp__htsapi__lookup_hts_code",
"mcp__htsapi__importers_paid",
"mcp__htsapi__get_notes",
"mcp__htsapi__heading_scope",
"mcp__htsapi__rulings_under_code",
"mcp__htsapi__classify_product"
],
"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 htsapi. Review it before you use it.
Capability tags behind 1 rule
- mcp__htsapi__get_notes private-data
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/dev.htsapi/mcp/verify?hash=46ed48ccd18b25218df091c016c71febafc3c37340edd8167b28dcd825831be2" | jq -e '.changed == false'Pinned hash 46ed48ccd18b, from Nov 19, 2026, 07:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/dev.htsapi/mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/dev.htsapi/mcp)Source: MCP Registry · repository. Synced Nov 19, 2026, 08:17 UTC.
htsapi.dev MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the htsapi.dev MCP server safe?
- No scan can promise that. What its definitions show: 8 tools, 6 of which can change, send or delete something, and 4 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the htsapi.dev MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the htsapi.dev 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 htsapi.dev MCP server have?
- 8 tools: 6 write, 2 read. lookup_hts_code, importers_paid, get_notes, heading_scope, rulings_under_code, classify_product, search_rulings and get_ruling.
Does the htsapi.dev MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the htsapi.dev MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the htsapi.dev MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.