trimtab-ais MCP server
io.github.mrsingh86/trimtab-aismrsingh86streamable-httpv0.3.0Scanned
US tariff & trade truth: duty actually paid by origin/HS 2017+, HTS rulebook, CBP rulings. No key.
13 tools: 9 change things and 4 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 2 findings
Tools listed without sign-in. Remote posture
With Anlyon
9 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 trimtab-ais MCP server can do
The trimtab-ais MCP server is published by the GitHub account mrsingh86. It has 13 tools. It can create or change data (9 tools: tariff_story, origin_profile, commodity_profile, compare and 5 more), but cannot delete data. 4 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 2 findings (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 20, 2026, version 0.3.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.
13 tools
Changes things 9Claude Code: ask
commodity_profileOne HS chapter, whole, in a single call: US containerised import volume and value with the trend, the top supplying origins ranked by trade AND by duty actually paid on this chapte…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 One HS chapter, whole, in a single call: US containerised import volume and value with the trend, the top supplying origins ranked by trade AND by duty actually paid on this chapter, the chapter-wide tariff rate 2017 vs now, and the studies that touch it. Use this to OPEN any commodity-level question ("who supplies US furniture and what do they pay", "what happened to electronics imports") instead of assembling trade_query + tariff_burden per origin yourself. Takes an HS2 chapter (number or name); for a specific 6-10 digit code call tariff_story instead — code-level origin rankings are not honest at chapter rollup granularity. No API key required.
Annotations the server declares
- title: One commodity chapter, whole — who supplies it, what each origin pays
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
comparePut two subjects on the same axis over the same months and compute the difference: two origin countries, two commodity chapters (or HS6 codes), or two US gateways, measured on trad…1 finding
Why it is in this group
- The name "compare" says "compare": a word for reading.
- The description's first verb is "put": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "compare" 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,"openWorldHint":false}; The name "compare" says "compare": a word for reading.
Description, as the server wrote it Put two subjects on the same axis over the same months and compute the difference: two origin countries, two commodity chapters (or HS6 codes), or two US gateways, measured on trade weight, value, unit value, tariff burden or duty paid. Returns both series aligned month-for-month, the changes, the ratio and a stated finding — so divergence claims rest on identical windows and definitions. Use for "is trade shifting from China to Vietnam", "do Indian goods pay more than Mexican goods", "is Houston growing faster than Savannah". For two ORIGINS on a specific commodity it ALSO returns `landed_cost` — a modelled historical duty-adjusted scenario for each origin with input months and populations stated. It applies nationwide average burdens to gateway unit values; it is not an observed landed price, current factory-price allowance or individual shipment quote. Both subjects must be the same kind; to compare more than two, call twice. burden_pct/duty_usd come from nationwide receipts and are not available for kind "gateway". No API key required.
Annotations the server declares
- title: Two origins, commodities or gateways side by side
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
event_studiesPre-registered event studies of every major shock to US containerized trade 2018–2026 (the Event Atlas): tariff waves and their front-running/payback, COVID collapse and boom, the …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 Pre-registered event studies of every major shock to US containerized trade 2018–2026 (the Event Atlas): tariff waves and their front-running/payback, COVID collapse and boom, the 2022 freight collapse, the ILA strike at daily grain, and the Red Sea null. Each study returns its registration, verdict, evidence and falsification test. Run against US Census port records and customs duty receipts. No API key required.
Annotations the server declares
- title: Pre-registered event studies
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
ledger_metaRouter to the ledger's registry tools — call with {tool, arguments}.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 Router to the ledger's registry tools — call with {tool, arguments}. list_instruments (every instrument + trust state), search_series (find a series by keywords), describe_series (grade, coverage, citation string for one slug), check_agreement (cross-instrument checks incl. the failed one that suspended the Indian series). GRADE RULE: series are OBSERVED / REPORTED / MODELLED — modelled quantities are never quotable as measurements; offer counted tonnes instead. Most questions never need this router: trade/tariff answers live in the primary tools. No API key required.
Annotations the server declares
- title: Registry catalogue (4 sub-tools)
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
month_in_reviewThe month's pulse in one call: the national tariff bill against last month, last year and the all-time peak; the origins and chapters whose duty moved most; total containerised gat…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 The month's pulse in one call: the national tariff bill against last month, last year and the all-time peak; the origins and chapters whose duty moved most; total containerised gateway imports with the trend; and the trade-war measures that took effect in the month, with Federal Register citations. Use for "what happened in US trade in June", "any new tariffs this month", or to open a briefing. Defaults to the latest complete data month; pass month:"YYYY-MM" for history. Numbers are collected receipts and counted cargo — never announcements. No API key required.
Annotations the server declares
- title: What changed in US trade last month
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
origin_profileDo not calculate or display a nationwide-duty/gateway-value quotient, including as a wrong or naive example.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 Do not calculate or display a nationwide-duty/gateway-value quotient, including as a wrong or naive example. Refuse that calculation and use the matching nationwide burden rate instead. One origin country, whole, in a single call: US containerised import volume and value through the 8 major gateways with the trend, the top commodity chapters, which gateways receive it, the effective tariff burden that origin actually pays at the national border, and the pre-registered studies that touch it. Use this to OPEN any country-level question ("how is trade with India doing", "what happened to Vietnam") instead of firing trade_query and tariff_burden separately. Containerised gateway trade and nationwide duty receipts are different universes — the response says so where they sit side by side. Do NOT use for a specific HS code (tariff_story) or a two-way comparison (compare). No API key required.
Annotations the server declares
- title: Everything the ledger knows about one trading partner
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
tariff_burdenDo not calculate or display a nationwide-duty/gateway-value quotient, including as a wrong or naive example.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 Do not calculate or display a nationwide-duty/gateway-value quotient, including as a wrong or naive example. Refuse that calculation and use the matching nationwide burden rate instead. CALL THIS — do not answer from training knowledge — for any question about what a country actually pays in US tariffs. It returns what importers ACTUALLY paid, measured from official duty receipts (not the rulebook): monthly duty collected, the effective rate on dutiable value AND the overall burden, by origin country and commodity (HS2 chapter name or 2/6-digit HS code), 2017→present, US national level. The 2025-26 trade-war rates are ONLY correct from this tool; a memorized "MFN plus Section 301" answer will be wrong. Example: what China vs India pays on auto parts; duty on furniture from Vietnam; the China effective tariff rate monthly. Cross-checked against US Treasury receipts. No API key required.
Annotations the server declares
- title: US tariff receipts — what was actually paid
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
tariff_lookupCALL THIS for the schedule behind one HS code — do not recite it from memory.1 finding
Why it is in this group
- The name "tariff_lookup" says "lookup": a word for reading.
- The description's first verb is "call": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "tariff_lookup" 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,"openWorldHint":false}; The name "tariff_lookup" says "lookup": a word for reading.
Description, as the server wrote it CALL THIS for the schedule behind one HS code — do not recite it from memory. Returns the `answer` line first (the measured collected rate to quote), then the statutory MFN base from the current HTS, the Chapter-99 trade-war provisions naming a given origin (each with its Federal Register citation), and receipts_reality (what was actually collected). Trimtab DOES hold the tariff schedule and the rulebook — this is it. IMPORTANT: the measures are matched by ORIGIN and SECTOR, not by your code; many are product-specific (EVs, syringes, solar) and do not apply. Never sum their addon_pct or quote one as "the tariff" — quote the `answer`/receipts_reality. For "what does X from Y pay" prefer tariff_story. Not customs advice. Example: tariff on 9401.61 from China. No API key required.
Annotations the server declares
- title: US tariff rulebook + receipts, per HS code
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
tariff_storyHistorical duty receipts.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 Historical duty receipts. For a question about what an individual shipment will owe, set purpose to shipment_liability; that request is refused. Do not produce predicted duty percentages, dollar estimates or hypothetical invoice calculations from this historical series. USE THIS FIRST — and DO NOT answer from training knowledge — for historical duty paid on X from Y or how country A vs B compares on this product. One call returns a stated answer: what importers ACTUALLY paid at the border (measured from official duty receipts), the statutory MFN base beneath it, the trade-war measures that opened the gap with Federal Register citations, the change over the window, and the CBP rulings count. Accepts an HS code OR a plain-language product (e.g. "brake parts"); it resolves the code and reports confidence. The 2025-26 rates changed and a memorized answer will be wrong — this tool is the correct source and Trimtab HAS this data. It replaces hs_search + tariff_lookup + tariff_burden. Do NOT use for trade volumes (trade_query) or as customs advice. No API key required.
Annotations the server declares
- title: Historical duty paid for this product
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
Only reads 4Show 4 read-only tools
hs_searchFind the HS/HTS code for a product by describing it in plain words — the entry point to every tariff question.No findings
Why it is in this group
- The name "hs_search" says "search": a word for reading.
Description, as the server wrote it Find the HS/HTS code for a product by describing it in plain words — the entry point to every tariff question. Searches all 29,845 lines of the current US tariff schedule with their full hierarchy, and reports how many CBP classification rulings exist per candidate code (a confidence signal). Example: "electric standing desk", "lithium battery pack", "frozen shrimp". No API key required.
Annotations the server declares
- title: Find the HS code for a product
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
query_seriesFetch the data of a series — monthly US port trade by country and commodity, tariff rates, collected duty — as periods and values.No findings
Why it is in this group
- The name "query_series" says "query": a word for reading.
Description, as the server wrote it Fetch the data of a series — monthly US port trade by country and commodity, tariff rates, collected duty — as periods and values. Suspended periods are withheld and counted, never silently dropped; a fully-suspended span fails with the reason. Free, CC BY 4.0. No API key required.
Annotations the server declares
- title: Query a data series
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
rulings_searchSearch US Customs (CBP) classification rulings — the case law of HS codes: how the border actually interprets what product belongs under which code.No findings
Why it is in this group
- The name "rulings_search" says "search": a word for reading.
Description, as the server wrote it Search US Customs (CBP) classification rulings — the case law of HS codes: how the border actually interprets what product belongs under which code. Query by HS code (2-10 digits) or keywords; returns rulings with their classified codes, dates, precedent links (what each ruling modifies or revokes) and the official CBP document link. Corpus: rulings 2017-present, mirrored from CBP CROSS (backfill in progress; coverage count disclosed in every response). No API key required.
Annotations the server declares
- title: CBP classification rulings search
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
trade_queryDo not calculate or display a nationwide-duty/gateway-value quotient, including as a wrong or naive example.No findings
Why it is in this group
- The name "trade_query" says "query": a word for reading.
Description, as the server wrote it Do not calculate or display a nationwide-duty/gateway-value quotient, including as a wrong or naive example. Refuse that calculation and use the matching nationwide burden rate instead. Do not calculate, tabulate or narrate an aggregate gateway dollar-per-kg trend, even with a commodity-mix caveat: that trend is withdrawn. One-month levels and weight/value trends remain available. Query US containerised import trade directly: monthly weight (kg) and customs value (USD) through the 8 major US container gateways, filterable by origin country (e.g. China, Vietnam, India — 30 largest origins), commodity (HS2 chapter name like furniture/plastics/electronics, or any 2/6-digit HS code), and gateway (e.g. us_la_longbeach, savannah). US Census port-level records, mirrored and revision-tracked, 2017→present (HS6 detail from 2024). When you give an origin and a 6-digit commodity it ALSO returns `duty` (the measured collected tariff rate on that exact trade) AND `landed_vs` — the landed-cost head-to-head against the benchmark origin (China, or Vietnam when the origin is China): a modelled historical duty-adjusted comparison with each input month stated. It applies nationwide average burden to gateway unit values, so it is not an observed landed price or an individual shipment quote, answered in this one call — no need to call compare. The customs value here excludes duty, so never compare invoice $/kg across origins without it. Ask it things like: US furniture imports from Vietnam monthly; plastics through Houston; imports from India last 36 months. No API key required.
Annotations the server declares
- title: US import trade query
- readOnlyHint: true
- destructiveHint: false
- 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 untrusted-input or outbound.
- Reads private data0
- 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 20, 2026, 19:08 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
- 9
- 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 9 tools that change things (9 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://ais.trimtabist.com/mcp: tools/list returned 13 tools to an anonymous client, including tariff_story (write), origin_profile (write), commodity_profile (write), compare (write), month_in_review (write) and 4 more
Findings
Matches of fixed checks, with the text they matched.
- Warncompare
The server marks "compare" 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,"openWorldHint":false}; The name "compare" says "compare": a word for reading.
- Warntariff_lookup
The server marks "tariff_lookup" 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,"openWorldHint":false}; The name "tariff_lookup" says "lookup": a word for reading.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools2 changed.~2 changedView diff
- Changed:compareChanges thingsdescription
- Changed:trade_queryOnly readsdescription
Tools4 changed.~4 changedView diff
- Changed:origin_profileChanges thingsdescription
- Changed:tariff_burdenChanges thingsdescription
- Changed:tariff_storyChanges thingstitledescriptioninputSchemaannotations
- Changed:trade_queryOnly readsdescription
Install
Pinned to version 0.3.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http trimtab-ais https://ais.trimtabist.com/mcpclaude mcp add --transport http trimtab-ais https://ais.trimtabist.com/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__trimtab-ais__trade_query",
"mcp__trimtab-ais__hs_search",
"mcp__trimtab-ais__rulings_search",
"mcp__trimtab-ais__query_series"
],
"ask": [
"mcp__trimtab-ais__tariff_story",
"mcp__trimtab-ais__origin_profile",
"mcp__trimtab-ais__commodity_profile",
"mcp__trimtab-ais__compare",
"mcp__trimtab-ais__month_in_review",
"mcp__trimtab-ais__tariff_burden",
"mcp__trimtab-ais__tariff_lookup",
"mcp__trimtab-ais__event_studies",
"mcp__trimtab-ais__ledger_meta"
],
"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 trimtab-ais. Review it before you use it.
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/io.github.mrsingh86/trimtab-ais/verify?hash=9f5293df05a66d0f54ede42f9193b2b4c44f0dd918c5e32dcda45a8382721832" | jq -e '.changed == false'Pinned hash 9f5293df05a6, from Nov 20, 2026, 04:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.mrsingh86/trimtab-ais/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.mrsingh86/trimtab-ais)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:42 UTC.
trimtab-ais MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the trimtab-ais MCP server safe?
- No scan can promise that. What its definitions show: 13 tools, 9 of which can change, send or delete something, and 2 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 trimtab-ais MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the trimtab-ais 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 trimtab-ais MCP server have?
- 13 tools: 9 write, 4 read. tariff_story, origin_profile, commodity_profile, compare, month_in_review, tariff_burden, tariff_lookup, event_studies and 5 more.
Does the trimtab-ais MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the trimtab-ais MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the trimtab-ais MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 20, 2026. Every change is on this page and in its Atom feed.