TariffsChart MCP server
Which servers in the official MCP registry are TariffsChart's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-18
- Registry namecom.tariffschart/tariffschartverified in the MCP registry
The registry name sits under tariffschart.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-18
- Tools2
- Server calls itselfTariffsChart
- Server version1.0.0
- Protocol version2025-06-18
On 2026-10-18 the server answered initialize and tools/list without a sign-in. First answer in 141 ms.
- Answeredmeasuring2 of the 7 daily checks it takes to print a share
- Median first answer149 ms
- Space in an agent's context≈ 1,082 tokensthe definitions of all its tools (2), which an agent carries on every turn
- Tool definitionsA · 92 of 100
- Parameters without a description: in 1 of 2
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The state of vendors' MCP servers: method and numbers →
lookup_hts_base_rateLook up a fresh simple MFN general duty field from TariffsChart’s USITC HTS data. Includes source revision, date and excluded layers. Base-only: never treat this as the final import tariff. Complex or stale rates may be unavailable; use…
review_import_dutyReview an import duty stack with official sources, known subtotals, missing inputs and unresolved applicability. Provide the real USD customs value and entry date. Unknowns stay unresolved; user review states are scenario assumptions. Do…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"tariffschart": {
"type": "http",
"url": "https://mcp.tariffschart.com/mcp"
}
}
}Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.