TwitterAPIs vs io.github.chrischall/easytable-mcp
TwitterAPIs is an MCP server published by TwitterAPIs. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). io.github.chrischall/easytable-mcp is an MCP server published by chrischall. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-08. 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 |  TwitterAPIs |  io.github.chrischall/easytable-mcp |
|---|---|---|
| Official MCP Registry | Listed Version: 0.28.0 Downloads/month (npm): 3 443 Downloads/week (npm): 200 Forks (GitHub): 3 Stars (GitHub): 6 Not marked · First seen |
Listed Version: 1.3.0 Downloads/month (npm): 2 280 Downloads/week (npm): 428 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| npm registry (MCP servers) | Listed Version: 0.28.0 Downloads/month (npm): 3 443 Downloads/week (npm): 200 Forks (GitHub): 3 Stars (GitHub): 6 Not marked · First seen |
Listed Version: 1.3.0 Downloads/month (npm): 2 280 Downloads/week (npm): 428 Forks (GitHub): 0 Stars (GitHub): 0 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 | TwitterAPIs | io.github.chrischall/easytable-mcp |
|---|---|---|
| Marketplaces that list it | 2 | 2 |
| Stars (GitHub) (differs) | 6 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 3 (better) | 0 (worse) |
| Last release (differs) | 2026-11-06 (better) | 2026-11-04 (worse) |
| Where it runs (differs) | Remote server or your machine | On your machine (easytable-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 1 | 4, secrets among them: 0 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/twitterapis/twitterapis-mcp | github.com/chrischall/easytable-mcp |
| Changes in the last 7 days (differs) | 10 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 22 h ago, requires authentication | 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
TwitterAPIs
Official MCP server for twitterapis.com. Twitter/X search, users, DMs, Grok, monitoring and writes.
io.github.chrischall/easytable-mcp
easyTable restaurant reservations for Claude — availability, and create/modify/cancel bookings
How to run each
TwitterAPIs As a remote MCP server
claude mcp add --transport http twitterapis-mcp https://api.twitterapis.com/mcpRequires: TWITTERAPIS_KEY (secret)
io.github.chrischall/easytable-mcp As a local MCP server: npm package
claude mcp add --transport stdio easytable-mcp -- npx -y easytable-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only TwitterAPIs 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
Only TwitterAPIs asks for
TWITTERAPIS_BASE_URLTWITTERAPIS_KEY (secret)TWITTERAPIS_TIMEOUT_MS
Only io.github.chrischall/easytable-mcp asks for
EASYTABLE_DEBUGEASYTABLE_WS_PORTFETCHPROXY_IDENTITY_DIRFETCHPROXY_WS_HOST
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: TwitterAPIs · What it can do: io.github.chrischall/easytable-mcp · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). 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.