# io.github.pocketlantern/pocketlantern (npm · @pocketlantern/mcp-server)

Blocker-aware decision layer for AI coding agents, grounded in source-linked, time-sensitive facts.

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

## Components

- npm · `@pocketlantern/mcp-server`: 79/100 (this document), [markdown](https://verifymcp.io/servers/pocketlantern-pocketlantern/pocketlantern-mcp-server.md), [page](https://verifymcp.io/servers/pocketlantern-pocketlantern/pocketlantern-mcp-server)

## Channel facts

- Registry: `npm`
- Package: `@pocketlantern/mcp-server`
- 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-04.

- **Supply Chain Security**: 83/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known medium-severity CVE affects hono 4.12.33, reached via @modelcontextprotocol/sdk > hono. A fixed version is available.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (97 of 101), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pocketlantern/pocketlantern).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 129 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 829 tokens (~103/item across 8 items; 8 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 pocketlantern-pocketlantern -- npx -y @pocketlantern/mcp-server
```

### Codex

```bash
codex mcp add pocketlantern-pocketlantern -- npx -y @pocketlantern/mcp-server
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add pocketlantern-pocketlantern --command npx --arg -y --arg @pocketlantern/mcp-server
```

### Hermes

```yaml
mcp_servers:
  pocketlantern-pocketlantern:
    command: "npx"
    args: ["-y", "@pocketlantern/mcp-server"]
```

### Other

```json
{
  "mcpServers": {
    "pocketlantern-pocketlantern": {
      "command": "npx",
      "args": [
        "-y",
        "@pocketlantern/mcp-server"
      ]
    }
  }
}
```

## 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-04 (score 79, +3)

- [security regression] CVE-2026-69207 affects this package: medium
- [security regression] Known CVEs: partial → fail
- [functional improvement] Stability: unverified → 0.27

### 2026-08-02 (score 76, +55)

- [security improvement] Provenance: unverified → pass
- [security improvement] Install scripts: unverified → pass
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Malware scan: unverified → pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [security] The attested source repository moved: pocketlantern/pocketlantern
- [functional regression] Security disclosure: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Schema quality: unverified → excellent
- [functional improvement] License: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] MCP protocol: unverified → pass
- [functional] First check of Schema quality: unverified
- [functional] Licence: MIT

### 2026-07-31 (score 21, −7)

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

### 2026-07-30 (score 28, −18)

- [security regression] Malware scan: pass → unverified

### 2026-07-27 (score 46)

First indexed and scored.

## MCP tools (8)

### `search_cards` (~291 tokens)

Before finalizing answers about technology choices, upgrades, migrations, licensing, or vendor selection — check this tool for blockers in these bundled decision cards. Your training data may be stale. Returns source-linked decision cards as of this bundle — surfacing EOL dates, breaking changes, version floors, lock-in risks (password export, vendor dependency), pricing model changes, and migration blockers. Includes source-linked blocker warnings where available. Use get_card for full details.

Input parameters:

- `constraints` (array): Narrow results by environment or operational needs (AND logic). Values: serverless, high-scale, low-ops, cost-sensitive, enterprise, small-team, monorepo, microservices, real-time, compliance.
- `include_blockers` (boolean): Include source-linked blocker warnings (EOL dates, breaking changes, lock-in, incompatibilities) linked to each result card when available. Default: true.
- `include_deprecated` (boolean): Include deprecated cards in results (default: false). Only set true when explicitly looking for outdated approaches.
- `limit` (integer): Maximum number of results (default: 5, max: 50)
- `query` (string, required): Natural-language problem or short topic query (e.g. 'auth for serverless', 'database migration'). Stopwords are filtered automatically.
- `tags` (array): Filter results to cards with these tags. Use list_tags to discover available values.

### `get_card` (~88 tokens)

Get the full content of a technology decision card by ID. Returns all candidate solutions with tradeoffs, cautions, and official reference links. Use after search_cards to deep-dive into a specific decision.

Input parameters:

- `id` (string, required): Card ID from search results (format: 'category/card-name', e.g. 'auth/jwt-vs-session'). Use search_cards first to find relevant IDs.

### `list_categories` (~40 tokens)

List available topic categories (auth, backend, database, frontend, infra, testing) with card counts. Call this first to understand what technology decisions are covered.

### `list_tags` (~64 tokens)

List all searchable tags with counts, optionally filtered by category. Use to discover available topics and refine search queries.

Input parameters:

- `category` (string): Optional: filter tags to a specific category (e.g. 'auth', 'backend', 'frontend'). Omit to see all tags.

### `list_constraints` (~41 tokens)

List environment constraints (serverless, enterprise, small-team, etc.) that can filter search results. Use when you know the project's environment and want only relevant cards.

### `get_cards` (~71 tokens)

Get full content of multiple cards by IDs in one call (max 5). Use instead of calling get_card repeatedly when you need to compare several candidates side by side.

Input parameters:

- `ids` (array, required): Array of card IDs to retrieve (max 5). Use after search_cards to fetch multiple cards in one call.

### `get_related_cards` (~68 tokens)

Get summaries of cards related to a given card. Use after reading a card to explore connected technology decisions (e.g. auth → OAuth flows → password hashing).

Input parameters:

- `id` (string, required): Card ID to find related cards for (format: 'category/card-name'). Returns summaries of connected topics.

### `report_issue` (~166 tokens)

Report a quality issue with PocketLantern cards. Use when: a topic has no card ('no_card'), a card has wrong facts ('inaccurate'), info seems outdated ('stale'), or the correct answer differs from the card ('answer_changed').

Input parameters:

- `card_id` (string): Card ID if the issue is about a specific card (e.g. 'auth/clerk-vs-auth0')
- `detail` (string): Brief description of what's wrong or what changed
- `issue_type` (string, required): Type of issue: 'no_card' (topic not covered), 'inaccurate' (wrong facts), 'stale' (outdated), 'answer_changed' (correct answer differs)
- `query` (string): The original search query that led to this issue

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/pocketlantern-pocketlantern/pocketlantern-mcp-server#diagnostics

## Score history

- 2026-08-04: 79
- 2026-08-03: 76
- 2026-08-02: 76
- 2026-08-01: 21
- 2026-07-31: 21
- 2026-07-30: 28
- 2026-07-28: 46
- 2026-07-27: 46

## Links

- npm package: https://www.npmjs.com/package/@pocketlantern/mcp-server
- Socket report: https://socket.dev/npm/package/@pocketlantern/mcp-server
- Repository: https://github.com/pocketlantern/pocketlantern
- Changelog RSS feed: https://verifymcp.io/servers/pocketlantern-pocketlantern/pocketlantern-mcp-server/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/pocketlantern-pocketlantern/pocketlantern-mcp-server/changelog.json
- HTML version of this page: https://verifymcp.io/servers/pocketlantern-pocketlantern/pocketlantern-mcp-server