Goldsky vs TimeBase
Goldsky is a plugin bundle for AI coding tools published by Goldsky. Marketplaces we read that list it: 1 (Community GitHub marketplaces). 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-21. 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
| Marketplace |  TimeBase | |
|---|---|---|
| Community marketplace goldsky-io/goldsky-agent | Listed Version: 1.7.14 Forks (GitHub): 1 Stars (GitHub): 12 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | 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
| Fact | Goldsky | TimeBase |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 3 (better) |
| Stars (GitHub) (differs) | 12 (better) | 8 (worse) |
| Forks (GitHub) (differs) | 1 (better) | 0 (worse) |
| Last release (differs) | 2026-10-20 | Not published |
| Where it runs (differs) | Remote server (docs.goldsky.com/mcp) | On your machine (timebase-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 16, secrets among them: 6 |
| Parts of the bundle (differs) | 22 | 8 |
| Licence (differs) | MIT | Apache-2.0 |
| Repository (differs) | github.com/goldsky-io/goldsky-agent | github.com/epam/timebase-mcp |
| Changes in the last 7 days (differs) | 3 | 2 |
| First seen (differs) | 2026-10-19 | 2026-10-11 |
| Endpoint at the last check (differs) | not checked yet | no remote endpoint we check |
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
Goldsky
Index and stream onchain data for the questions finance teams actually ask: proof-of-reserves and circulating supply, stablecoin transfer and sanctions monitoring, deposit detection, cross-chain settlement tracking (CCTP), payment reconciliation, wallet balances and transaction history, tokenized assets and RWA holder registries, and prediction-market data including Polymarket fills, positions and PnL. Real-time pipelines, hosted subgraphs, and managed RPC across 150+ chains.
TimeBase
Explore and query TimeBase streams, schemas, QQL, symbols, and server status via MCP.
How to run each
Goldsky As a Claude Code plugin
/plugin marketplace add goldsky-io/goldsky-agent
/plugin install goldsky@goldsky-agentTimeBase As a local MCP server: PyPI package
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-mcpRequires: 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 Goldsky publish no settings it asks for, so we do not compare settings.
What it can do: Goldsky · What it can do: TimeBase · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.