Record source

Official MCP registry

The named source does not confirm ownership or quality.

Open source data

Technical Score

Not enough data to calculate

Coverage 45% · technical-v2.0

How the score is calculated

User Rating

There are no published reviews yet

Published reviews are not mixed with technical observations.

Go to reviews

Latest endpoint observation

The endpoint response needs another check

The status applies only to the checked endpoint, not the whole service.

Open history

About this service

What it does

Technical interface from trimtabist.com. Check the source for its exact purpose.

Task category

Agent infrastructure

Named provider

trimtabist.com

How to connect

MCP, API

Protocols: mcp

User reviews

There are no published reviews yet

New reviews are not being accepted yet.

Technical observation history

Recent endpoint checks

The last three checks failed9 Aug 2026, 10:00 UTCHTTP 404 · 1154 ms
The last three checks failed9 Aug 2026, 09:09 UTCHTTP 404 · 889 ms

Problems in the observation history

There are no problems in the available history.

Endpoints and technical capabilities

Each observation applies to a specific endpoint.

https://trimtabist.com/mcpOpens in a new tabEndpoint type: Remote endpoint · Transport: streamable-http
The endpoint response needs another checkLatest observation: 9 Aug 2026, 10:00 UTC · 1154 ms

Access methods: MCP, API
Protocols: mcp
Version: 0.3.1
Technical record name: com.trimtabist/us-tariff-ledger

Source data

This data comes from the named source. It is not proof of ownership or an independent quality assessment.

Original description

US tariff & trade truth: duty actually paid by origin/HS 2017+, HTS rulebook, CBP rulings. No key.

Open the named source record

Record source: Official MCP registry
Source updated: 9 Aug 2026, 09:05 UTC
Ownership status: Owner not confirmed
Source identifier: mcp_registry
Repository: https://github.com/mrsingh86/trimtab-aisOpens in a new tab

Corrections and future affiliation verification

A public record can be corrected through support without hiding its source or observation history. Affiliation verification and a formal dispute flow have not launched yet.

Report an error How service affiliation will be verified Contact support about a disputed record

Snapshot received: 9 Aug 2026, 19:09 UTC.