NatGasLens — US Natural Gas & Henry Hub Data
com.natgaslens/natgaslens · 0.4.2
US natural gas for agents: LNG feedgas, outages, EIA storage, Henry Hub curve, COT, charts
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 60 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 15 of 15 | The registry entry declares a key or a token. |
| Latest connection test reached it | 20 of 20 | The latest test had its handshake answered. |
Where it answers
https://mcp.natgaslens.com/mcpstreamable-httpAuthorizationoptional, secret: Bearer <token> from a paid NatGasLens subscription — no free trial; get one at https://t.me/NatGasLens_bot?start=mcp (the same token opens natgaslens.com). Optional: without it every tool still answer
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 12 tools.
- Protocol
- 2025-06-18
- Calls itself
- natgaslens 0.4.2
- Handshake time
- 375 ms
- HTTP status
- 200
The tools it lists (12, as of 2 days ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
get_us_natural_gas_market_briefSTART HERE for any US natural gas / Henry Hub question: the whole dashboard in one call, so an agent does not have to chain five tools and stitch the numbers itself. Returns, as of the latest data we hold: (1) pressure — every fundamental we track (LNG feedgas, liquefaction outages, weather-model shifts, the EIA injection pace, power burn vs normal, NOAA cooling demand, total demand week-over-week) with its direction on price, strength, the number behind it and a plain-English sentence, plus an overall roll-up naming which signals push down and which push up; (
get_us_natural_gas_fundamental_scoreComposite fundamental pressure score for US natural gas / Henry Hub (-100..+100), built from 5 z-normalized signals (EIA storage vs 5-yr norm, 4-week surplus change, power burn, 7-day cooling and heating demand), with per-signal breakdown, its percentile against its own history and the latest NOAA degree-day forecast revision. ALWAYS returns the score's measured out-of-sample accuracy (walk-forward, against a baseline) and a disclaimer: this is market analysis, NOT investment advice. Set include_history=true for the daily score series with Henry Hub spot prices
get_us_natural_gas_storage_nowcastEIA weekly natural gas storage report (Bcf, lower-48 working gas): the released headline injection/withdrawal plus, on pro scope, `pending` — our estimate of the report that has NOT been published yet, built from weather-driven demand and LNG feedgas components — and `last_verified` (estimate vs actual with realized error), alongside out-of-sample accuracy and backtest stats. Every week also carries the market expectation (`consensus_bcf`, pre-release snapshot) and the surprise against it (`actual_minus_consensus_bcf`) — our `est_bcf` is a model nowcast, not the
get_us_natural_gas_production_nowcastDaily/monthly US dry natural gas production nowcast (Bcf/d), estimated from the year-ago level scaled by a YoY growth trend and anchored to news, with a per-month series (est vs EIA actual once published). Demo scope hides the freshest month's estimate.
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
com.natgaslens/natgaslens, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 70 days ago. The registry entry · natgaslens.com