io.github.pocketlantern/pocketlantern
NPM · @POCKETLANTERN/MCP-SERVER · SCANNED AUG 3
Blocker-aware decision layer for AI coding agents, grounded in source-linked, time-sensitive facts.
Available components
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. How we score →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (97 of 101), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (97 of 101), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pocketlantern/pocketlantern). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 128 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 829 tokens (~103/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @pocketlantern/mcp-server
claude mcp add pocketlantern-pocketlantern -- npx -y @pocketlantern/mcp-server
codex mcp add pocketlantern-pocketlantern -- npx -y @pocketlantern/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"pocketlantern-pocketlantern": {
"type": "local",
"command": [
"npx",
"-y",
"@pocketlantern/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add pocketlantern-pocketlantern --command npx --arg -y --arg @pocketlantern/mcp-server
mcp_servers:
pocketlantern-pocketlantern:
command: "npx"
args: ["-y", "@pocketlantern/mcp-server"] {
"mcpServers": {
"pocketlantern-pocketlantern": {
"command": "npx",
"args": [
"-y",
"@pocketlantern/mcp-server"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Aug 26 +55
- Install scripts: unverified → pass ▲ security
- Provenance: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- 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 security
- Security disclosure: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: unverified → excellent ▲ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: unverified functional
- Licence: MIT functional
- 31 Jul 26 −7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 27 Jul 26 46
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Analysed npm/@pocketlantern/[email protected]
Provenance verified
Ecosystem: npm · Outcome: verified
Reason: verified
- Source repo:
- pocketlantern/pocketlantern
- Certificate issuer:
- https://token.actions.githubusercontent.com
- Certificate SAN:
- https://github.com/pocketlantern/pocketlantern/.github/workflows/release.yml@refs/heads/main
- Rekor log index:
- 1189273434
- Predicate type:
- https://slsa.dev/provenance/v1
- Subject digest:
- sha512:56e0841213a932b9d1053c60743f9f4c1231b52c4b8696103ef96cee819127e47d501b2c8ee589d32c1917f19f38278ce7becb412ebce76913b75b732
- Discovery method:
- attestation_endpoint
Dependencies 97 packages
97 packages in the resolved dependency tree · 95 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
get_card ~88
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Card ID from search results (format: 'category/card-name', e.g. 'auth/jwt-vs-session'). Use search_cards first to find relevant IDs. |
No output schema declared.
No examples provided.
get_cards ~71
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | array | yes | Array of card IDs to retrieve (max 5). Use after search_cards to fetch multiple cards in one call. |
No output schema declared.
No examples provided.
get_related_cards ~68
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).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Card ID to find related cards for (format: 'category/card-name'). Returns summaries of connected topics. |
No output schema declared.
No examples provided.
list_categories ~40
List available topic categories (auth, backend, database, frontend, infra, testing) with card counts. Call this first to understand what technology decisions are covered.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_constraints ~41
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_tags ~64
List all searchable tags with counts, optionally filtered by category. Use to discover available topics and refine search queries.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | — | Optional: filter tags to a specific category (e.g. 'auth', 'backend', 'frontend'). Omit to see all tags. |
No output schema declared.
No examples provided.
report_issue ~166
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').
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 |
No output schema declared.
No examples provided.
search_cards ~291
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.