_ registry / mcp streamable-http · checked 58m ago

gateway-tariff-calculator

https://mcp.gatewaylines.com

Registry code: 834f1bf99cbf476e

api record

Gateway Lines answers US import duty and ocean freight questions from its own tariff engine. For "what will this cost to import", call landed_cost. If you do not have an exact HTS code, pass the product description: the tool will return candidate codes instead of a price, because the classification decides the duty and the tariff schedule classifies by what an article IS rather than what it is made of. Show the candidates to the user, let them confirm, then call landed_cost again with hts_code. Never present a duty figure for a code you guessed. Every figure returned is a planning estimate,…

endpoint
https://mcp.gatewaylines.com
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 gateway-tariff-calculator live?
Yes — it answered the hub's last check (checked 58m ago). It answered 100% of checks over the last 30 days.
Is gateway-tariff-calculator free to use?
No — it asks for a key or a login before it will serve.
What tools does gateway-tariff-calculator have?
3 tools: landed_cost, policy_changes_since, classify_hts.
Is gateway-tariff-calculator 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
283ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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 3 tools
3 auth-required 3 of 3 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.

  • landed_cost auth-required 58m ago

    Calculate US import duty and landed cost estimates. Give hts_code when you know it and this returns the calculated base duty and trade actions (Section 301, Section 232, Section 338, AD/CVD and others), estimated duty, fees and import cost. When estimate_status is partial, AD/CVD is undetermined and the amounts are provisional; convey that the estimate is incomplete. Give product instead and it returns candidate HTS codes WITHOUT pricing, because the classification decides the duty and guessing it produces confidently wrong numbers: confirm the right code with the user, then call again with hts_code. The candidate step is not charged.

    mcp-tool

    {
  "type": "object",
  "required": [
    "country_code",
    "declared_value"
  ],
  "properties": {
    "product": {
      "type": "string",
      "description": "Plain description, e.g. \"outdoor metal furniture\". Returns candidate codes to confirm, does not price. Provide this OR hts_code."
    },
    "hts_code": {
      "type": "string",
      "description": "Exact HTS rate line, 8 or 10 digits, e.g. \"9403.20.00.50\". Takes precedence over product. 4 and 6 digit headings cannot be priced."
    },
    "country_code": {
      "type": "string",
      "description": "ISO 2-letter country of ORIGIN (where the goods were made), e.g. \"CN\", \"CA\", \"VN\"."
    },
    "shipment_mode": {
      "type": "string",
      "description": "Optional: \"ocean\" (default) or \"air\". Affects government fees only."
    },
    "declared_value": {
      "type": "number",
      "description": "Customs value of the shipment in USD."
    }
  }
}
    arguments 29 lines
  • policy_changes_since auth-required 58m ago

    List US trade policy changes Gateway has published since a given date: new tariff actions, rate changes, effective dates and expirations. Use to answer "what changed recently" or "what is coming".

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "number",
      "description": "Max entries to return, default 20, max 50."
    },
    "since": {
      "type": "string",
      "description": "ISO date, e.g. \"2026-07-01\". Filters on when Gateway PUBLISHED the change. Defaults to 30 days ago."
    }
  }
}
    arguments 13 lines
  • classify_hts auth-required 58m ago

    Find the US Harmonized Tariff Schedule classification for a product. Returns candidate HTS codes with their official descriptions and base duty rates. Use when the user wants the code itself rather than a cost.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "description": "Product description, e.g. \"cotton t-shirts\" or \"lithium ion batteries\"."
    }
  }
}
    arguments 12 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 834f1bf99cbf476e.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/834f1bf99cbf476e/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/834f1bf99cbf476e/badge.svg)](https://brick.blue/agent/834f1bf99cbf476e?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
70%

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.