MCP.Market

Fuel Prices MCP server

online · 100% uptime
by johnisanerd·io.github.johnisanerd/fuel-prices·v1.0.0·2 stars

Gas and fuel prices by station and area, as structured data via a hosted MCP server.

A97/100grade A
What users say
No reviews yet
Be the first
Safety scan
A97/100

full report

Adoption
Growing

2 stars

Reviews

Write one

Nobody has reviewed Fuel Prices yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Fuel Prices tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Public scan report

scanner v0.1.9 · 2026-09-25 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 39ms (auth required)20/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualityOAuth resource metadata advertised on 40115/15
  • Maintenancelast push 1 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 97/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Fuel Prices compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
97/100
higher than 98% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
162 ms
faster than 71% of 30,031 servers
GitHub stars
2
more than 75% of 28,688 servers

Install Fuel Prices in Claude Code, Cursor or VS Code

claude mcp add --transport http fuel-prices https://mcp.apify.com/?tools=johnvc/fuelprices
Add to Cursor

What the publisher says

From the Fuel Prices repository's README, as published. We do not edit it. Read it on GitHub

⛽ Fuel Prices API: Live US Gas Station Prices in Clean JSON

The most efficient, reliable, and developer-friendly way to use the Fuel Prices API.

Actor page: apify.com/johnvc/fuelprices Input schema: apify.com/johnvc/fuelprices/input-schema

The Fuel Prices API returns live, crowd-reported gas station prices and station metadata for any US location (with some Canadian coverage) as clean, structured JSON. Search by ZIP code, city name, or GPS coordinates and get one record per station: name, full address, distance from your search point, cash and credit prices with posting timestamps, price unit, and ratings. Choose the fuel type (regular, midgrade, premium, diesel, E85, or unleaded 88) and filter by data freshness.

Video Walkthrough

Quick Start

Prerequisites

  • Python 3.11 or higher
  • An Apify account and API key (get a free key here)
  1. Clone the repository
git clone https://github.com/johnisanerd/Apify-Fuel-Prices-Scraper.git
   cd Apify-Fuel-Prices-Scraper
  1. Install dependencies with UV
# Install UV if you do not have it:
   curl -LsSf https://astral.sh/uv/install.sh | sh

   # Install project dependencies:
   uv sync
  1. Configure your API key
cp .env.example .env
   # Edit .env and add your Apify API key
   # Get your free API key at: https://apify.com?fpr=9n7kx3
  1. Run the example
uv run python fuel-prices-scraper.py

Alternative: set the API key directly

export APIFY_API_TOKEN="your_api_key_here"
uv run python fuel-prices-scraper.py

Why Use This Fuel Prices API?

Station-level detail. Each result is one gas station with its name, full address, distance from your search point, cash and credit prices, price unit, and ratings, so you can compare stations directly.

Search any way you like. Query by ZIP code, city name, or GPS coordinates pasted straight from a map. Coordinates resolve to the nearest area.

Fuel-type and freshness controls. Pick regular, midgrade, premium, diesel, E85, or unleaded 88, and use the freshness filter to keep only recently reported prices.

Pay only for results. Billing is per station returned, with no setup fee, no subscription, and no charge for runs that return nothing. A typical city or ZIP search costs a couple of cents.

Easy to automate. Call it from Python in a few lines, or load it as an MCP tool so assistants like Claude and Cursor can pull live fuel prices for you on demand.

Features

Core Capabilities

  • Search by ZIP, city, or coordinates across US locations (some Canadian coverage)
  • Fuel-type selection: regular, midgrade, premium, diesel, E85, unleaded 88
  • Freshness filtering by maximum data age in days
  • Cash and credit prices with per-price posting timestamps
  • Station metadata: name, address, distance, ratings

Data Quality

  • One record per station with a stable structure
  • Cash and credit prices reported separately, each with a posted time
  • Full address components (line 1/2, city, region, postal code)
  • Distance and ratings for ranking and comparison
  • Consistent JSON shape across every query

Usage Examples

Basic Example

The cheapest way to try the API: one ZIP code, regular fuel.

{
  "search": "11507"
}

Advanced Example

A city search for diesel, freshest data only.

{
  "search": "New York, NY",
  "fuel": 4,
  "lang": "en",
  "maxAge": 3
}

By coordinates

Paste GPS coordinates straight from a map.

{
  "search": "36.0816642, -115.0534345",
  "fuel": 1
}

Input Parameters

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Fuel Prices: common questions

Is Fuel Prices MCP server safe?
Yes, by our scan: it is graded A (97/100). Read the Fuel Prices safety report
How do I install Fuel Prices?
It runs remotely at mcp.apify.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Fuel Prices need an API key?
No key to paste: it signs you in with OAuth when your client connects.
Is Fuel Prices maintained?
The last commit was 41 days ago (2026-09-24). The latest release is v1.0.0.
Is Fuel Prices up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Fuel Prices compare with other MCP servers?
safety score 97/100 (higher than 98% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 162 ms (faster than 71% of 30,031 servers). Full comparison.