io.github.pipeworx-io/fuel-prices is an MCP server that retail petrol, diesel and LPG prices across Europe, by country and week. Its tool list has not been published yet over http, requires no API key, and scores 60/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"fuel-prices": {
"url": "https://gateway.pipeworx.io/fuel-prices/mcp"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Retail petrol, diesel and LPG prices across Europe, by country and week.
This server supports HTTP transport. Be the first to test it - help the community know if it works.
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked @pipeworx/mcp-fuel-prices against OSV.dev.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in ecommerce
Which credit card earns the most at a merchant, from your cards or every card, and why.
Read-only MCP servers for Russian marketplaces: prices, stock, ratings, reviews, seller identity
Dutch construction facts with measured accuracy + NL coordination. Never holds third-party funds.
MCP server for EPLAN Electric P8: ~200 tools to drive EPLAN from Claude Code, Codex, Cursor or any MCP client (actions, scripts, live DataModel, exports). Includes the eplan-tools plugin marketplace.
MCP Security Weekly
Get CVE alerts and security updates for io.github.pipeworx-io/fuel-prices and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
What petrol, diesel and LPG cost across Europe — 28 countries, weekly, back to 2005.
Part of Pipeworx — an MCP gateway connecting AI agents to 1865+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
| Tool | Answers |
|---|---|
fuel_price | "What does petrol cost in Portugal?" — current price per litre for one country. |
compare_fuel_prices | "Where is diesel cheapest in Europe?" — every country ranked, within one week. |
fuel_price_history | "How much has petrol gone up in Germany this year?" — weekly series plus the change. |
fuel_price_coverage | What countries, weeks and fuels are in scope, and how fresh the newest week is. |
None. No key, no account.
The European Commission's Weekly Oil Bulletin:
Weekly_Oil_Bulletin_Prices_History_maticni_4web.xlsxEU Member States report retail prices into it every week under Council Decision
1999/280/EC, and the Commission publishes the consolidated series. Coverage is
the 27 EU states plus the United Kingdom, plus an EU-wide aggregate under the
code EU.
2143 is €2.143 per litre. Every response
carries price_per_litre_eur already converted, and the raw figure alongside
it with its unit.price_per_litre_eur is null for those rather than a
fabricated conversion.week_ending so a figure cannot be quoted as
"today" by accident.EU is an aggregate, not a country. It is available to ask for directly
but is excluded from compare_fuel_prices rankings.country_not_covered refusal naming the reason rather than an empty result.Weekly, when the Commission republishes the bulletin:
node scripts/ingest-eu-oil-bulletin.mjs # full history
node scripts/ingest-eu-oil-bulletin.mjs --weeks 8 # just the recent tail
The script parses the workbook with no dependencies — xlsx is a zip of XML, and
node ships zlib — and upserts by (country_code, week_ending, fuel), so a week
that stops being republished keeps its last known value.
It refuses to load rather than warn in two cases, because both would otherwise produce a plausible series that is wrong:
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"fuel-prices": {
"url": "https://gateway.pipeworx.io/fuel-prices/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/fuel-prices/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.