Remote MCP · Endpoint

TokenOS Gas & Fee Tracker MCP server

No. TokenOS Gas & Fee Tracker answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://tokenos.ai/api/mcp/apps/gas-tracker

The last check completed an MCP handshake.

Registry name
ai.tokenos/gas-tracker
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
533 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Live fees on five chains
Listing
From the official MCP registry (active).
Recent checks of TokenOS Gas & Fee Tracker
CheckedResultHandshake
1 hour agoHandshake completed533 ms
2 days agoHandshake completed214 ms
5 days agoHandshake completed227 ms
7 days agoHandshake completed134 ms
9 days agoHandshake completed315 ms
11 days agoHandshake completed150 ms
13 days agoHandshake completed275 ms
16 days agoHandshake completed280 ms
18 days agoHandshake completed198 ms
19 days agoHandshake completed216 ms
21 days agoHandshake completed291 ms
22 days agoHandshake completed123 ms
23 days agoHandshake completed166 ms
26 days agoHandshake completed70 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 14.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with TokenOS Gas & Fee Tracker and makes no claim about it beyond what these checks measured.