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.

TokenOS Gas & Fee Tracker

REMOTE · TOKENOS.AI

Live fees on five chains

Available components

+2 this week 86 Trust /100

Last scanned (5 hours ago)

Scores higher than 93% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Crypto and Web3

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 Security80
Transport & Reachability100
Schema Quality & AI Usability84
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 328 tokens (~82/item across 4 items; 3 tools + 1 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage83
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 50% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "cheapest_chain_to_deploy" implies "deploy" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
  • An AI judge read all 5 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
  • Supports UI / widget rendering.Pass
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.

  • 2 Nov 26 0
    • Stability: 0.97 → pass security
  • 1 Nov 26 +1

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

  • 30 Oct 26 +1

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

  • 28 Oct 26 +1

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

  • 26 Oct 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.

  • 23 Oct 26 +1

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

  • 21 Oct 26 +1

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

  • 19 Oct 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.

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 5 Nov 2026 · Probed https://tokenos.ai/api/mcp/apps/gas-tracker

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=tokenos.ai CN=WE1,O=Google Trust Services,C=US 24 Oct 2026 22 Jan 2027 ECDSA 256 ECDSA-SHA256 b91e1ad31864bf7c0e7379d501820fce
SANs: tokenos.ai
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 tokenos.ai. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 1814, 3799 8, 8 Verified
tokenos.ai. absent 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
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://tokenos.ai/api/mcp/apps/gas-tracker Verified 200
http (plaintext) http://tokenos.ai/api/mcp/apps/gas-tracker HTTPS enforced 301 https://tokenos.ai/api/mcp/apps/gas-tracker
MCP tools · 3 exposed · ~240 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
cheapest_chain_to_deploy ~70

Rank Ethereum, Base, Arbitrum, Robinhood Chain and Solana by the cost of deploying a contract or program of a given bytecode size.

NameTypeReqDescription
bytecode_kbnumber–Compiled bytecode size in KB (default 24)
speedstring––

No output schema declared.

No examples provided.

estimate_tx_cost ~91

Cost of one transaction on a chain at a speed tier, by transaction type (transfer, erc20_transfer, swap, nft_mint, deploy) or explicit gas / compute units.

NameTypeReqDescription
chainstringyes–
gas_unitsinteger–Override: gas units (EVM) or compute units (Solana)
speedstring––
tx_typestring––

No output schema declared.

No examples provided.

gas_now ~79

Current fees on Ethereum, Base, Arbitrum, Robinhood Chain and Solana: base fee, slow/standard/fast tiers, USD cost per transaction type, trend and the cheapest chain.

NameTypeReqDescription
chainsarray–Subset of chains (default all)
speedstring–Tier used for the USD cost columns (default standard)

No output schema declared.

No examples provided.

Install

How do I install the TokenOS Gas & Fee Tracker MCP server?

TokenOS Gas & Fee Tracker is a hosted endpoint at https://tokenos.ai/api/mcp/apps/gas-tracker, 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 · tokenos.ai

# add to Claude Code
claude mcp add --transport http ai-tokenos-gas-tracker 'https://tokenos.ai/api/mcp/apps/gas-tracker'
Common questions

What is the TokenOS Gas & Fee Tracker MCP server?

TokenOS Gas & Fee Tracker is an MCP server listed in the public MCP registry as ai.tokenos/gas-tracker. Live fees on five chains. This page covers its hosted endpoint (https://tokenos.ai/api/mcp/apps/gas-tracker).

Is the TokenOS Gas & Fee Tracker MCP server safe to use?

TokenOS Gas & Fee Tracker scores 86 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 TokenOS Gas & Fee Tracker MCP server expose?

TokenOS Gas & Fee Tracker exposes 3 tools: gas_now, estimate_tx_cost, cheapest_chain_to_deploy. Their descriptions and schemas cost roughly 240 tokens of context every time the server is loaded.

Does the TokenOS Gas & Fee Tracker MCP server require authentication?

No. We connected to TokenOS Gas & Fee Tracker without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the TokenOS Gas & Fee Tracker MCP server still maintained?

TokenOS Gas & Fee Tracker 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.