# io.github.Fisher521/bookmarks-lifecycle (npm · bookmarks-lifecycle)

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

- Trust score: 73/100 (medium)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-16

## Components

- npm · `bookmarks-lifecycle`: 73/100 (this document), [markdown](https://verifymcp.io/servers/fisher521-bookmarks-lifecycle/bookmarks-lifecycle.md), [page](https://verifymcp.io/servers/fisher521-bookmarks-lifecycle/bookmarks-lifecycle)

## Channel facts

- Registry: `npm`
- Package: `bookmarks-lifecycle`
- Version: `0.2.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-16.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 30 of 98 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 10 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 79/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1469 tokens (~209/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 91/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 73% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add fisher521-bookmarks-lifecycle -- npx -y bookmarks-lifecycle
```

### Codex

```bash
codex mcp add fisher521-bookmarks-lifecycle -- npx -y bookmarks-lifecycle
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "fisher521-bookmarks-lifecycle": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "bookmarks-lifecycle"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add fisher521-bookmarks-lifecycle --command npx --arg -y --arg bookmarks-lifecycle
```

### Hermes

```yaml
mcp_servers:
  fisher521-bookmarks-lifecycle:
    command: "npx"
    args: ["-y", "bookmarks-lifecycle"]
```

### Other

```json
{
  "mcpServers": {
    "fisher521-bookmarks-lifecycle": {
      "command": "npx",
      "args": [
        "-y",
        "bookmarks-lifecycle"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-15 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-14 (score 72, +4)

- [functional improvement] Stability: unverified → 0.27

### 2026-08-11 (score 68, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-08-07 (score 67, +4)

- [security improvement] Known CVEs: partial → pass
- [functional] Dependency health: partial → 0.86

### 2026-08-06 (score 63)

First indexed and scored.

## MCP tools (7)

### `intake` (~180 tokens)

Pull in newly saved bookmarks

Scan browser bookmarks (via bookmarks-mcp) and merge them into the lifecycle: new URLs land in `inbox` with their real save date persisted; already-tracked ones get reconciled (sources, title). Never deletes a record — a URL missing from every source that was successfully scanned gets `sourceGone: true`, not removed. A source that failed to read (e.g. Safari without Full Disk Access) is never treated as confirming a URL is gone. Check `sourceStatus` in the response before assuming an empty result means nothing was found. This call may first persist lazy expiry/drip housekeeping (see README) even if you only meant to read.

Input parameters:

- `source` (string): Filter by browser ("chrome", "safari", "firefox", …) or a source id from bookmarks-mcp's list_sources. Omit for all.

### `today` (~110 tokens)

Today's pending layer

The 24-hour layer, oldest first — the actual to-do list. Each item includes `remainingMs` until it lapses on its own. `hasEverIntaken: false` means nothing has ever been scanned in (an empty pending list in that case means "you haven't started", not "you're caught up") — call `intake` first. This is where daily_triage starts. This call may first persist lazy expiry/drip housekeeping (see README) even if you only meant to read.

### `decide` (~377 tokens)

Judge one or more pending/watching items

MUTATING TOOL. Never call until the user has explicitly confirmed the exact item ids and action in the current turn, unless the MCP host has a trusted autonomous-approval mode enabled — silence, "looks good", or an earlier preference is not confirmation. Moves items to `kept` (keep permanently), `watching` (give it 30 more days), or `lapsed` (remove from the attention queue — this never deletes the browser bookmark or the lifecycle record, and is fully undoable via `undo`). From `pending`: keep/watch/drop all allowed. From `watching`: only `keep` (use `undo` to reverse a watch/drop decision instead of re-deciding an item that's already moved on). Anything else comes back as `not-decidable`. This call may first persist lazy expiry/drip housekeeping (see README) even if you only meant to read.

Input parameters:

- `action` (string, required): keep -> kept, watch -> watching (30d), drop -> lapsed
- `actorClaim` (string): Attribution claim only — this is NOT proof of user consent. This server has no way to verify who is really behind a call; omit this field unless you have a specific reason to claim "user" or "ai" (om…
- `ids` (array, required): One or more item ids, from today/list_layer output. Max 25 per call.
- `note` (string): Why — stored on the item and in its history, if given (this field is optional; omitting it is fine)

### `list_layer` (~145 tokens)

List one layer (paginated)

See what's in one layer — including `lapsed`, to answer 'what did I let go of'. Paginated: default limit 50, raise it only if you actually need more in one call (a large unpaginated layer can be megabytes of JSON, which will crowd out everything else in your context). `sourceGone: true` on an item means it's no longer found in any browser source that was successfully scanned (the record itself is never deleted). This call may first persist lazy expiry/drip housekeeping (see README) even if you only meant to read.

Input parameters:

- `layer` (string, required)
- `limit` (integer)
- `offset` (integer)

### `restore` (~222 tokens)

Bring a lapsed item back

MUTATING TOOL. Move one or more `lapsed` items back to `pending`, resetting their 24-hour clock. Only works on items currently `lapsed` — for `kept`/`watching` items that need reverting, use `undo` instead. This call may first persist lazy expiry/drip housekeeping (see README) even if you only meant to read.

Input parameters:

- `actorClaim` (string): Attribution claim only — this is NOT proof of user consent. This server has no way to verify who is really behind a call; omit this field unless you have a specific reason to claim "user" or "ai" (om…
- `ids` (array, required): One or more item ids, from today/list_layer output. Max 25 per call.

### `undo` (~365 tokens)

Undo a specific state change, by history event

MUTATING TOOL. Revert an item to whatever it was immediately before one of ITS OWN history events — this works for `kept` and `watching`, not just `lapsed` (that's what `restore` is for). Only an item's current LATEST event can be undone; anything else comes back as `not-latest-event`, showing you the actual latest one to target instead. Select events either with explicit `eventIds` (from any tool's `history[].eventId`), or with `filter` (by source id / time range / attribution) to batch-undo every matching item's latest event at once. Pass `preview: true` to see exactly what would change first. Undoing never erases history — it appends a new entry, so the full trail including undos stays intact. This call may first persist lazy expiry/drip housekeeping (see README) even if you only meant to read.

Input parameters:

- `actorClaim` (string): Attribution claim only — this is NOT proof of user consent. This server has no way to verify who is really behind a call; omit this field unless you have a specific reason to claim "user" or "ai" (om…
- `eventIds` (array): Specific history event ids to undo
- `filter` (object): Alternative to eventIds: undo every item's LATEST event matching these criteria
- `note` (string)
- `preview` (boolean): See what would be undone without changing anything

### `stats` (~70 tokens)

Lifecycle stats

Counts per layer, how many decisions landed today (local calendar day on the machine running this server — see README), and how much is still sitting in `inbox` waiting for its daily drip slot. This call may first persist lazy expiry/drip housekeeping (see README) even if you only meant to read.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/fisher521-bookmarks-lifecycle/bookmarks-lifecycle#diagnostics

## Score history

- 2026-08-16: 73
- 2026-08-15: 73
- 2026-08-14: 72
- 2026-08-13: 68
- 2026-08-12: 68
- 2026-08-11: 68
- 2026-08-10: 67
- 2026-08-09: 67
- 2026-08-08: 67
- 2026-08-07: 67
- 2026-08-06: 63

## Links

- npm package: https://www.npmjs.com/package/bookmarks-lifecycle
- Socket report: https://socket.dev/npm/package/bookmarks-lifecycle
- Repository: https://github.com/Fisher521/bookmarks-lifecycle
- Website: https://www.burn451.cloud/tools/bookmarks-lifecycle
- Changelog RSS feed: https://verifymcp.io/servers/fisher521-bookmarks-lifecycle/bookmarks-lifecycle.xml
- Changelog JSON feed: https://verifymcp.io/servers/fisher521-bookmarks-lifecycle/bookmarks-lifecycle.json
- HTML version of this page: https://verifymcp.io/servers/fisher521-bookmarks-lifecycle/bookmarks-lifecycle