Ext Ops Panel
Open dashboard
Comparison

Hyperliquid Agent Gateway vs TimeBase

Hyperliquid Agent Gateway is an MCP server published by alekskram. Marketplaces we read that list it: 1 (Official MCP Registry). TimeBase is an MCP server published by epam. Marketplaces we read that list it: 3 (Official MCP Registry, Copilot CLI: github/awesome-copilot, Community GitHub marketplaces). As of our marketplace pass on 2026-10-19. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceHyperliquid Agent GatewayTimeBase
Official MCP Registry Listed
Version: 0.1.3
Downloads/month (PyPI): 391
Downloads/week (PyPI): 40
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 0.2.6
Downloads/month (PyPI): 548
Downloads/week (PyPI): 233
Forks (GitHub): 0
Stars (GitHub): 8
Not marked · First seen
Copilot CLI: github/awesome-copilot Not listed Listed
Version: 0.1.7
Forks (GitHub): 0
Stars (GitHub): 7
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Hyperliquid Agent Gateway vs TimeBase
FactHyperliquid Agent GatewayTimeBase
Marketplaces that list it (differs)1 (worse)3 (better)
Stars (GitHub) (differs)1 (worse)8 (better)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)On your machine (hyperliquid-agent-gateway)On your machine (timebase-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published16, secrets among them: 6
Parts of the bundle (differs)Not a bundle8
Licence (differs)Not statedApache-2.0
Repository (differs)github.com/alekskram/hyperliquid-agent-gatewaygithub.com/epam/timebase-mcp
Changes in the last 7 days (differs)02
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Hyperliquid Agent Gateway

In its own words, on Official MCP Registry:

Read-only MCP gateway to Hyperliquid: liquidation distance, funding carry, HyperEVM flows. No keys.

TimeBase

In its own words, on Official MCP Registry:

Explore and query TimeBase streams, schemas, QQL, symbols, and server status via MCP.

How to run each

Hyperliquid Agent Gateway As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio hyperliquid-agent-gateway -- uvx hyperliquid-agent-gateway

TimeBase As a local MCP server: PyPI package

Claude Code
claude mcp add --env "TIMEBASE_OAUTH2_CLIENT_SECRET=<YOUR_TIMEBASE_OAUTH2_CLIENT_SECRET>" --env "TIMEBASE_PASSWORD=<YOUR_TIMEBASE_PASSWORD>" --transport stdio timebase-mcp -- uvx --from "timebase-mcp[all]" timebase-mcp

Requires: TIMEBASE_OAUTH2_CLIENT_SECRET (secret), TIMEBASE_PASSWORD (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of Hyperliquid Agent Gateway publish no settings it asks for, so we do not compare settings.

What it can do: Hyperliquid Agent Gateway · What it can do: TimeBase · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/github/awesome-copilot/blob/HEAD/.github/plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built