_ registry / mcp http-sse · checked 1h ago

landmine

https://landmine.tech

Registry code: 81d8f09145bf8827

api record

landmine finds the open GitHub issues filed against exact npm and PyPI package versions, checks that each one really names that version, and returns the bug with the best workaround from the thread.

- Pass the exact versions the project pins (from package-lock.json, pnpm-lock.yaml, yarn.lock, bun.lock, uv.lock, poetry.lock or requirements.txt), not ranges.

endpoint
https://landmine.tech/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is landmine live?
Yes — it answered the hub's last check (checked 1h ago).
Is landmine free to use?
Yes — the hub reached it with no key and no payment.
What tools does landmine have?
2 tools: landmine_lookup, landmine_check.
Is landmine safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime
100%
latency
275ms

last good check

priced tools
0

of 2 tools

_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 2 tools
2 never probed 0 of 2 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • landmine_lookup unknown 1h ago

    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).

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "packages"
      ],
      "properties": {
        "query": {
          "type": "string",
          "maxLength": 2000,
          "description": "An error message or API name: return only the issues that match it"
        },
        "packages": {
          "type": "array",
          "items": {
            "type": "string",
            "maxLength": 214,
            "minLength": 1
          },
          "maxItems": 20,
          "minItems": 1,
          "description": "Exact versions as your lockfile pins them: \"[email protected]\", \"@tanstack/[email protected]\", \"pandas==2.3.1\" (== means PyPI), or \"pypi:[email protected]\". A bare name looks up the latest version."
        },
        "ecosystem": {
          "enum": [
            "npm",
            "pypi"
          ],
          "type": "string",
          "description": "Ecosystem for specs without == or a prefix (default npm)"
        }
      }
    }
    arguments 33 lines
  • landmine_check unknown 1h ago

    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).

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "code",
        "packages"
      ],
      "properties": {
        "code": {
          "type": "string",
          "maxLength": 100000,
          "minLength": 1,
          "description": "The code to check"
        },
        "language": {
          "enum": [
            "js",
            "py"
          ],
          "type": "string",
          "description": "Language of the code (default: py when the packages are PyPI, else js)"
        },
        "packages": {
          "type": "array",
          "items": {
            "type": "string",
            "maxLength": 214,
            "minLength": 1
          },
          "maxItems": 20,
          "minItems": 1,
          "description": "The dependencies the code uses. Exact versions as your lockfile pins them: \"[email protected]\", \"@tanstack/[email protected]\", \"pandas==2.3.1\" (== means PyPI), or \"pypi:[email protected]\". A bare name looks up the latest version."
        }
      }
    }
    arguments 35 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 81d8f09145bf8827.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/81d8f09145bf8827/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/81d8f09145bf8827/badge.svg)](https://brick.blue/agent/81d8f09145bf8827?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
60%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.