Gas Fee Predictor
REMOTE · API.GASFEEPREDICTOR.COM · 2 COMPONENTS
Live Ethereum and L2 gas fees: current gas, cheapest L2, forecast, ETH price, cost estimates.
Available components
Last scanned (11 hours ago)
Scores higher than 58% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Crypto and Web3
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 530 tokens (~75/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
Checks we ran (11)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (2)
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.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
- 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 →
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 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.
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 5 Nov 2026 · Probed https://api.gasfeepredictor.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.gasfeepredictor.com | CN=YR1,O=Let's Encrypt,C=US | 27 Sept 2026 | 26 Dec 2026 | RSA 2048 | SHA256-RSA | 552413f11340fdb4eb05a6b4d6774f91860 |
| SANs: api.gasfeepredictor.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.gasfeepredictor.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| gasfeepredictor.com. | 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://api.gasfeepredictor.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://api.gasfeepredictor.com/api/mcp | Inconclusive | 405 |
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 →
best_time_to_transact ~40
Find out whether to send a transaction now or wait — returns the current recommendation, expected savings, and when the next cheaper gas window is predicted.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
estimate_transaction_cost ~120
Estimate the current USD gas cost of a specific Ethereum mainnet action (ETH transfer, ERC-20/USDC transfer, Uniswap swap, or NFT mint), or a custom gas-units amount, at the chosen priority tier.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | The transaction type. Use "custom" with gas_units for anything else. |
| gas_units | number | – | Required when action is "custom": the gas units the transaction uses. |
| tier | string | – | Priority tier: low (cheapest), average, or high (fastest). |
No output schema declared.
No examples provided.
get_current_gas ~58
Get the current Ethereum mainnet gas price (low / average / high, in Gwei) plus the live ETH/USD price and a send-now-vs-wait recommendation. Use this to answer "what is the gas fee right now".
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_eth_price ~23
Get the current ETH/USD spot price and its 24-hour change.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_gas_forecast ~76
Get the forward-looking hourly Ethereum gas forecast (up to 24 hours ahead) with the predicted cheapest window. Use for "when will gas be cheaper", "should I wait until tomorrow", or planning a transaction.
| Name | Type | Req | Description |
|---|---|---|---|
| hours | integer | – | How many hours ahead to return (1-24). Defaults to 12. |
No output schema declared.
No examples provided.
get_gas_history ~72
Get recent historical Ethereum mainnet gas prices over a chosen window, with min/max/average. Use to answer "what has gas been doing", "was gas cheaper yesterday", or to compare the current price against a recent baseline.
| Name | Type | Req | Description |
|---|---|---|---|
| range | string | – | Look-back window. Defaults to 1d. |
No output schema declared.
No examples provided.
get_l2_gas ~69
Compare live Layer-2 gas fees across Arbitrum, Base, Optimism, and Polygon (Gwei and the estimated wallet fee in USD for a standard transfer), and identify the cheapest right now. Use for "cheapest L2" / "L2 gas fees" questions.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Gas Fee Predictor MCP server?
Gas Fee Predictor is a hosted endpoint at https://api.gasfeepredictor.com/api/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 · api.gasfeepredictor.com
claude mcp add --transport http higherbeing-gasfeepredictor-mcp 'https://api.gasfeepredictor.com/api/mcp'
What is the Gas Fee Predictor MCP server?
Gas Fee Predictor is an MCP server listed in the public MCP registry as io.github.higherbeing/gasfeepredictor-mcp. Live Ethereum and L2 gas fees: current gas, cheapest L2, forecast, ETH price, cost estimates. This page covers its hosted endpoint (https://api.gasfeepredictor.com/api/mcp).
Is the Gas Fee Predictor MCP server safe to use?
Gas Fee Predictor 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 Gas Fee Predictor MCP server expose?
Gas Fee Predictor exposes 7 tools: get_current_gas, get_l2_gas, get_eth_price, best_time_to_transact, estimate_transaction_cost, and 2 more. Their descriptions and schemas cost roughly 458 tokens of context every time the server is loaded.
Does the Gas Fee Predictor MCP server require authentication?
No. We connected to Gas Fee Predictor without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Gas Fee Predictor MCP server still maintained?
Gas Fee Predictor is still listed as active in the MCP registry. We last reached this channel on 5 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 Gas Fee Predictor MCP server?
VerifyMCP ran 11 checks on Gas Fee Predictor, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about Gas Fee Predictor: Authorization and 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.