TimeBase vs three.ws Provenance
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). three.ws Provenance is an MCP server published by nirholas. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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 |  three.ws Provenance |
|---|---|---|
| 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.3 Downloads/month (npm): 197 Downloads/week (npm): 61 Forks (GitHub): 65 Stars (GitHub): 239 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 | three.ws Provenance |
|---|---|---|
| Marketplaces that list it (differs) | 3 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 8 (worse) | 239 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 65 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (timebase-mcp) | On your machine (@three-ws/provenance-mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 16, secrets among them: 6 | 4, secrets among them: 2 |
| 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/nirholas/three.ws |
| Changes in the last 7 days (differs) | 2 | 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.
three.ws Provenance
Append-only, signed, on-chain-verifiable agent action log — record and audit what agents did.
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)
three.ws Provenance As a local MCP server: npm package
claude mcp add --env "THREE_WS_SIGNER_KEY=<YOUR_THREE_WS_SIGNER_KEY>" --env "THREE_WS_TOKEN=<YOUR_THREE_WS_TOKEN>" --transport stdio provenance-mcp -- npx -y @three-ws/provenance-mcpRequires: THREE_WS_SIGNER_KEY (secret), THREE_WS_TOKEN (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
Only TimeBase asks for
DXAPI_SSL_CERT_FILEDXAPI_SSL_TERMINATIONDXAPI_SSL_TRUST_ALLMCP_AUTH_API_KEYS_FILEMCP_AUTH_AUDIENCEMCP_AUTH_PUBLIC_URLMCP_HOSTMCP_LOG_LEVELMCP_PORTTIMEBASE_AUTH_MODETIMEBASE_HTTP_URLTIMEBASE_OAUTH2_CLIENT_ID (secret)
Show the remaining 9
TIMEBASE_OAUTH2_CLIENT_SECRET (secret)TIMEBASE_OAUTH2_SCOPE (secret)TIMEBASE_OAUTH2_TOKEN_PARAMS (secret)TIMEBASE_OAUTH2_TOKEN_URL (secret)TIMEBASE_PASSWORD (secret)TIMEBASE_READ_ONLYTIMEBASE_SERVERSTIMEBASE_URLTIMEBASE_USERNAME
Only three.ws Provenance asks for
THREE_WS_BASETHREE_WS_SIGNER_KEY (secret)THREE_WS_TIMEOUT_MSTHREE_WS_TOKEN (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: TimeBase · What it can do: three.ws Provenance · 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.