Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Heating Oil and Propane Prices MCP

REMOTE · HEATING-OIL-PROPANE-PRICES-MCP.LIPMICHAL.WORKERS.DEV

Heating oil and propane prices per gallon by state, from the EIA weekly survey, with history.

+4 this week 72 Trust /100

Last scanned (12 hours ago)

Scores higher than 57% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 645 tokens (~215/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
  • Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 85% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 8 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 6 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://heating-oil-propane-prices-mcp.lipmichal.workers.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=lipmichal.workers.dev CN=WE1,O=Google Trust Services,C=US 2 Oct 2026 31 Dec 2026 ECDSA 256 ECDSA-SHA256 ebf145553d5751d20e0d3cd51e3d7a94
SANs: lipmichal.workers.dev, *.lipmichal.workers.dev
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of heating-oil-propane-prices-mcp.lipmichal.workers.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
workers.dev. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://heating-oil-propane-prices-mcp.lipmichal.workers.dev/mcp Verified 200
http (plaintext) http://heating-oil-propane-prices-mcp.lipmichal.workers.dev/mcp Inconclusive 405
MCP tools · 3 exposed · ~556 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
estimate_heating_fuel_cost ~268

Cost of a heating oil or propane delivery (gallons times this week's EIA average for the state, or a given price), the cost per million Btu, and a comparison of heating oil and propane per million Btu at the same area's averages. Optionally add your electricity rate (cents per kWh) or natural gas rate (dollars per therm) to compare. Uses EIA heat contents.

NameTypeReqDescription
efficiency_percentnumber–Appliance efficiency in percent, for example 85. Default 100 (fuel energy only).
electricity_cents_per_kwhnumber–Your electricity rate in cents per kWh, to compare.
fuelstringyes–
gallonsnumberyesGallons to buy, for example 200 for a heating oil fill or 400 for a propane tank.
natural_gas_dollars_per_thermnumber–Your natural gas rate in dollars per therm, to compare.
price_per_gallonnumber–Your dealer price per gallon. Default: the EIA average for the state.
statestring–State name or code ("Maine", "CT"), an EIA region ("New England (PADD 1A)") or "US". Default US.

No output schema declared.

No examples provided.

get_heating_fuel_price_history ~137

EIA weekly residential heating oil or propane prices per gallon for the US or a surveyed state between two dates (series since 1990 for most areas), with high, low and average. Default is the last 52 weeks.

NameTypeReqDescription
end_datestring–End date, default the latest week as YYYY-MM-DD.
fuelstringyes–
start_datestring–Start date as YYYY-MM-DD.
statestring–State name or code ("Maine", "CT"), an EIA region ("New England (PADD 1A)") or "US". Default US.

No output schema declared.

No examples provided.

get_heating_oil_propane_prices ~151

Latest EIA weekly average residential price per gallon (taxes included) of heating oil and propane for the US, an EIA region or a surveyed state, read at call time from eia.gov: price, change from last week, the last five survey weeks, the price a year ago and the next release date. Heating oil is surveyed in Northeast and Midwest states; propane in about 40 states. Uncovered states return the covered list.

NameTypeReqDescription
fuelstring–Default both.
statestring–State name or code ("Maine", "CT"), an EIA region ("New England (PADD 1A)") or "US". Default US.

No output schema declared.

No examples provided.

Install

How do I install the Heating Oil and Propane Prices MCP server?

Heating Oil and Propane Prices MCP is a hosted endpoint at https://heating-oil-propane-prices-mcp.lipmichal.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · heating-oil-propane-prices-mcp.lipmichal.workers.dev

# add to Claude Code
claude mcp add --transport http theluckystrike-heating-oil-propane-prices-mcp 'https://heating-oil-propane-prices-mcp.lipmichal.workers.dev/mcp'
Common questions

What is the Heating Oil and Propane Prices MCP server?

Heating Oil and Propane Prices MCP is listed in the public MCP registry as io.github.theluckystrike/heating-oil-propane-prices-mcp. Heating oil and propane prices per gallon by state, from the EIA weekly survey, with history. This page covers its hosted endpoint (https://heating-oil-propane-prices-mcp.lipmichal.workers.dev/mcp).

Is the Heating Oil and Propane Prices MCP server safe to use?

Heating Oil and Propane Prices MCP scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Heating Oil and Propane Prices MCP server expose?

Heating Oil and Propane Prices MCP exposes 3 tools: get_heating_oil_propane_prices, get_heating_fuel_price_history, estimate_heating_fuel_cost. Their descriptions and schemas cost roughly 556 tokens of context every time the server is loaded.

Does the Heating Oil and Propane Prices MCP server require authentication?

No. We connected to Heating Oil and Propane Prices MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Heating Oil and Propane Prices MCP server still maintained?

Heating Oil and Propane Prices MCP is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Heating Oil and Propane Prices MCP server?

VerifyMCP ran 12 checks on Heating Oil and Propane Prices MCP, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Heating Oil and Propane Prices MCP: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.