Ext Ops Panel
Open dashboard
Comparison

io.github.Fisher521/bookmarks-lifecycle vs Timebook

io.github.Fisher521/bookmarks-lifecycle is an MCP server published by Fisher521. Marketplaces we read that list it: 1 (Official MCP Registry). Timebook is an MCP server published by squidcode. 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

Where each is published
Marketplaceio.github.Fisher521/bookmarks-lifecycleTimebook
Official MCP Registry Listed
Version: 0.2.0
Downloads/month (npm): 151
Downloads/week (npm): 27
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.6.0
Downloads/month (npm): 217
Downloads/week (npm): 40
Forks (GitHub): 0
Stars (GitHub): 2
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

io.github.Fisher521/bookmarks-lifecycle vs Timebook
Factio.github.Fisher521/bookmarks-lifecycleTimebook
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)2 (better)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)On your machine (bookmarks-lifecycle)Remote server (usetimebook.com/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 0
LicenceNot statedNot stated
Repository (differs)github.com/fisher521/bookmarks-lifecyclegithub.com/squidcode/timebook-cli
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 9 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

io.github.Fisher521/bookmarks-lifecycle

In its own words, on Official MCP Registry:

Bookmarks on a decision clock: 24 hours to decide, 30 days to watch, or keep. Never deletes.

Timebook

In its own words, on Official MCP Registry:

Track time on usetimebook.com - start/stop timers, log entries, list projects/clients.

How to run each

io.github.Fisher521/bookmarks-lifecycle As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio bookmarks-lifecycle -- npx -y bookmarks-lifecycle

Timebook As a remote MCP server

Claude Code
claude mcp add --transport http timebook https://usetimebook.com/mcp

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

Only Timebook 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 io.github.Fisher521/bookmarks-lifecycle publish no settings it asks for, so we do not compare settings.

What it can do: io.github.Fisher521/bookmarks-lifecycle · What it can do: Timebook · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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