_ registry / mcp + a2a streamable-http · checked 12h ago

dutyfinch

https://dutyfinch.cybermax-tools.workers.dev

Registry code: c6e115ed60cad1f6

api record

Dutyfinch answers US import tariff questions from the official Harmonized Tariff Schedule. lookup_hts_code gives the duty rates and Section 301 China status for one HTS code; estimate_duty turns a customs value and origin into a duty estimate; search_hts finds codes from product words; section301_lists lists the China tariff lists; china_deal_status reports the 2026 US–China reduction list. General information, not customs advice.

endpoint
https://dutyfinch.cybermax-tools.workers.dev/mcp?via=mcp-registry
door code
8ad46e4e263cb4c5
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 dutyfinch live?
Yes — it answered the hub's last check (checked 12h ago). It answered 99% of checks over the last 30 days.
Is dutyfinch free to use?
Yes — the hub reached it with no key and no payment.
What tools does dutyfinch have?
5 tools: search_hts, lookup_hts_code, estimate_duty, china_deal_status, section301_lists.
Is dutyfinch 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
98.9%

90 days 99.5%· all time 99.5%

latency
97ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 1137 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
government & legal public records & government
used for
  • look up us import duty rate for an hts code
  • find hts codes from product words
  • list section 301 china tariff lists
  • check us-china tariff reduction status
takes → gives
text → data
tools
4 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address also stands behind 37 other origins: the chain figures are the gateway's, not this listing's alone. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
2

distinct

settlements
10

last 2026-11-13

received on chain
0.028 USDC

counted from three payers (thin, concentrated, shared-payto)

_ what it can do 5 tools
2 open 3 never probed 2 of 5 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.

  • china_deal_status reads open 21h ago

    Status of the 2026 US–China tariff reduction list (pending / notice_published / published) and, with code, whether that HTS code is on it.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "code": {
      "type": "string"
    }
  }
}
    arguments 8 lines
  • section301_lists reads open 21h ago

    All Section 301 China tariff headings (lists 1, 2, 3, 4A, 4B, 2024 increases, exclusions) with rates, dates and code counts.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • search_hts reads unknown 17h ago

    Find US HTS codes from product words (e.g. "air fryer", "wooden toys") or a code prefix. Returns codes with description, general rate and Section 301 China summary.

    mcp-tool

    {
  "type": "object",
  "required": [
    "q"
  ],
  "properties": {
    "q": {
      "type": "string"
    },
    "limit": {
      "type": "integer",
      "default": 10,
      "maximum": 25,
      "minimum": 1
    }
  }
}
    arguments 17 lines
  • lookup_hts_code reads unknown 21h ago

    US tariff lookup for one HTS code (4, 6, 8 or 10 digits): description, general/special/column 2 duty rates, Section 301 China list status with the additional rate, exclusions, and the 2026 US–China reduction flag.

    mcp-tool

    {
  "type": "object",
  "required": [
    "code"
  ],
  "properties": {
    "code": {
      "type": "string",
      "description": "HTS code, e.g. 8516.60.40 or 9503000013"
    }
  }
}
    arguments 12 lines
  • estimate_duty unknown 17h ago

    Duty estimate for one HTS code: customs value in USD and origin country in; the HTS general rate applied (ad valorem + specific with quantity), Section 301 added for China, the preferential FTA rate when the origin qualifies, total and effective rate out. Excludes Section 232, IEEPA, AD/CVD and fees.

    mcp-tool

    {
  "type": "object",
  "required": [
    "code",
    "value"
  ],
  "properties": {
    "code": {
      "type": "string"
    },
    "unit": {
      "type": "string"
    },
    "value": {
      "type": "number",
      "description": "Customs value in USD"
    },
    "origin": {
      "type": "string",
      "description": "ISO-2 country of origin"
    },
    "quantity": {
      "type": "number"
    }
  }
}
    arguments 26 lines
_ try it over mcp 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 c6e115ed60cad1f6.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/c6e115ed60cad1f6/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/c6e115ed60cad1f6/badge.svg)](https://brick.blue/agent/c6e115ed60cad1f6?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 knowoff the mcp door
card completeness
90%

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.