Skip to content

landmine

tech.landmine/landminelandmine.techstreamable-httpv0.2.2Scanned

Known open GitHub issues in exact npm and PyPI versions, with workarounds, for coding agents.

2 tools: 1 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 1 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 2
  • Can send data out · 0
  • 1 finding

Anlyon alternative

1 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

2 tools

Changes things 1Claude Code: ask
  • landmine_checkCheck a JS/TS or Python code snippet against the open GitHub issues filed against the exact package versions it runs on.Reads text others write1 finding

    Why it is in this group

    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "landmine_check" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The input takes a statement or command to run (input.code), which can change anything it can reach.

      What this check looks for
    Description, as the server wrote it
    Check a JS/TS or Python code snippet against the open GitHub issues filed against the exact package versions it runs on. Returns each issue the code touches (by the APIs it calls), with the evidence and the best workaround from the thread (untrusted third-party text).

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 1Show 1 read-only tool
  • landmine_lookupLook up the open GitHub issues filed against exact npm or PyPI package versions, with no lockfile or scan needed.Reads text others writeNo findings

    Why it is in this group

    • The name "landmine_lookup" says "lookup": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "issue": it reads issues, which other people can write.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "landmine_check" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The input takes a statement or command to run (input.code), which can change anything it can reach.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.2.2. Values in angle brackets are yours to fill in.

claude mcp add --transport http landmine https://landmine.tech/mcp
claude mcp add --transport http landmine https://landmine.tech/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__landmine__landmine_lookup"
    ],
    "ask": [
      "mcp__landmine__landmine_check"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as landmine. Review it before you use it.

Capability tags behind 2 rules
  • mcp__landmine__landmine_lookup untrusted-input
  • mcp__landmine__landmine_check untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://anlyon.dev/api/v1/servers/tech.landmine/landmine/verify?hash=882e49eed95c1e24a72b97f70b59777c169353a0de6402fbe1139f1f84598abe" | jq -e '.changed == false'

Pinned hash 882e49eed95c, from Oct 24, 2026, 12:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/tech.landmine/landmine/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

anlyon.dev badge for tech.landmine/landmine
[![anlyon.dev](https://anlyon.dev/badge/tech.landmine/landmine.svg)](https://anlyon.dev/servers/tech.landmine/landmine)

Source: MCP Registry · repository. Synced Oct 24, 2026, 12:17 UTC.