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

commodities.sh

https://api.commodities.sh

Registry code: 5739d3aef547fd75

api record

Primary-source commodities MCP. Start with catalog.list (free) to discover instrument codes, then price.latest / inventory.get / positioning.get for observations. Use snapshot.get for a sector bundle and decision.get for deterministic signal packs. calendar.get (free) lists EIA/USDA/CFTC release cadence. Paid tools settle via x402 USDC on Base.

endpoint
https://api.commodities.sh/api/mcp
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
10 · newcomer
_ is it live, free and safe measured by this hub
Is commodities.sh live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is commodities.sh free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does commodities.sh have?
12 tools: observation.resolve, catalog.list, calendar.get, fx.latest, inventory.get, price.history, snapshot.get, decision.get, ….
Is commodities.sh 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
99.5%

90 days 98.6%· all time 99%

latency
236ms

last good check

priced tools
9

of 12 tools

_ answered our checks, 90 days 507 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
finance & markets stock & market data
used for
  • get latest commodity prices
  • get eia petroleum inventories
  • get cftc positioning data
  • compute commodity spreads
  • list commodity release calendar
takes → gives
text → data
tools
11 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 stands behind 2 doors on this origin, so the chain figures are the operator's. 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
6

distinct

settlements
39

last 2026-11-04

received on chain
0.39 USDC

concentrated

_ what it can do 12 tools
9 paid2 open 1 never probed 11 of 12 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.

  • fx.latest reads 0.01 USDC paid 6h ago

    Return the latest FX rate observation for a pair or FRED FX series. Useful alongside commodity prices when converting cash values across currencies.

    mcp-tool

    {
  "type": "object",
  "required": [
    "pair"
  ],
  "properties": {
    "pair": {
      "type": "string",
      "description": "FX pair or series id. Example: EURUSD, USDCNY, DTWEXBGS."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • inventory.get reads 0.03 USDC paid 9h ago

    Fetch EIA weekly petroleum inventory levels. Omit series to list all latest inventory points, or pass a series key to get week-over-week change, vs-5y deviation, and a surprise label for that series.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "series": {
      "type": "string",
      "description": "Optional EIA inventory series key. Omit to return all latest inventory rows. Example: crude_stocks."
    }
  },
  "additionalProperties": false
}
    arguments 10 lines
  • price.history reads 0.02 USDC paid 2h ago

    Return historical observations for an instrument code (up to 500 points). Use after price.latest when you need a short time series for the same code.

    mcp-tool

    {
  "type": "object",
  "required": [
    "code"
  ],
  "properties": {
    "code": {
      "type": "string",
      "description": "Instrument code from catalog.list. Example: CL, GC, ZC."
    },
    "limit": {
      "type": "number",
      "description": "Number of historical points to return. Max 500, default 60."
    }
  },
  "additionalProperties": false
}
    arguments 17 lines
  • snapshot.get reads 0.05 USDC paid 20h ago

    Build a sector snapshot bundling prices, inventories, spreads, and related fundies for energy, metals, ags, or all sectors. Prefer this over calling many single-observation tools when you need a full sector picture.

    mcp-tool

    {
  "type": "object",
  "required": [
    "sector"
  ],
  "properties": {
    "sector": {
      "enum": [
        "energy",
        "metals",
        "ags",
        "all"
      ],
      "type": "string",
      "description": "Sector to snapshot. Use all to receive energy, metals, and ags together."
    }
  },
  "additionalProperties": false
}
    arguments 19 lines
  • decision.get reads 0.1 USDC paid 20h ago

    Build a deterministic decision pack for energy, metals, ags, or all sectors. Returns method, signals with direction/rationale, an embedded snapshot, and a disclaimer — no ML model, rule-based only.

    mcp-tool

    {
  "type": "object",
  "required": [
    "sector"
  ],
  "properties": {
    "sector": {
      "enum": [
        "energy",
        "metals",
        "ags",
        "all"
      ],
      "type": "string",
      "description": "Sector for the decision pack. Use all to bundle every sector."
    }
  },
  "additionalProperties": false
}
    arguments 19 lines
  • positioning.get reads 0.02 USDC paid 6h ago

    Return the latest CFTC Commitments of Traders managed-money positioning for an instrument code. Includes long, short, net, and week-over-week net change with source URL.

    mcp-tool

    {
  "type": "object",
  "required": [
    "code"
  ],
  "properties": {
    "code": {
      "type": "string",
      "description": "Instrument code from catalog.list. Example: CL, NG, GC, ZC."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • spread.get reads 0.03 USDC paid 20h ago

    Compute a derived spread observation: 3-2-1 crack, soybean crush, or WTI-Brent basis (paid). type=calendar is a free Phase-2 stub that returns available=false until licensed curves exist. Prefer crack/crush/basis for live derived values with formula and inputs.

    mcp-tool

    {
  "type": "object",
  "required": [
    "type"
  ],
  "properties": {
    "root": {
      "type": "string",
      "description": "Optional root symbol for calendar spreads. Example: CL. Ignored for crack/crush/basis."
    },
    "type": {
      "enum": [
        "crack",
        "crush",
        "basis",
        "calendar"
      ],
      "type": "string",
      "description": "Spread type to compute. Example: crack for 3-2-1 gasoline/distillate crack."
    }
  },
  "additionalProperties": false
}
    arguments 23 lines
  • fundamentals.get reads 0.03 USDC paid 6h ago

    Fetch a fundamentals document: USDA WASDE, crop progress, export sales, or USGS mineral summaries. Choose kind based on the ags/metals question you are answering.

    mcp-tool

    {
  "type": "object",
  "required": [
    "kind"
  ],
  "properties": {
    "kind": {
      "enum": [
        "wasde",
        "crop_progress",
        "export_sales",
        "usgs"
      ],
      "type": "string",
      "description": "Fundamentals report kind. Example: wasde for World Agricultural Supply and Demand Estimates."
    }
  },
  "additionalProperties": false
}
    arguments 19 lines
  • price.latest reads 0.01 USDC paid 2h ago

    Return the latest cash/fundies observation for one instrument code. Use catalog.list to discover codes such as CL, GC, or ZC. Response follows the shared observation contract with provenance and license tags.

    mcp-tool

    {
  "type": "object",
  "required": [
    "code"
  ],
  "properties": {
    "code": {
      "type": "string",
      "description": "Instrument code from catalog.list. Example: CL, GC, ZC."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • catalog.list reads open 9h ago

    List every commodity instrument in the catalog with sector, unit, primary source, and freshness metadata. Call this first to discover valid codes before price.latest or inventory.get. Free discovery tool — no payment required.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • calendar.get reads open 9h ago

    List EIA, USDA, and CFTC release calendar entries with cadence, typical Eastern time, next_hint prose, and next_release_at ISO date (America/New_York). Free discovery tool — call before scheduling agents around inventory or WASDE prints.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • observation.resolve unknown never probed

    Resolve a single observation by its id. Derived observations (crack, crush, basis) cite the observations they were computed from in inputs[]; this is how you dereference those ids to audit a derived value. Ids look like obs_<24 hex>.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Observation id, e.g. from a derived observation's inputs[] array."
    }
  },
  "additionalProperties": false
}
    arguments 13 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 5739d3aef547fd75.

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

_ also on commodities.sh 1 entry

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.