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

fortitude21-dangerous-goods

https://fortitude21.com

Registry code: a1e939105b36128e

api record

Fortitude21 publishes two tool sets here. Eight free calculators: UN number to permitted containers, UN mark decoding, IBC inspection dates, the ADR 1,000-point small-load test, bund sizing, jerry can quantities, and EU and UK CBAM costs on imported steel, aluminium and other covered goods. And eight catalogue tools over Fortitude21's own range of jerry cans, pails, tins, drums, spill pallets, closures and handling equipment: search, details, compare, pricing, categories, documents, a requirements check and a quotation request. Results carry `cite` (credit and link) and `publisher`. Any price…

endpoint
https://fortitude21.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 fortitude21-dangerous-goods live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is fortitude21-dangerous-goods free to use?
Yes — the hub reached it with no key and no payment.
What tools does fortitude21-dangerous-goods have?
16 tools: create_quote_request, jerry_can_quantity, un_number_packaging, search_products, cbam_cost, get_product_details, compare_products, check_product_requirements, ….
Is fortitude21-dangerous-goods 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
298ms

last good check

priced tools
0

of 16 tools

_ answered our checks, 90 days 156 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 16 tools
15 open 1 never probed 15 of 16 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.

  • jerry_can_quantity open 13h ago

    Work out how much water or fuel to hold, with a margin, and how many jerry cans and 20 ft containers that takes. Use when: planning an emergency water store, or fuel for a trip, boat, generator or machinery. Instead: un_number_packaging for transport rules. Water (the default): people times days times the scenario's litres a person a day. Rates: relief 15 (Sphere minimum, the default); acute 7.5; protracted 50; survival 3; national advice nl, se and dk 3, no 2.86, fi and de 2; custom takes rate. National scenarios also supply a household of 4 and their own days when those are left out. Fuel (mode=fuel, or set by any fuel input): road and overland work from distance and consumption, and returnTrip=1 adds the way back on overland. marine, agri and generator work from hours and consumption; generator also takes kva and load instead of consumption. Hours or kva with no scenario selects generator. units=us switches to miles, mpg and US gallons. Either mode: volume with no scenario is the amount to hold. reserve sets the margin; by default 10% for water and 0 to 50% by fuel scenario. Behaviour: a missing people, days, distance or hours returns ok:false with needs naming it; no demo figure is substituted. A defaulted consumption, household or period is noted in assumed, and so are unknown arguments. Constraints: no authentication, key or headers. At most 10 requests per 10 seconds per IP address; above that HTTP 429, so space out repeated calls.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "can": {
          "type": "string",
          "description": "Optional product slug of the can to size in, e.g. product-20l-nato-steel-fuel-can. Default: the scenario's usual can"
        },
        "kva": {
          "type": "number",
          "description": "Fuel, generator: rating in kVA, used with load instead of consumption"
        },
        "days": {
          "type": "number",
          "description": "Water: days to cover. Required unless the scenario sets it"
        },
        "load": {
          "type": "number",
          "description": "Fuel, generator: load in per cent, with kva"
        },
        "mode": {
          "enum": [
            "water",
            "fuel"
          ],
          "type": "string",
          "description": "water (default) or fuel. Set to fuel when distance, hours, kva or consumption is given"
        },
        "rate": {
          "type": "number",
          "description": "Water, custom scenario: litres a person a day"
        },
        "hours": {
          "type": "number",
          "description": "Fuel, marine, agri and generator: running hours to cover. Required for those scenarios"
        },
        "units": {
          "enum": [
            "metric",
            "us"
          ],
          "type": "string",
          "description": "metric (default) or us for miles, mpg and US gallons"
        },
        "weeks": {
          "type": "number",
          "description": "Weeks to cover, converted to days when days is not given"
        },
        "people": {
          "type": "number",
          "description": "Water: people to supply. Required unless a national scenario sets a household of 4"
        },
        "volume": {
          "type": "number",
          "description": "Litres (US gallons with units=us) to hold. With no scenario it replaces the calculation in either mode"
        },
        "reserve": {
          "type": "number",
          "description": "Margin in per cent added to the base volume"
        },
        "units_n": {
          "type": "number",
          "description": "Fuel: number of vehicles, boats or machines (default 1)"
        },
        "distance": {
          "type": "number",
          "description": "Fuel, road and overland: trip distance in km (miles with units=us). Required for those scenarios"
        },
        "scenario": {
          "type": "string",
          "description": "Water: relief (default), acute, protracted, survival, nl, se, no, fi, dk, de, custom. Fuel: road (default), overland, marine, generator, agri, direct"
        },
        "returnTrip": {
          "enum": [
            "0",
            "1"
          ],
          "type": "string",
          "description": "Fuel, overland: 1 to count the return leg"
        },
        "consumption": {
          "type": "number",
          "description": "Fuel: L/100 km for road and overland, L/h for marine, agri and generator; with units=us, miles per US gallon or US gallons an hour. Defaults noted in assumed"
        }
      }
    }
    arguments 85 lines
  • un_number_packaging open 25h ago

    Find which UN-approved packagings may carry a dangerous liquid under ADR 2025 Table A and its packing instructions. Use when: the user has a UN number from section 14 of a safety data sheet, or a substance name, and asks what it can travel in and how large. Instead: decode_un_packaging_mark to read a mark already on a container; adr_1000_points to test a vehicle load. Inputs: send un or name. If both arrive, un wins and name is not read. name is a case-insensitive substring search over proper shipping names and common names and needs at least 3 characters, so a broad word such as "acid" returns up to 20 candidates to choose from. Where one candidate is the everyday meaning (petrol: UN 1203, paint: UN 1263), that entry is answered and the other matches are listed in assumed. Behaviour: covers 157 liquids for road transport under ADR; sea (IMDG Code) and air (IATA) rules can differ. An uncovered number returns ok:false with covered_un_numbers, and a name with no match returns ok:false asking for the number. A number with several Table A rows (packing groups or variants) returns each as its own entry, so choose by the packing group on the safety data sheet. Unknown arguments are ignored and named in assumed. Constraints: no authentication, key or headers. At most 10 requests per 10 seconds per IP address; above that HTTP 429, so space out repeated calls.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "un": {
          "type": "string",
          "description": "Four digits, with or without a \"UN\" prefix, e.g. \"1203\" or \"UN 1203\""
        },
        "name": {
          "type": "string",
          "description": "Substance name, e.g. \"acetone\""
        }
      }
    }
    arguments 13 lines
  • search_products open 13h ago

    Search the Fortitude21 catalogue of liquid containment: jerry cans, pails, tins, drums, spill pallets, closures and handling equipment in steel, stainless, aluminium, tinplate and UN-rated HDPE. Use when: finding products that fit a need. Then: get_product_details for one record, compare_products for two to six, get_product_pricing for terms, create_quote_request to ask for a price. Inputs: q and every filter combine with AND, so each one narrows the result. q expands synonyms, such as bund for spill pallet, and words no product mentions are named in query.terms_no_product_mentions so they can be dropped. category also takes the exact category name. application matches words in the product's listed uses. certification=UN matches any product with a UN status that is not excluded; a design code must appear in that status. sort defaults to relevance with q and to name without. Behaviour: a product with no recorded value for a filtered attribute is left out rather than assumed to match, so an empty result means nothing meets every condition: drop a filter and search again. An unknown category, pricing_type or sort returns ok:false listing the valid values. Results are summaries; get_product_details has the full record. Constraints: no authentication, key or headers. At most 10 requests per 10 seconds per IP address; above that HTTP 429, so space out repeated calls.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "q": {
          "type": "string",
          "description": "Free text, e.g. \"20 litre steel fuel can\" or \"spill pallet for 4 drums\". Leave out to list by filters alone"
        },
        "page": {
          "type": "integer",
          "description": "Page number, from 1"
        },
        "sort": {
          "enum": [
            "relevance",
            "capacity",
            "capacity_desc",
            "price",
            "name"
          ],
          "type": "string",
          "description": "Order of results. relevance (default) needs q"
        },
        "limit": {
          "type": "integer",
          "description": "Results per page, 1 to 100. Default 20"
        },
        "category": {
          "type": "string",
          "description": "Category slug from get_product_categories, e.g. spill-containment"
        },
        "material": {
          "type": "string",
          "description": "hdpe, polypropylene, polyethylene, stainless, steel, galvanised, aluminium, tinplate, plastic or metal. Resolved to the material family, so hdpe does not return polypropylene"
        },
        "application": {
          "type": "string",
          "description": "Intended use, e.g. \"defence\", \"agriculture\", \"marine\""
        },
        "capacity_max": {
          "type": "number",
          "description": "Maximum capacity in litres"
        },
        "capacity_min": {
          "type": "number",
          "description": "Minimum capacity in litres, e.g. 20"
        },
        "pricing_type": {
          "enum": [
            "PUBLIC_PRICE",
            "STARTING_FROM",
            "PRICE_ON_REQUEST",
            "CONTRACT_PRICE"
          ],
          "type": "string",
          "description": "Filter by pricing model. Most products are PRICE_ON_REQUEST"
        },
        "certification": {
          "type": "string",
          "description": "UN for any UN-rated design, or a design code such as 3H1 or 3A1"
        }
      }
    }
    arguments 62 lines
  • cbam_cost open 11h ago

    Work out the EU CBAM certificates owed on imported goods after the free allocation adjustment, what they cost at the official certificate price, and where the importer stands against the 50-tonne annual threshold, on EU default values. Use when: the user asks what CBAM will cost on cement, fertiliser, iron and steel, aluminium or hydrogen imported into the EU. Instead: uk_cbam_cost for imports into the UK. Inputs: one line per goods and origin. cn is the CN code (4 to 10 digits); words such as "steel tubes" are matched against the official descriptions and return candidates when several fit. origin is an ISO code or an English country name; tonnes is the net mass. period is 2026-Q1 to 2026-Q4 or a year from 2027, defaulting to the current quarter; 2026 prices are quarterly and later ones weekly, so from 2027 the latest published price applies unless price is sent. other_tonnes adds CBAM goods not listed, for the threshold; unit_kg adds the cost per item. Behaviour: summary states the result in one sentence. Under 50 t a year (lines plus other_tonnes) owed is none and the totals show what becomes owed above it. A country without its own default values takes the table for other countries and territories, noted in assumed; origins in the EU, Iceland, Liechtenstein, Norway or Switzerland are refused as outside CBAM. Electricity and verified actual emissions are not covered; an estimate, not a declaration. Constraints: no authentication, key or headers. At most 10 requests per 10 seconds per IP address; above that HTTP 429, so space out repeated calls.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "cn": {
          "type": "string",
          "description": "Single line: CN code or words"
        },
        "path": {
          "enum": [
            "law",
            "proposal"
          ],
          "type": "string",
          "description": "law (default): the free allocation phase-out in force. proposal: COM(2026) 616, not law"
        },
        "lines": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "cn",
              "origin",
              "tonnes"
            ],
            "properties": {
              "cn": {
                "type": "string",
                "description": "CN code, e.g. \"7310\" or \"73102990\", or words describing the goods"
              },
              "origin": {
                "type": "string",
                "description": "Country of origin: ISO code such as \"CN\" or a name such as \"Viet Nam\""
              },
              "tonnes": {
                "type": "number",
                "description": "Net mass in tonnes"
              }
            }
          },
          "description": "One item per goods and origin. Or send cn, origin and tonnes for a single line"
        },
        "price": {
          "type": "number",
          "description": "Certificate price in EUR, to override the published price"
        },
        "origin": {
          "type": "string",
          "description": "Single line: country of origin"
        },
        "period": {
          "type": "string",
          "description": "Quarter of import for 2026, e.g. \"2026-Q3\", or a year from 2027, e.g. \"2027\". Default: the current quarter"
        },
        "tonnes": {
          "type": "number",
          "description": "Single line: net mass in tonnes"
        },
        "unit_kg": {
          "type": "number",
          "description": "Net mass of one item in kg, e.g. 3.1 for a 20 L steel jerry can, for the cost per item"
        },
        "compare_with": {
          "type": "string",
          "description": "Optional second country of origin: the same lines made there, returned as comparison and never added to the totals"
        },
        "other_tonnes": {
          "type": "number",
          "description": "Other CBAM goods (cement, fertiliser, iron and steel, aluminium) imported this year, tonnes, for the 50 t threshold"
        }
      }
    }
    arguments 71 lines
  • get_product_details open 6h ago

    Get the complete published record for one Fortitude21 product. Use when: the user needs the specifications, sizes, part numbers or images of one product, usually after search_products. Instead: get_product_pricing for commercial terms; get_product_documents for certificates; check_product_requirements for what a quotation still needs. Inputs: sku takes the product slug, with or without its product- prefix, the product part number, or the part number of one size, which returns the whole product that size belongs to. Letter case is ignored. Returns: product with identity, typed specifications and the source of each figure, the spec table, orderable units with their part numbers, size and model tables, images, documents available on request and pricing. Behaviour: a figure the factory has not supplied comes back as available on request, never left out, so an absent value is not read as zero. Any price in the record is indicative, never a quotation. An unknown sku returns ok:false with example ids and a search link. Constraints: no authentication, key or headers. At most 10 requests per 10 seconds per IP address; above that HTTP 429, so space out repeated calls.

    mcp-tool

    {
      "type": "object",
      "required": [
        "sku"
      ],
      "properties": {
        "sku": {
          "type": "string",
          "description": "An F21 part number such as F21-NF-20, or a product slug such as product-20l-nato-steel-fuel-can. Both come from search_products results"
        }
      }
    }
    arguments 12 lines
  • compare_products open 6h ago

    Compare two to six Fortitude21 products on the attributes they publish. Use when: the user is choosing between products already found with search_products. Instead: get_product_details for one product in full. Inputs: each entry in skus may be a slug, a product part number or the part number of one size, mixed freely; a size stands for its whole product. Products come back in the order given. Behaviour: rows every product has a value for go in comparable; rows some products lack go in partial, naming them, so a blank is never read as a worse figure. It does not rank or recommend: which product suits depends on the contents, the destination market and the order. Fewer than two skus or more than six returns ok:false, and an unknown one returns ok:false with not_found. Constraints: no authentication, key or headers. At most 10 requests per 10 seconds per IP address; above that HTTP 429, so space out repeated calls.

    mcp-tool

    {
      "type": "object",
      "required": [
        "skus"
      ],
      "properties": {
        "skus": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "maxItems": 6,
          "minItems": 2,
          "description": "Two to six F21 part numbers or product slugs, from search_products"
        }
      }
    }
    arguments 17 lines
  • check_product_requirements open 18h ago

    Report what Fortitude21 publishes about one product's certification: the exact scope of any UN status, its cautions, the documents that exist and what a quotation still needs. Use when: about to quote or ship a specific product. Instead: un_number_packaging, adr_1000_points, bund_size or decode_un_packaging_mark for the regulations themselves; the response names them. Inputs: only sku is required, read as in get_product_details. destination_market and intended_contents only shorten information_still_needed, since each one left out is listed there; neither is checked against any rule. To learn whether the contents are dangerous goods, call un_number_packaging with their UN number. Behaviour: it states what the publisher says, not what a market requires, and does not confirm that Fortitude21 holds a certificate: UN approval is granted per design type and plant. An unknown sku returns ok:false. Constraints: no authentication, key or headers. At most 10 requests per 10 seconds per IP address; above that HTTP 429, so space out repeated calls.

    mcp-tool

    {
      "type": "object",
      "required": [
        "sku"
      ],
      "properties": {
        "sku": {
          "type": "string",
          "description": "An F21 part number or product slug, from search_products"
        },
        "intended_contents": {
          "type": "string",
          "description": "What the container will hold, ideally with its UN number, e.g. \"diesel, UN 1202\""
        },
        "destination_market": {
          "type": "string",
          "description": "Country or market the goods are going to, e.g. \"Australia\""
        }
      }
    }
    arguments 20 lines
  • get_product_documents open 18h ago

    List which documents exist for one Fortitude21 product and how to request them. Use when: the user asks for a certificate, test report, mill certificate, food-contact declaration, specification sheet or drawing. Instead: check_product_requirements for the scope of a UN status and what a quotation needs; get_product_details for specifications. Inputs: sku is read as in get_product_details; the part number of one size returns the documents for its whole product. Behaviour: it requests nothing itself; following request_url is the buyer's step. hosted is usually empty, because documents are issued against a specific design and production run. Each document says when it applies: a UN certificate only where the design carries one, a mill certificate for a stainless grade, a food-contact declaration where the product is specified for food or drinking water. An unknown sku returns ok:false with example ids. Constraints: no authentication, key or headers. At most 10 requests per 10 seconds per IP address; above that HTTP 429, so space out repeated calls.

    mcp-tool

    {
      "type": "object",
      "required": [
        "sku"
      ],
      "properties": {
        "sku": {
          "type": "string",
          "description": "An F21 part number or product slug, from search_products"
        }
      }
    }
    arguments 12 lines
  • get_product_categories open 13h ago

    List the twelve Fortitude21 product categories with their slugs, taglines and product counts, in two families. Use when: you need a category slug for search_products, or want to show the user the range. Instead: search_products to list the products themselves. Inputs: family limits the list to one family; any other value returns ok:false with valid_families. Behaviour: the list changes only when the catalogue does. Each product has one home category and may be cross-listed into others, so listed_count can exceed product_count. Constraints: no authentication, key or headers. At most 10 requests per 10 seconds per IP address; above that HTTP 429, so space out repeated calls.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "family": {
          "enum": [
            "container",
            "system"
          ],
          "type": "string",
          "description": "Optional. container: cans, pails, tins and drums. system: spill containment, closures, pouring and handling. Leave out for all twelve categories"
        }
      }
    }
    arguments 13 lines
  • get_product_pricing open 11h ago

    Get the published commercial terms for one Fortitude21 product: pricing type, currency, minimum order, quantity bands with any approved indicative unit price, validity, Incoterms and lead time. Use when: the user asks about price, minimum order or lead time for a known product. Instead: create_quote_request for an actual quotation; search_products with pricing_type to find products by pricing model. Inputs: sku is read as in get_product_details. Without quantity it returns every band. With quantity it also returns the band that covers it; below the minimum order no unit price is given and assumed says so; a quantity in the top band returns a quotation band rather than a price. A quantity under 1 returns ok:false. Behaviour: any price is indicative, never a quotation: binding is always false, and prices exclude freight, duty and taxes. Products priced on request return no number. An unknown sku returns ok:false with example ids. Constraints: no authentication, key or headers. At most 10 requests per 10 seconds per IP address; above that HTTP 429, so space out repeated calls.

    mcp-tool

    {
      "type": "object",
      "required": [
        "sku"
      ],
      "properties": {
        "sku": {
          "type": "string",
          "description": "An F21 part number or product slug, from search_products"
        },
        "quantity": {
          "type": "integer",
          "description": "Optional units to price, e.g. 500. Returns the band that covers it in band and for_quantity"
        }
      }
    }
    arguments 16 lines
  • bund_size open 25h ago

    Work out the minimum sump capacity for a bund or spill pallet under the containment rule where the containers are stored, and name the rule. Use when: sizing a spill pallet, bund or drip tray. Instead: ibc_inspection_dates for IBC tests; un_number_packaging for container approval. Inputs: count only the containers stored together over one bund; size separate stores in separate calls. Give at least one count: drums, ibcs, small and other add up, and small and other each need their size. liquid and mode=tray can change which rule applies. With no region the rule for England is used; a country without its own rule gets the common 110% and 25% rule; both are noted in assumed. Behaviour: the rule comes labelled as law, code, guidance or practice, so say which when advising. A region it cannot read returns ok:false with the 16 region codes, and a count without its size returns ok:false naming the size. Unknown arguments are ignored and named in assumed. Constraints: no authentication, key or headers. At most 10 requests per 10 seconds per IP address; above that HTTP 429, so space out repeated calls.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "ibcs": {
          "type": "integer",
          "description": "Number of 1,000-litre IBCs"
        },
        "mode": {
          "enum": [
            "bund",
            "tray"
          ],
          "type": "string",
          "description": "bund (default) for a bund or spill pallet, tray for a drip tray"
        },
        "drums": {
          "type": "integer",
          "description": "Number of 205-litre drums"
        },
        "other": {
          "type": "integer",
          "description": "Number of other containers; needs otherSize"
        },
        "small": {
          "type": "integer",
          "description": "Number of smaller containers; needs smallSize"
        },
        "liquid": {
          "type": "string",
          "description": "oil (fuel, diesel, petrol; the default), flam (flammable liquids), other (chemicals), or waste (US only)"
        },
        "region": {
          "type": "string",
          "description": "A region code (gb-eng, gb-wls, gb-sct, gb-nir, ie, de, fr, nl, es, us, ca, au, nz, sg, jp, world), a country name or a US state such as \"Texas\""
        },
        "otherSize": {
          "type": "number",
          "description": "Litres in each other container, e.g. 500"
        },
        "smallSize": {
          "type": "number",
          "description": "Litres in each smaller container, e.g. 25"
        }
      }
    }
    arguments 45 lines
  • uk_cbam_cost open 11h ago

    Work out the UK CBAM liability in pounds on goods imported from 1 January 2027: tonnes times the UK default embedded emissions for the commodity code times the CBAM rate for the sector, with the £50,000 threshold and, if an origin is sent, the EU CBAM cost of the same goods in 2027 for comparison. Use when: the user asks about UK CBAM on aluminium, cement, fertiliser, hydrogen, or iron and steel goods. Instead: cbam_cost for imports into the EU. Inputs: one line per commodity code: code (8 digits; a shorter code or words return candidates) and tonnes. value_gbp, the customs value of all CBAM goods over the last 12 months, tests the threshold. origin adds the EU comparison for that country. Behaviour: summary states the result in one sentence. The UK sets one default per code for every origin. Until HMRC publishes the first quarterly rates, the rates are the illustrative ones GOV.UK published on 16 October 2026, shown in rate_basis and noted in assumed. Imports before the threshold trigger date owe nothing. Default values only; an estimate, not a return. Constraints: no authentication, key or headers. At most 10 requests per 10 seconds per IP address; above that HTTP 429, so space out repeated calls.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "code": {
          "type": "string",
          "description": "Single line: commodity code or words"
        },
        "lines": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "code",
              "tonnes"
            ],
            "properties": {
              "code": {
                "type": "string",
                "description": "UK commodity code, e.g. \"73102990\", or words describing the goods"
              },
              "tonnes": {
                "type": "number",
                "description": "Net mass in tonnes"
              }
            }
          },
          "description": "One item per commodity code. Or send code and tonnes for a single line"
        },
        "origin": {
          "type": "string",
          "description": "Optional country of origin, e.g. \"CN\", to add the EU CBAM cost of the same goods in 2027"
        },
        "tonnes": {
          "type": "number",
          "description": "Single line: net mass in tonnes"
        },
        "unit_kg": {
          "type": "number",
          "description": "Net mass of one item in kg, for the liability per item"
        },
        "value_gbp": {
          "type": "number",
          "description": "Customs value of all CBAM goods imported over the last 12 months, GBP, for the £50,000 threshold"
        }
      }
    }
    arguments 46 lines
  • ibc_inspection_dates open 25h ago

    Work out when an IBC (intermediate bulk container) is due for its leakproofness test and its 2.5-year and 5-year inspections, the last month it may be filled and, for plastic and composite IBCs, the end of its five-year life. Use when: the user asks whether an IBC is in date or may still be filled. Instead: decode_un_packaging_mark to read the rest of an IBC mark; bund_size to size spill containment under IBCs. Inputs: mark alone is enough, since the code and month of manufacture are read from it. Otherwise send made, plus code if known; without code a composite 31HA1 tote is assumed. leak and insp move the due dates on from the last test; without them every date counts from manufacture. bottle restarts the five-year life of a remanufactured composite. A full date is read only when its day cannot be mistaken for the month. regime=us has no five-year life. Behaviour: dates are judged against the current month, so the same IBC moves from ok to soon to overdue as time passes. Every default is listed in assumed; an unreadable date or code returns ok:false. Constraints: no authentication, key or headers. At most 10 requests per 10 seconds per IP address; above that HTTP 429, so space out repeated calls.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "code": {
          "type": "string",
          "description": "IBC code when no mark is given, e.g. 31HA1 (composite), 31H1 (rigid plastic), 31A (steel)"
        },
        "insp": {
          "type": "string",
          "description": "Month of the last inspection, same formats. Usually the same month as leak"
        },
        "leak": {
          "type": "string",
          "description": "Month of the last leakproofness test, same formats"
        },
        "made": {
          "type": "string",
          "description": "Month of manufacture, e.g. \"03/2022\", \"2022-03\" or \"March 2022\""
        },
        "mark": {
          "type": "string",
          "description": "The IBC UN mark from the plate; the code and month of manufacture are read from it, e.g. \"31HA1/Y/03 22/D/BAM 12345/10800/1200\""
        },
        "bottle": {
          "type": "string",
          "description": "Month the inner receptacle was replaced, for remanufactured composite IBCs"
        },
        "regime": {
          "enum": [
            "un",
            "us"
          ],
          "type": "string",
          "description": "un: UN Model Regulations and ADR (default). us: 49 CFR 180.352"
        },
        "repair": {
          "type": "string",
          "description": "Month of the last repair, if any"
        }
      }
    }
    arguments 41 lines
  • adr_1000_points open 18h ago

    Total the ADR 1.1.3.6 points for a road load of dangerous goods and say whether it stays within the small-load exemption, and what still applies if it does. Use when: the user asks whether a vehicle load needs full ADR. Instead: un_number_packaging for container rules; bund_size for storage. Inputs: one line per substance and package size, so the same UN number in two package sizes is two lines. packing_group matters only where a UN number has entries in more than one transport category, such as UN 1263 paint; without it those lines are refused with the entries to choose from. Points are quantity_per_package times packages times the category multiplier: 50 for category 1, 3 for category 2, 1 for category 3 and 0 for category 4. A category 0 substance needs full ADR at any quantity. Behaviour: covers 92 UN numbers. If any line cannot be read, the whole load is refused with a reason per line and never totalled without it. An exempt load still carries duties, listed in still_required. Unknown arguments are ignored and named in assumed. Constraints: no authentication, key or headers. At most 10 requests per 10 seconds per IP address; above that HTTP 429, so space out repeated calls.

    mcp-tool

    {
      "type": "object",
      "required": [
        "lines"
      ],
      "properties": {
        "lines": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "un",
              "quantity_per_package"
            ],
            "properties": {
              "un": {
                "type": "string",
                "description": "UN number, e.g. \"1203\""
              },
              "packages": {
                "type": "integer",
                "default": 1,
                "description": "Number of packages of this size"
              },
              "packing_group": {
                "enum": [
                  "I",
                  "II",
                  "III"
                ],
                "type": "string",
                "description": "Packing group from section 14 of the safety data sheet. Required where the UN number has entries in more than one transport category, such as 1263 paint; the refusal lists them"
              },
              "quantity_per_package": {
                "type": "number",
                "description": "Litres (liquids) or kg (solids) in each package, e.g. 20 for a 20 L jerrican"
              }
            }
          },
          "description": "One item per substance carried"
        }
      }
    }
    arguments 43 lines
  • decode_un_packaging_mark open 6h ago

    Decode a UN packaging mark part by part: packaging code, performance level, density or gross mass, test pressure, year, state and maker, for packagings, IBCs, large packagings, salvage and reconditioned marks. Use when: the user has read a mark off a drum, jerrican, box or IBC. Instead: un_number_packaging to find which codes a substance may use; ibc_inspection_dates for an IBC's test dates. Inputs: mark alone decodes. Adding un also checks, against ADR 2025 Table A, whether that container may carry that substance, using the density limit printed in the mark. A bare code such as 3H1 decodes to its meaning only. If the user has not read the mark, ask for it rather than describing the container. Behaviour: text it cannot read as a mark returns ok:false, and only the first 120 characters are read. If un is not one of the 157 covered numbers, the mark still decodes and check carries the error. Unknown arguments are ignored and named in assumed. Constraints: no authentication, key or headers. At most 10 requests per 10 seconds per IP address; above that HTTP 429, so space out repeated calls.

    mcp-tool

    {
      "type": "object",
      "required": [
        "mark"
      ],
      "properties": {
        "un": {
          "type": "string",
          "description": "Optional UN number (four digits) to check the container against, e.g. \"1203\""
        },
        "mark": {
          "type": "string",
          "description": "The mark as printed, parts separated by slashes, e.g. \"UN 3H1/Y1.9/150/26/D/BAM 12345\" or an IBC mark \"31HA1/Y/03 22/D/BAM 12345/10800/1200\""
        }
      }
    }
    arguments 16 lines
  • create_quote_request unknown never probed

    Send a quotation request for one or more Fortitude21 products to a person who prices it, and get a reference back. Use when: the buyer wants a quotation and has agreed to share their contact details. Instead: get_product_pricing for indicative terms without contacting anyone. Inputs: consent must be true and means the buyer agreed, not the agent. A quantity under the minimum order is recorded, not refused. Without a destination (delivery_destination or country) or incoterms the request is still sent, and the gaps come back in missing_information. A required_date not written as YYYY-MM-DD refuses the request. Behaviour: writes and is not idempotent. Each call stores an enquiry and emails it to Fortitude21's sales team, who reply by email, usually within one working day, so two calls send two requests. It never creates an order or accepts a price. An unknown sku or missing consent refuses the whole request. Constraints: no authentication, key or headers. At most 10 requests per 10 seconds per IP address; above that HTTP 429, so space out repeated calls.

    mcp-tool

    {
      "type": "object",
      "required": [
        "consent",
        "company",
        "contact_name",
        "email",
        "lines"
      ],
      "properties": {
        "email": {
          "type": "string",
          "description": "Business email address for the reply"
        },
        "lines": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "sku",
              "quantity"
            ],
            "properties": {
              "sku": {
                "type": "string",
                "description": "An F21 part number or product slug"
              },
              "quantity": {
                "type": "integer",
                "description": "Whole number of units required. Below the minimum order is recorded, not refused"
              },
              "certification": {
                "type": "string",
                "description": "Certification the destination market requires"
              },
              "specification": {
                "type": "string",
                "description": "Colour, branding, closure, gauge, anything specified"
              }
            }
          },
          "description": "One entry per product"
        },
        "notes": {
          "type": "string",
          "description": "Anything else the quotation should account for"
        },
        "source": {
          "type": "string",
          "description": "The agent or integration sending this, for the enquiry log"
        },
        "company": {
          "type": "string",
          "description": "Buying company name"
        },
        "consent": {
          "type": "boolean",
          "description": "Must be true. Confirms the buyer agreed to their company and contact details being sent to Fortitude21"
        },
        "country": {
          "type": "string",
          "description": "Buyer country"
        },
        "incoterms": {
          "type": "string",
          "description": "Preferred Incoterm, e.g. FOB, CIF, DDP"
        },
        "contact_name": {
          "type": "string",
          "description": "Person to reply to"
        },
        "required_date": {
          "type": "string",
          "description": "Required delivery date, YYYY-MM-DD"
        },
        "delivery_destination": {
          "type": "string",
          "description": "Port or city the goods ship to"
        }
      }
    }
    arguments 81 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 a1e939105b36128e.

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

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.