X (Twitter) Trends API vs TimeBase
X (Twitter) Trends API is an MCP server published by trendsapi.ai. 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-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 |  X (Twitter) Trends API |  TimeBase |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.2 Forks (GitHub): 0 Stars (GitHub): 0 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
| Fact | X (Twitter) Trends API | TimeBase |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 3 (better) |
| Stars (GitHub) (differs) | 0 (worse) | 8 (better) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | 2026-10-21 | Not published |
| Where it runs (differs) | Remote server (x-twitter.api.trendsapi.ai/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) | Not a bundle | 8 |
| Licence (differs) | Not stated | Apache-2.0 |
| Repository (differs) | github.com/trendsapi-ai/trends-mcp | github.com/epam/timebase-mcp |
| Changes in the last 7 days (differs) | 1 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 4 days ago | 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
X (Twitter) Trends API
X trending topics and discussion volume over time. Free key at trendsapi.ai
TimeBase
Explore and query TimeBase streams, schemas, QQL, symbols, and server status via MCP.
How to run each
X (Twitter) Trends API As a remote MCP server
claude mcp add --transport http x-twitter https://x-twitter.api.trendsapi.ai/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
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)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only X (Twitter) Trends API has a remote endpoint we check. How we check endpoints
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 X (Twitter) Trends API publish no settings it asks for, so we do not compare settings.
What it can do: X (Twitter) Trends API · 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.