mcpbeat Sign in

tariff.watch MCP Server

by jaketdaniels Your server? Claim it
not responding

tariff.watch is listed as active in the registry but did not answer our last check. It exposes 3 tools.

Source-linked US tariff and trade-action changes: legal status, effective dates, dated archive.

Uptime history 91 days of history · worst day 0%
91 days agonow
0.0%
Uptime 24h
0 of 92 checks
3
Tools
read from the server
31 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 6

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 9 August 2026. No other catalogue keeps this.

9 Aug 3 tools appeared tariffs_effective_dates, tariffs_get_source, tariffs_list_changes
9 Aug 2 tools disappeared exec, run_code
9 Aug a tool changed version

tariff.watch does not always answer

Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

run in your terminal
claude mcp add tariff-watch --transport http https://tariff.watch/mcp
Settings → Connectors → Add custom connector, then paste this address
https://tariff.watch/mcp
~/.codex/config.toml
[mcp_servers.tariff-watch]
url = "https://tariff.watch/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "tariff-watch": {
      "url": "https://tariff.watch/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "tariff-watch": {
      "type": "http",
      "url": "https://tariff.watch/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

tariffs
tariffs_effective_dates
List effective dates, comment deadlines, and hearings carried by trade actions published since a date.
tariffs_get_source
Get one trade-action source record by Federal Register document number.
tariffs_list_changes
List source-linked tariff, customs, and trade-action changes.

Tools removed

Tools this server used to expose. Anything built against them stopped working on the day they went.

exec
removed 9 Aug 2026
run_code
removed 9 Aug 2026

Endpoints

URLTransportStateLatencyChecked
https://tariff.watch/mcp streamable-http answering 31 ms 2 min ago

Alternatives to tariff.watch

same job, measured the same way
Casimo Research — casino terms & changes
by casimo

Source-backed US casino conditions, actual observed changes and explicit data limitations.

12 tools answering
Contractor License Watch (OR CCB + WA L&I)
by brunckel

Oregon CCB and Washington L&I contractor license status, expiry dates, and changes via Apify.

answering
AI Model Lifecycle Index
by oscarlopez-gif

Cross-vendor AI model lifecycle: status, sunset dates, and migration targets, source-cited.

4 tools answering
Citation Dialogue
by 6forwater29

Explore the active Zotero citation graph and save source-linked Obsidian or Notion research notes.

local only
SourceActs
by sourceacts

Official EUR-Lex, UK, US, and gazette search, metadata fetch, and change-only watches.

answering
Uk Legislation MCP Server
by cyanheads

Search and read UK legislation at any date, resolve citations, list amendments, track changes.

141 installs/wk 6 tools answering
LinkList
by linklist

Search source collections your team vetted. Every passage cites its URL and fetch date.

answering
PageWatch - page-to-data extraction and change monitoring
by workers-zenith-ops-pagewatch

Extract prices, lists, tables, events from static pages and watch them for changes.

3 tools answering

tariff.watch — questions

Answers built from our own checks of this server.

What can tariff.watch do?
It exposes 3 tools, read directly from the server on our last check. Among them: tariffs_effective_dates, tariffs_get_source, tariffs_list_changes. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is tariff.watch working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 92 checks got a reply (0.0%), average response time 31 ms. The bar chart above shows every period we have measured.
Did tariff.watch ever remove tools?
Yes. exec, run_code are no longer exposed — we recorded the date each one disappeared. A tool vanishing usually means a breaking change for anything that depended on it.
The registry lists tariff.watch as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect tariff.watch?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does tariff.watch need an API key?
No. tariff.watch completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.