io.github.pocketlantern/pocketlantern
NPM · @POCKETLANTERN/MCP-SERVER · SCANNED SEP 20
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 → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 98 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- 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 176 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability82
- 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 Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.pocketlantern/pocketlantern MCP server?
io.github.pocketlantern/pocketlantern runs locally as an npm package, launched with npx -y @pocketlantern/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pocketlantern/mcp-server
claude mcp add pocketlantern-pocketlantern -- npx -y @pocketlantern/mcp-server
{
"mcpServers": {
"pocketlantern-pocketlantern": {
"command": "npx",
"args": [
"-y",
"@pocketlantern/mcp-server"
]
}
}
} {
"servers": {
"pocketlantern-pocketlantern": {
"command": "npx",
"args": [
"-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": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@pocketlantern/mcp-server"
]
}
}
} assistant mcp add pocketlantern-pocketlantern -t stdio -c npx -a -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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −3
- Stability: pass → 0.80 functional
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 20 Sept 2026 · Analysed npm/@pocketlantern/mcp-server@0.2.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| 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 |
Background: How many MCP packages publish verified provenance →
Dependencies 98 packages
| Packages resolved | 98 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
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.
What is the io.github.pocketlantern/pocketlantern MCP server?
io.github.pocketlantern/pocketlantern is an MCP server listed in the public MCP registry as io.github.pocketlantern/pocketlantern. Blocker-aware decision layer for AI coding agents, grounded in source-linked, time-sensitive facts. This page covers its npm package (@pocketlantern/mcp-server).
Is the io.github.pocketlantern/pocketlantern MCP server safe to use?
io.github.pocketlantern/pocketlantern scores 95 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.pocketlantern/pocketlantern MCP server expose?
io.github.pocketlantern/pocketlantern exposes 8 tools: search_cards, get_card, list_categories, list_tags, list_constraints, and 3 more. Their descriptions and schemas cost roughly 829 tokens of context every time the server is loaded.
Is the io.github.pocketlantern/pocketlantern MCP server still maintained?
io.github.pocketlantern/pocketlantern is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.pocketlantern/pocketlantern MCP server under?
io.github.pocketlantern/pocketlantern declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.