com.opnplatform/packindex

3 of 26 tools are described as changing something (creating, editing, deleting, sending or running).

• search_indiceson 1 other serverreads or searches

  “Find PackIndex codes by material, input, format or plain words ('polypropylene', 'recovered paper', 'natural gas', 'kraftliner', 'corrugated box').”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  3 inputs, 1 required

  • layerstring“Optional layer filter: L0 primary inputs, L1 raw materials, L2 semi-finished, L3 finished units.”
  • limitinteger
  • querystringrequired
• get_live_indexreads or searches

  “Today's value of one PackIndex code — commodity inputs (L0: oil, gas, power, metals, recovered fibre), raw materials (L1: PP, HDPE, pulp…), semi-finished (L2: kraftliner, films…) or finished packs (L…”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  2 inputs, 1 required

  • codestringrequired“PackIndex code, e.g.”
  • currencystring“Also show the value in this currency (ISO code, e.g.”
• get_index_historyon 2 other serversreads or searches

  “Price history for any PackIndex code (L0-L3), one value per date: every point for up to 3 months, weekly closes for longer spans, with the change between points.”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  2 inputs, 1 required

  • codestringrequired“PackIndex code, e.g.”
  • monthsinteger“Capped to the caller's plan depth.”
• get_all_indicesreads or searches

  “Page through index values by layer: L0 primary inputs, L1 raw materials, L2 semi-finished (paid plans) and L3 finished packs.”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  3 inputs

  • layerstring
  • limitinteger
  • offsetinteger
• get_carbon_indexreads or searches

  “Carbon footprint: finished packs (L3) in kg CO2e per unit with grade A-D; raw materials and semi-finished (board grades, pulps, polymers, aluminium, steel, cullet) in kg CO2e per tonne, virgin and PE…”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  2 inputs, 1 required

  • codestringrequired“PackIndex code, e.g.”
  • recycled_contentnumber“Materials only: recycled share 0-1 for the CFF value.”
• packindex_queryreads or searches

  “Ask a plain-English question about packaging costs, indices or which PACKIQ agent to use.”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  2 inputs, 1 required

  • currencystring“Answer currency; auto-detected from the question if omitted.”
  • questionstringrequired
• get_index_forecastreads or searches

  “12-week forward value for any PackIndex code — inputs, raw materials, semi-finished and finished packs: current level, projection, projected change and confidence.”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  2 inputs, 1 required

  • codestringrequired“PackIndex code, e.g.”
  • currencystring“Also show the value in this currency (ISO code, e.g.”
• get_priceson 38 other serversreads or searches

  “Today's values for up to 20 PackIndex codes in one call (any layer: oil, gas, resins, pulp, board, films, finished packs) with 1w/1m/3m/1y change — for watchlists and cost models.”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  2 inputs, 1 required

  • codesarrayrequired“PackIndex codes, e.g.”
  • currencystring“Also show values in this currency (ISO code).”
• check_quoteon 4 other serversreads or searches

  “Is this supplier price fair?”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  7 inputs, 2 required

  • codestringrequired“PackIndex code, e.g.”
  • currencystring“Quote currency (ISO code)”
  • pricenumberrequired“Quoted price per unit”
  • quantitynumber“Order quantity in the quote's unit”
  • quote_datestring“YYYY-MM-DD; compares with the benchmark on that date (paid plans)”
  • regionstring“Where the quote is for, e.g.”
  • unitstring“Quote unit: t, kg, lb, MWh, therm, L, bbl, unit, 1000… (defaults to the benchmark's unit)”
• price_adjustmentcalculates or converts

  “Recalculate an index-linked contract price: base price and base date plus the indices it follows and their weights (the rest is fixed).”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  7 inputs, 2 required

  • adjustment_datestring“YYYY-MM-DD, default today”
  • base_datestringrequired“YYYY-MM-DD the base price was agreed”
  • base_pricenumberrequired
  • codestring“Shortcut for one index (with weight)”
  • componentsarray“e.g.”
  • currencystring“Currency of the contract price (label only)”
  • weightnumber
• compare_regionson 3 other serversreads or searches

  “One material across regions — e.g.”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  5 inputs

  • codesarray“Or explicit codes to compare”
  • duty_pctnumber“Import duty % into the reference region”
  • freight_per_unitnumber“USD freight per benchmark unit into the reference region”
  • materialstring“Code or name, e.g.”
  • referencestring“Reference code (default: the European benchmark)”
• explain_price_moveon 1 other server

  “Why did a price move?”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  2 inputs, 1 required

  • codestringrequired“PackIndex code, e.g.”
  • periodstring

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.