What is the key difference between Tnl and Tariff.watch?

Tnl belongs to the Legal category with local stdio execution, while Tariff.watch belongs to the Legal category with cloud HTTP/SSE execution.

How do I install Tnl or Tariff.watch in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Tnl and Tariff.watch free or paid?

Tnl operates under a Free / Open Source model (No auth required). Tariff.watch operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Tnl lists 6 tools with 0 views and 8 GitHub stars. Tariff.watch lists 0 tools with 0 views and 0 GitHub stars.

Can I use both Tnl and Tariff.watch together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

How do I install Tnl or Tariff.watch in Claude Desktop, Cursor, or Windsurf?

Both servers follow the standard Model Context Protocol configuration format. Simply copy the JSON block from the configuration section above and paste it into your AI client's mcpServers configuration object (for instance in claude_desktop_config.json or ~/.cursor/mcp.json ), then completely restart or refresh the application.

Are Tnl and Tariff.watch free to use, or do they require API keys?

Tnl is listed under a Free / Open Source model with No auth required . Tariff.watch operates under a Free / Open Source model with No auth required . If environment variables are required (such as API keys), be sure to define them under the env key in your MCP client's configuration file.

Can I run both Tnl and Tariff.watch at the same time in my AI client?

Yes! MCP clients support multi-server orchestration. You can include both janaraj-tnl and tariff-watch as distinct keys inside the single mcpServers object in your configuration file. Your AI assistant will automatically select and call the appropriate tool from either server during chat sessions.

Which MCP server has higher directory engagement and quality ratings?

On AllMCPs, Tnl has a Quality Score of 52 /100 ( Good ) with 0 views, 0 installs, and 8 GitHub stars. Tariff.watch holds a Quality Score of 42 /100 ( Fair ) with 0 views, 0 installs, and 0 GitHub stars.

Side-by-Side Model Context Protocol Comparison

Tnl vs Tariff.watch

In-depth architectural comparison of the Tnl and Tariff.watch MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Tnl

Legal · Local stdio

Quality: 52/100 (Good) | Auth: No auth required

Tariff.watch

Legal · Remote HTTP/SSE

Quality: 42/100 (Fair) | Auth: No auth required

Verdict Summary: Choose Tnl if you need specialized Legal tools running via a local process. Choose Tariff.watch if your workspace requires Legal integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Tnl when:

You need dedicated capabilities in the Legal domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Structured contract schema with fixed fields (id, scope, paths, behaviors, etc.), Agent-driven proposal and human approval workflow for contract edits, Self-attestation by agents mapping MUST clauses to code or tests.

Explore Tnl Details

Choose Tariff.watch when:

You need dedicated capabilities in the Legal domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore Tariff.watch Details

Feature & Specification Comparison

Specification	Tnl janaraj Legal	T Tariff.watch Legal
Summary	MCP server for TNL (Typed Natural Language): per-feature English contracts for AI coding agents. 6 tools — getimpactedtnls, retrievetnl, trace, proposetnldiff, approvetnldiff, verify — let agents look up relevant contracts, propose contract edits, and verify implementations against them. Drop-in via npx typed-nl init for Claude Code, Codex, Gemini.	Source-linked US tariff and trade-action changes: legal status, effective dates, dated archive.
Category & Scope	Legal

Tools & Capabilities Breakdown

Tnl Tools (6)

Structured contract schema with fixed fields (id, scope, paths, behaviors, etc.)

Agent-driven proposal and human approval workflow for contract edits

Self-attestation by agents mapping MUST clauses to code or tests

Verification tool to check contract validity and test bindings

PreToolUse hook to re-inject contracts during editing to prevent drift

Drop-in integration via npx typed-nl init for supported agents

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Tnl Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "janaraj-tnl": {
      "command": "npx",
      "args": [
        "-y",
        "typed-nl"
      ]
    }
  }
}

Tariff.watch Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "tariff-watch": {
      "url": "https://tariff.watch"
    }
  }
}

Frequently Asked Questions

Tnl is categorized under Legal and uses a local stdio subprocess. In contrast, Tariff.watch belongs to Legal using remote streaming HTTP/SSE transport. Select Tnl when you need capabilities focused on legal and Tariff.watch when you require tools for legal.