Ext Ops Panel
Open dashboard
Comparison

TimeBase vs Clear MCP

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). Clear MCP is an MCP server published by mcp-dir. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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

Where each is published
MarketplaceTimeBaseClear MCP
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

TimeBase vs Clear MCP
FactTimeBaseClear MCP
Marketplaces that list it (differs)3 (better)1 (worse)
Stars (GitHub) (differs)8 (better)0 (worse)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)On your machine (timebase-mcp)Remote server (api.mcp.ai/p_clear)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)16, secrets among them: 6Not published
Parts of the bundle (differs)8Not a bundle
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/epam/timebase-mcpgithub.com/mcp-dir/clear-mcp
Changes in the last 7 days (differs)20
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 2 h ago

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

In its own words, on Official MCP Registry:

Explore and query TimeBase streams, schemas, QQL, symbols, and server status via MCP.

Clear MCP

In its own words, on Official MCP Registry:

Connect your Clear account to AI via Brazil's Open Finance: balances, statements, cards, investments

How to run each

TimeBase As a local MCP server: PyPI package

Claude Code
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-mcp

Requires: TIMEBASE_OAUTH2_CLIENT_SECRET (secret), TIMEBASE_PASSWORD (secret)

Clear MCP As a remote MCP server

Claude Code
claude mcp add --transport http clear-mcp https://api.mcp.ai/p_clear

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Clear MCP 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 Clear MCP publish no settings it asks for, so we do not compare settings.

What it can do: TimeBase · What it can do: Clear MCP · 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.

Where the data comes from: how the catalog is built