customs-bridge
Registry code: 31057810d3fe147e
Deterministic HS6/TARIC customs resolution engine and bilingual FTS5 nomenclature API (UNE Node 04).
from a public catalogue that lists it, not from the operator
- endpoint
- https://customs.une.education/mcp.php
- protocol
- streamable-http ·2024-11-05
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is customs-bridge live?
- Yes — it answered the hub's last check (checked 4h ago). It answered 99% of checks over the last 30 days.
- Is customs-bridge free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does customs-bridge have?
- 6 tools: provision_free_api_key, resolve_hs_code, calculate_customs_duties, check_import_restrictions, resolve_cbam_and_antidumping, search_customs_nomenclature.
- Is customs-bridge 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.
90 days 99%· all time 99%
last good check
of 6 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- degraded → live
- live → degraded· timeout after 20000ms
- used for
- resolve an hs or taric customs code
- search eu customs nomenclature
- takes → gives
- text → data
- tools
- 2 reads
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.
through this hub
successful
what callers paid
Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run
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.
provision_free_api_key unknown never probed
Provisions a free sandbox API key (50 credits) for agents to unlock advanced CBAM carbon calculations and factory-specific anti-dumping duty codes.
{ "type": "object", "required": [ "developer_email" ], "properties": { "use_case": { "type": "string", "description": "Brief description of the intended usage" }, "developer_email": { "type": "string", "description": "Business or developer email address" } } }arguments 16 linesresolve_hs_code reads unknown never probed
Resout l arborescence hierarchique et la designation officielle d un code SH6 ou TARIC.
{ "type": "object", "properties": { "code": { "type": "string", "description": "Alias pour hs_code" }, "hs_code": { "type": "string", "description": "Code SH ou TARIC" } } }arguments 13 linescalculate_customs_duties unknown never probed
Calculates official EU customs duties (Common Customs Tariff / MFN) and import VAT for a given HS code and CIF customs value in EUR.
{ "type": "object", "required": [ "hs_code", "customs_value_eur" ], "properties": { "hs_code": { "type": "string", "description": "HS or TARIC code (e.g. 760421, 640411)" }, "origin_country": { "type": "string", "description": "ISO-2 origin country code (default: CN)" }, "customs_value_eur": { "type": "number", "description": "CIF customs value in EUR" } } }arguments 21 linescheck_import_restrictions unknown never probed
Checks mandatory EU import restrictions, document codes (CE, REACH, CBAM, CHED), and compliance directives.
{ "type": "object", "required": [ "taric_code" ], "properties": { "taric_code": { "type": "string", "description": "HS or TARIC code" }, "origin_country": { "type": "string", "description": "ISO-2 country code (default: CN)" } } }arguments 16 linesresolve_cbam_and_antidumping unknown never probed
Computes definitive EU anti-dumping duties and CBAM carbon financial obligations for steel, aluminium, and sensitive imports.
{ "type": "object", "required": [ "hs_code", "cif_value_eur" ], "properties": { "api_key": { "type": "string", "description": "UNE Developer or Enterprise API Key" }, "hs_code": { "type": "string", "description": "HS or TARIC code (e.g. 7604, 7318, 7208)" }, "weight_kg": { "type": "number", "description": "Net mass in kilograms (aliases: weight_net_kg, mass_kg)" }, "cif_value_eur": { "type": "number", "description": "CIF customs value in EUR" }, "origin_country": { "type": "string", "description": "ISO-2 origin country code (default: CN)" } } }arguments 29 linessearch_customs_nomenclature reads unknown 4h ago
Recherche textuelle bilingue (FR/EN) dans la nomenclature TARIC via indexation FTS5.
{ "type": "object", "required": [ "query" ], "properties": { "lang": { "enum": [ "fr", "en" ], "type": "string", "default": "fr" }, "limit": { "type": "integer", "default": 5 }, "query": { "type": "string", "description": "Terme de recherche" } } }arguments 24 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id31057810d3fe147e.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/31057810d3fe147e/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/31057810d3fe147e?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.
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.
- maritime.une.education maritime-gateway
- legal.une.education sino-gateway
- standards.une.education sino-industrial-compliance-mcp