_ registry / mcp streamable-http · checked 13h ago

landfiller-commander

https://landfiller.app

Registry code: bd2d1ad138ae65ed

api record

Search for a commander, then build a mana base. Budget is USD, not cents. Preserve all returned warnings and color-coverage deficits. Prices and recommendations are estimates. Shopping URLs open a list; they do not purchase cards. Builds are previews and are not saved publicly.

endpoint
https://landfiller.app/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
137ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

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.

  • build_mana_base unknown 13h ago

    Generate 30–42 lands for a Commander within a USD purchase budget, optionally with acceleration. Returns card quantities, reasoning, prices, coverage, warnings, and shopping links. Preview only: no saved build, email, purchase, or cart modification. Shopping imports match by card name; printing and final prices may differ. Always show warnings rather than describing a deficient build as optimal.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "commanderName"
  ],
  "properties": {
    "bracket": {
      "type": "integer",
      "default": 3,
      "maximum": 5,
      "minimum": 1
    },
    "budgetUsd": {
      "type": "number",
      "default": 100,
      "maximum": 10000,
      "minimum": 20
    },
    "landCount": {
      "type": "integer",
      "default": 37,
      "maximum": 42,
      "minimum": 30
    },
    "commanderName": {
      "type": "string",
      "maxLength": 200,
      "minLength": 1
    },
    "excludedCards": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 200,
        "minLength": 1
      },
      "default": [],
      "maxItems": 100
    },
    "includeAcceleration": {
      "type": "boolean",
      "default": false
    }
  }
}
    arguments 46 lines
  • search_commanders unknown 13h ago

    Find Commander candidates by name. The existing autocomplete may include non-commander cards; only the primary field is validated as a legendary creature. Use the exact commander name for build_mana_base.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "maxLength": 100,
      "minLength": 2
    }
  }
}
    arguments 14 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 bd2d1ad138ae65ed.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/bd2d1ad138ae65ed/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/bd2d1ad138ae65ed/badge.svg)](https://brick.blue/agent/bd2d1ad138ae65ed?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.