TimeBase vs Polymarket MCP Server
TimeBase is an MCP server published by epam. Marketplaces we read that list it: 2 (Official MCP Registry, Copilot CLI: github/awesome-copilot). Polymarket MCP Server is an MCP server published by joinQuantish. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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 |  Polymarket MCP Server |
|---|---|---|
| Official MCP Registry | Listed Version: 0.2.6 Downloads/month (PyPI): 548 Downloads/week (PyPI): 233 Forks (GitHub): 0 Stars (GitHub): 8 Not marked · First seen |
Listed Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| Copilot CLI: github/awesome-copilot | Listed Version: 0.1.7 Forks (GitHub): 0 Stars (GitHub): 7 Not marked · First seen |
Not listed |
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 | TimeBase | Polymarket MCP Server |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 8 (better) | 0 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (timebase-mcp) | Not stated |
| Transport (differs) | stdio | Not stated |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 15, secrets among them: 2 | Not published |
| Parts of the bundle (differs) | 8 | Not a bundle |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/epam/timebase-mcp | github.com/joinquantish/polymarket-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-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
TimeBase
Explore and query TimeBase streams, schemas, QQL, symbols, and server status via MCP.
Polymarket MCP Server
Self-hosted MCP server for AI agent trading on Polymarket prediction markets
How to run each
TimeBase 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)
Polymarket MCP Server
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
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 Polymarket MCP Server publish no settings it asks for, so we do not compare settings.
What it can do: TimeBase · What it can do: Polymarket MCP Server · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.