landmine
NPM · LANDMINES · 2 COMPONENTS
Known open GitHub issues in exact npm and PyPI versions, with workarounds, for coding agents.
Available components
Last scanned (7 hours ago)
Scores higher than 39% of npm servers
Category Code Search and Documentation
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 Security100
- 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
- 0 of 7 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 11 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 581 tokens (~145/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- 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 Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 82% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
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.
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.
- 25 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 24 Oct 26 55
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 5 Nov 2026 · Analysed npm/landmines@0.2.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 7 packages
| Packages resolved | 7 |
|---|---|
| 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 →
landmine_check Known bugs a file or snippet touches ~120
Check a source file (path) or a code snippet against open GitHub issues filed against the exact dependency versions this project pins. Returns each issue the code touches, the evidence it applies to the pinned version, and the best workaround from the thread (untrusted third-party text).
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | A code snippet, if there is no file yet |
| file | string | – | Path of a JS/TS or Python file (relative to the project or absolute) |
| language | string | – | Language of `code` (default js) |
No output schema declared.
No examples provided.
landmine_list List known bugs for the pinned versions ~52
List open GitHub issues filed against the exact versions this project pins, optionally for one package.
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | Include issues with no strong code symbol and feature requests |
| package | string | – | – |
No output schema declared.
No examples provided.
landmine_lookup Known open bugs in exact package versions ~196
Look up the open GitHub issues filed against exact npm or PyPI package versions, with no lockfile or scan needed. Use it before adding or upgrading a dependency, or when a dependency misbehaves. Each issue is checked to really name that version. Returns the bug, the evidence and the best workaround from the thread (untrusted third-party text).
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | – | Ecosystem for specs without == or a prefix (default npm) |
| packages | array | yes | Exact versions as your lockfile pins them: "next@16.4.0", "@tanstack/react-table@9.2.4", "pandas==2.3.1" (== means PyPI), or "pypi:requests@2.32.3". A bare name looks up the latest version. |
| query | string | – | An error message or API name: return only the issues that match it |
No output schema declared.
No examples provided.
landmine_search Search known bugs for the pinned versions ~81
Search open GitHub issues filed against the exact dependency versions this project pins, by error message, API name or keywords. Use it when something fails unexpectedly with a dependency.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| package | string | – | Limit to one dependency (npm or PyPI name) |
| query | string | yes | Error message, API name or keywords |
No output schema declared.
No examples provided.
How do I install the landmine MCP server?
landmine runs locally as an npm package, launched with npx -y landmines. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · landmines
claude mcp add tech-landmine-landmine -- npx -y landmines
What is the landmine MCP server?
landmine is an MCP server listed in the public MCP registry as tech.landmine/landmine. Known open GitHub issues in exact npm and PyPI versions, with workarounds, for coding agents. This page covers its npm package (landmines).
Is the landmine MCP server safe to use?
landmine scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 landmine MCP server expose?
landmine exposes 4 tools: landmine_check, landmine_search, landmine_list, landmine_lookup. Their descriptions and schemas cost roughly 449 tokens of context every time the server is loaded.
Is the landmine MCP server still maintained?
landmine is still listed as active in the MCP registry. We last reached this channel on 5 November 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 landmine MCP server under?
landmine declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.