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

standard-trade-trade-evidence

https://standardtrade.ai

Registry code: ac7c091f2c3dc790

api record

Standard Trade's Trade Evidence: all 36,524 exhibitors and 200,204 product listings at the 140th Canton Fair (Guangzhou, October 2026), from the fair's public exhibitor profiles (collected October 8 to 15, 2026), plus a US import checklist per product type. Company type, certificates, staff and export facts are what each exhibitor says about itself. Cite an exhibitor by name and booth and link its fair_profile. Exhibitor refs (E1234) from one tool work in get_exhibitors and check_fit. Each invite code has 15 searches across search_listings, get_exhibitors and check_fit; us_requirements and…

endpoint
https://standardtrade.ai/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 standard-trade-trade-evidence live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is standard-trade-trade-evidence free to use?
Yes — the hub reached it with no key and no payment.
What tools does standard-trade-trade-evidence have?
5 tools: search_listings, price_bands, us_requirements, check_fit, get_exhibitors.
Is standard-trade-trade-evidence 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
202ms

last good check

priced tools
0

of 5 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

inferred, not observed

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

_ what it can do 5 tools
5 never probed 0 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.

  • search_listings unknown never probed

    Search exhibitors' product listings and profiles across the whole fair. Returns totals and the best-matching exhibitors with their matching listings. Use product words only (e.g. 'bamboo cutting board'). Optional filters apply to the exhibitors returned. Spends one search.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "type": {
          "enum": [
            "manufacturer",
            "trader"
          ],
          "type": "string"
        },
        "limit": {
          "type": "integer",
          "maximum": 10,
          "minimum": 1
        },
        "phase": {
          "enum": [
            "1",
            "2",
            "3"
          ],
          "type": "string",
          "description": "Fair phase"
        },
        "query": {
          "type": "string",
          "description": "Product words only"
        },
        "certificate": {
          "type": "string",
          "description": "A certificate the exhibitor must list, e.g. BSCI, FDA, LFGB, UL/ETL, OEKO-TEX, FSC"
        }
      }
    }
    arguments 37 lines
  • price_bands unknown 2h ago

    Going prices for a product: median, middle half and median MOQ across all priced listings in matching fair categories, with the US import duty where known. Free; does not spend a search.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string"
        }
      }
    }
    arguments 11 lines
  • us_requirements unknown never probed

    What a US seller must check before importing and selling a product: laws, marketplace (Amazon) rules and common buyer requests, each with its source and the certificate or test report a factory can show. Free; does not spend a search.

    mcp-tool

    {
      "type": "object",
      "required": [
        "product"
      ],
      "properties": {
        "product": {
          "type": "string"
        }
      }
    }
    arguments 11 lines
  • check_fit unknown 2h ago

    Who lists the paperwork each US rule for a product asks for. Checks every exhibitor selling the product (counts per rule), plus up to 10 named exhibitors and the others that list the most, in detail: which list a matching certificate, which only claim it in a product listing, which have only a foreign mark or a lab name; and which rules are the importer's own job. Spends one search.

    mcp-tool

    {
      "type": "object",
      "required": [
        "product"
      ],
      "properties": {
        "refs": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "maxItems": 10,
          "description": "Exhibitor refs (E1234) from search_listings to check in detail. Leave out to check the ones that list the most."
        },
        "product": {
          "type": "string",
          "description": "Product words, e.g. 'bamboo cutting board'"
        }
      }
    }
    arguments 20 lines
  • get_exhibitors unknown 2h ago

    Full profiles for up to 5 exhibitors by ref (E1234): booths, self-declared type, founding year, certificates, staff, export markets, payment terms, and listings with prices and MOQs. Spends one search.

    mcp-tool

    {
      "type": "object",
      "required": [
        "refs"
      ],
      "properties": {
        "refs": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "maxItems": 5
        }
      }
    }
    arguments 15 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 ac7c091f2c3dc790.

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