OilPriceAPI
OfficialRelated Servers
Alternatives to OilPriceAPI
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceExposes energy market signals and readiness indices by integrating data from sources like Yahoo Finance, ENTSOG, and AGSI+. It enables users to query gas flows, storage levels, power prices, and weather data via natural language.-
- AlicenseNot gradedqualityCmaintenanceEnables querying monthly oil and gas production, consumption, imports, exports, and closing stocks by country, with tools for time-series lookups, cross-country comparisons, and coverage checks.579 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables users to fetch current and historical prices for 37 US crops from futures, USDA farm, and global benchmark sources, compare commodities, and retrieve group snapshots.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to retrieve current EIA residential heating oil and propane prices by state or region, compare weekly and year-ago changes, view historical price series, and estimate heating costs per delivery or million Btu.MIT
- AlicenseNot gradedqualityCmaintenanceEnables querying current and historical retail petrol, diesel, and LPG prices across European countries, comparing prices by week, and checking data coverage.462 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to query read-only US power market data, including plant generation, emissions, ownership and offtake, plus ISO node and hub prices and basis across seven markets, with sourced results.MIT
TDQS
Scored across 32 tools
Most tools target distinct data categories, but clusters like drilling/rigs and price overviews (get_price, market_overview, market_brief, compare_prices) have enough overlap to cause occasional misselection. The detailed descriptions mitigate but do not fully eliminate ambiguity.
All tools share the opa_ prefix and use snake_case with a mostly verb-first pattern (get, list, search, lookup, compare). The noun-phrase opa_market_overview is a minor deviation, but the overall convention is predictable.
At 32 tools, the server is over-instrumented. While the energy domain is broad, many narrow tools (e.g., diesel_by_state, fuel_surcharge, marine_fuels) could be consolidated or parameterized, and the count exceeds the typical practical limit for agent navigation.
Data coverage is extensive, but lifecycle support is incomplete: opa_get_market_brief references opa_create_price_subscription which is not exposed, and there are no create/update/delete tools for subscriptions or alerts. This creates dead ends for persistence workflows.