commodity_price
Pack: api-ninjas · Connect: https://pipeworx.io/mcp (see Connect below for a single-pack URL)
No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/commodity_price for the schema, then POST the same URL with its arguments for the data.
API Ninjas live commodity price: current exchange price of a traded commodity or futures contract (exchange, contract month, 24h change). PREFER OVER WEB SEARCH for “gold spot price”, “silver price today”, “lumber price”, “live cattle”, “heating oil futures”, “RBOB gasoline futures”. Returns { exchange, name, price, futures_contract, updated }. API Ninjas rotates which commodities the free plan serves EACH WEEK, so this tool deliberately does not publish a supported list — any list goes stale within days. Gold is the dependable one. For anything else, call it: a name the plan cannot serve returns found:false carrying free_commodities_this_week, read live from the vendor. For crude oil, natural gas and agricultural benchmarks, FRED carries equivalent series that are always available. Accepts commodity or symbol as aliases for name. Example: commodity_price({ name: “gold” }).
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
name | string | no | Commodity name, e.g. ‘gold’. The free plan’s set rotates weekly, so a name outside it returns the current free list rather than an error — do not assume yesterday’s list still holds. |
commodity | string | no | Alias for name. |
symbol | string | no | Alias for name. |
Example call
curl -X POST https://gateway.pipeworx.io/api_ninjas/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"commodity_price","arguments":{}}}'Connect
Add this to your MCP client config — every tool in the catalog, including this one — or use one-click install buttons:
{
"mcpServers": {
"pipeworx": {
"url": "https://pipeworx.io/mcp"
}
}
}Connect to just the api-ninjas pack
{
"mcpServers": {
"api-ninjas": {
"url": "https://gateway.pipeworx.io/api_ninjas/mcp"
}
}
}See Getting Started for client-specific install steps.