_ registry / mcp streamable-http · checked 18h ago

PixHarvest Tariff Data

https://pixharvest.com

Registry code: 6c1c8bccb159240a

api record

PixHarvest Tariff Data provides live US import tariff intelligence: base MFN rates, stacked 2026 Section 301 China-origin rates, EU rates, MPF/HMF fees and landed-cost estimates by HS code or product keyword. Call tariff.lookup first for any tariff question — it resolves HS codes and product keywords to exact rates with a landed-cost example. If the query is ambiguous, tariff.lookup returns the closest matches so you can refine. Use tariff.export when you need the raw sample schedule (first 300 rows) for offline analysis instead of a single-rate answer. Full 4,000+ page schedule and API…

endpoint
https://pixharvest.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is PixHarvest Tariff Data live?
Yes — it answered the hub's last check (checked 18h ago). It answered 100% of checks over the last 30 days.
Is PixHarvest Tariff Data free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does PixHarvest Tariff Data have?
4 tools: tariff.export, tariff.lookup, tariff.batch, tariff.full.
Is PixHarvest Tariff Data safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
184ms

last good check

priced tools
1

of 4 tools

_ answered our checks, 90 days 88 checks · signed record
  • unknown → live
_ what it is for
used for
  • look up us import tariff rates by hs code
  • estimate landed cost of an import
  • export sample tariff schedule
takes → gives
text → text, data
tools
2 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
1 paid2 open 1 never probed 3 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • tariff.full 49 USDC paid 39d ago

    PAID (USDC $49 one-time via x402 HTTP 402 Payment Required, Base network). Unlock the FULL tariff schedule for a product or HS code: all origin countries, Section 232 and stacked totals, instead of the free 3-row sample. If your client supports x402 it will receive an HTTP 402 with a PAYMENT-REQUIRED header, sign the exact payment and retry automatically. Call tariff.lookup first to see the free sample.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "description": "HS code (e.g. '8703.24') or product keyword (e.g. 'aluminum profile', '笔记本电脑')."
        }
      }
    }
    arguments 12 lines
  • tariff.lookup reads open 39d ago

    Look up live US import tariff rates by HS code, product keyword or Chinese product name (e.g. 8703.24, laptop, steel pipe, 笔记本电脑, 运动相机, aluminum profile from vn). Returns base MFN rate, Forced-labor security layer, Section 301 (China), Section 232 (steel/aluminum), stacked total and origin country, daily-updated, with Chinese labels (productZh). Call this first for any tariff question.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "description": "HS code (e.g. '8703.24') or product keyword (e.g. 'laptop', 'steel pipe'). Free-text is fine; being specific improves precision. Example: '8703.24'."
        }
      }
    }
    arguments 12 lines
  • tariff.batch open 39d ago

    Look up US tariff rates for multiple HS codes or product keywords in one call. Accepts comma-separated or space-separated inputs (e.g. '8703.24 8471.30 laptop') and returns each match with stacked 2026 rates plus Chinese labels. Use when comparing landed cost across several products.

    mcp-tool

    {
      "type": "object",
      "required": [
        "queries"
      ],
      "properties": {
        "queries": {
          "type": "string",
          "description": "Comma- or space-separated HS codes / product keywords, e.g. '8703.24, 8471.30, laptop, steel pipe'. Max 10 items."
        }
      }
    }
    arguments 12 lines
  • tariff.export reads unknown never probed

    Return the sample US tariff schedule as plain text (first 300 rows) for offline analysis or filtering. Call after tariff.lookup when you need the raw schedule rather than a single-rate answer.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 6c1c8bccb159240a.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/6c1c8bccb159240a/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/6c1c8bccb159240a/badge.svg)](https://brick.blue/agent/6c1c8bccb159240a?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on pixharvest.com 2 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.