mcpbeat

tariff.watch MCP Server

io.github.Jaketdaniels/tariff-watch
answering

tariff.watch is answering right now. Last checked 6 min ago. It exposes 2 tools.

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

Uptime history 40 hours of history
40 hours agonow
100.0%
Uptime 24h
91 of 91 checks
2
Tools
read from the server
978 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

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

run in your terminal
claude mcp add tariff-watch --transport http https://tariff.watch/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "tariff-watch": {
      "url": "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
{
  "mcpServers": {
    "tariff-watch": {
      "url": "https://tariff.watch/mcp"
    }
  }
}

Available tools 2

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

code
run_code
Execute code in a persistent sandbox interpreter and return output. Defaults to Python.
exec
exec
Run a shell command in the sandbox and return stdout/stderr and exit code.

Endpoints

URLTransportStateLatencyChecked
https://tariff.watch/mcp streamable-http answering 1042 ms 6 min ago

tariff.watch — questions

Answers built from our own checks of this server.

What can tariff.watch do?
It exposes 2 tools, read directly from the server on our last check. Among them: exec, run_code. 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 91 of 91 checks got a reply (100.0%), average response time 978 ms. The bar chart above shows every period we have measured.
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 with the file path 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 2 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is tariff.watch?
It answers our handshake in 978 ms on average, which is faster than 5% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.