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

MapMyLot

https://mapmylot.com

Registry code: 049e4e1138a71b8f

api record

MapMyLot looks up land lots (parcels) from official cadastre data in Australia (QLD, NSW, VIC, TAS, ACT), New Zealand, Canada (BC, MB, NB, YK) and the UK (England, Wales, Scotland). Call mml_coverage to see what each area supports. mml_find_lot takes an address, lot/plan, UK postcode or coordinates and returns the lot and its row_id. mml_lot_facts then gives its area, frontage, planning and hazard layers and surroundings; mml_build_facts gives the facts that bear on building, without any verdict. Answers can be locked by the user's plan: a locked answer is unknown to you, never absent, so…

endpoint
https://mapmylot.com/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
_ is it live, free and safe measured by this hub
Is MapMyLot live?
Yes — it answered the hub's last check (checked 17h ago). It answered 100% of checks over the last 30 days.
Is MapMyLot free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does MapMyLot have?
11 tools: mml_find_lot, mml_save_lot, mml_lot_facts, mml_build_facts, mml_report_link, mml_watch, mml_unwatch, mml_coverage, ….
Is MapMyLot 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, 30 days
100%

90 days 100%· all time 100%

latency
1,340ms

last good check

priced tools
0

of 11 tools

_ answered our checks, 90 days 2 checks · signed record
  • unknown → live
_ 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

_ what it can do 11 tools
1 open3 auth-required 7 never probed 4 of 11 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.

  • mml_coverage open 17h ago

    Lists the areas MapMyLot covers, what each accepts (lot/plan, street address, postcode, coordinates), which planning and hazard layers are loaded, and the daily limits for each plan. Works without sign-in.

    mcp-tool

    {
      "type": "object",
      "title": "mml_coverageArguments",
      "properties": {
        "country": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Country",
          "default": null,
          "description": "Optional filter: AU, NZ, CA or UK, or an area code such as qld"
        }
      }
    }
    arguments 19 lines
  • mml_watches auth-required 17h ago

    Lists the lots and suburbs this account watches, each with its watch id and whether it is active or paused.

    mcp-tool

    {
      "type": "object",
      "title": "mml_watchesArguments",
      "properties": {}
    }
    arguments 5 lines
  • mml_compare_lots auth-required 17h ago

    Returns side-by-side facts for 2 to 10 lots: one row per lot with the same facts as the lot facts result, or that lot's error. Rows stay in the order given, or follow a requested sort (by area, frontage, layers found, constraint score and so on); sorted_by states the order used. The result is facts only, with no ranking of which lot is better. Each new lot counts toward the day's lookups. Requires a MapMyLot Pro plan.

    mcp-tool

    {
      "type": "object",
      "$defs": {
        "SortBy": {
          "type": "object",
          "title": "SortBy",
          "required": [
            "key"
          ],
          "properties": {
            "key": {
              "enum": [
                "area_m2",
                "perimeter_m",
                "frontage_m",
                "layers_present",
                "constraint_score",
                "unconstrained_area_m2",
                "suburb_percentile"
              ],
              "type": "string",
              "title": "Key"
            },
            "direction": {
              "enum": [
                "asc",
                "desc"
              ],
              "type": "string",
              "title": "Direction",
              "default": "asc",
              "description": "asc: smallest or fewest first; desc: largest or most first"
            }
          }
        }
      },
      "title": "mml_compare_lotsArguments",
      "properties": {
        "lots": {
          "anyOf": [
            {
              "type": "array",
              "items": {
                "anyOf": [
                  {
                    "type": "integer"
                  },
                  {
                    "type": "string"
                  }
                ]
              }
            },
            {
              "type": "null"
            }
          ],
          "title": "Lots",
          "default": null,
          "description": "2 to 10 lots: row_ids returned by the lot search, or addresses, lot/plans or coordinates"
        },
        "sort": {
          "anyOf": [
            {
              "type": "array",
              "items": {
                "$ref": "#/$defs/SortBy"
              },
              "maxItems": 4
            },
            {
              "type": "null"
            }
          ],
          "title": "Sort",
          "default": null,
          "description": "The facts the user asked to order the rows by, in turn, each with a direction, for example fewest layers_present first, then largest area_m2. Without it, the rows stay in the order given"
        },
        "saved": {
          "type": "boolean",
          "title": "Saved",
          "default": false,
          "description": "Compares the account's saved lots instead (up to 10, newest first)"
        }
      }
    }
    arguments 86 lines
  • mml_saved_lots auth-required 44h ago

    Lists the lots this account has saved on MapMyLot (the site's shortlist), newest first, with the stored fields and a link to each. Returns no lot facts. Spends no lookup.

    mcp-tool

    {
      "type": "object",
      "title": "mml_saved_lotsArguments",
      "properties": {}
    }
    arguments 5 lines
  • mml_find_lot unknown never probed

    Finds the land lot for an address, lot/plan, UK postcode, INSPIRE ID or coordinates. Returns the lot's MapMyLot id (row_id), lot/plan, area, perimeter, a point inside it, its outline as GeoJSON, a link to view it on mapmylot.com, and the data sources. In hosts that show apps the lot is also drawn on a map. Each new lot counts toward the account's daily MapMyLot lookups. Requires a free MapMyLot account.

    mcp-tool

    {
      "type": "object",
      "title": "mml_find_lotArguments",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "title": "Query",
          "maxLength": 200,
          "description": "A street address, a lot/plan (QLD and NSW, e.g. 2/RP213261 or Lot 2 DP236756), a UK postcode, 'INSPIRE ID <number>' (England and Wales), or decimal coordinates 'lat, lon'"
        }
      }
    }
    arguments 15 lines
  • mml_save_lot unknown never probed

    Saves a lot to the account's saved lots on MapMyLot, with an optional note. Saving the same lot again changes nothing. Saved lots are removed on mapmylot.com. Spends no lookup.

    mcp-tool

    {
      "type": "object",
      "title": "mml_save_lotArguments",
      "required": [
        "row_id"
      ],
      "properties": {
        "label": {
          "anyOf": [
            {
              "type": "string",
              "maxLength": 200
            },
            {
              "type": "null"
            }
          ],
          "title": "Label",
          "default": null,
          "description": "Optional short note to save with the lot"
        },
        "row_id": {
          "type": "integer",
          "title": "Row Id",
          "minimum": 1,
          "description": "The lot's row_id, as returned by the lot search or in the list of purchased reports"
        }
      }
    }
    arguments 29 lines
  • mml_lot_facts unknown never probed

    Returns facts about a lot by its row_id: area, perimeter, frontage, traditional custodians, a 0-100 constraint score, each planning and hazard layer checked on the lot (present or not, value, share of the lot), the unconstrained area, how its size compares with the suburb, distances to the coast, parks, water and transmission lines, elevation, and whether boundary files exist. A lot whose report the account bought has every answer, as on Pro. Layers checked on the lot but not included on the account's plan are listed in locked_layers; a locked layer is not absent. Spends no lookup.

    mcp-tool

    {
      "type": "object",
      "title": "mml_lot_factsArguments",
      "required": [
        "row_id"
      ],
      "properties": {
        "row_id": {
          "type": "integer",
          "title": "Row Id",
          "minimum": 1,
          "description": "The lot's row_id, as returned by the lot search or in the list of purchased reports"
        }
      }
    }
    arguments 15 lines
  • mml_build_facts unknown never probed

    Returns the facts about a lot that bear on building: area, frontage, zone (where zoning is loaded), planning and hazard constraints, unconstrained area, and slope and fall. The result is facts only, with no ruling on what can be built, and carries a caveat that the council decides. Spends no lookup.

    mcp-tool

    {
      "type": "object",
      "title": "mml_build_factsArguments",
      "required": [
        "row_id"
      ],
      "properties": {
        "row_id": {
          "type": "integer",
          "title": "Row Id",
          "minimum": 1,
          "description": "The lot's row_id, as returned by the lot search or in the list of purchased reports"
        }
      }
    }
    arguments 15 lines
  • mml_report_link unknown never probed

    Returns a permanent link to the MapMyLot PDF report for a lot when the account has bought that report or has a Pro plan; otherwise how the report is obtained. With no row_id, lists the reports this account has bought. Spends no lookup.

    mcp-tool

    {
      "type": "object",
      "title": "mml_report_linkArguments",
      "properties": {
        "row_id": {
          "anyOf": [
            {
              "type": "integer",
              "minimum": 1
            },
            {
              "type": "null"
            }
          ],
          "title": "Row Id",
          "default": null,
          "description": "The lot's row_id, as returned by the lot search. Without it, the account's purchased reports are listed"
        }
      }
    }
    arguments 20 lines
  • mml_watch unknown never probed

    Watches a lot, or the suburb it is in. MapMyLot emails the account holder when the public data about it changes, at most once a day. Watching the same lot or suburb again changes nothing. Requires a MapMyLot Pro plan.

    mcp-tool

    {
      "type": "object",
      "title": "mml_watchArguments",
      "required": [
        "row_id"
      ],
      "properties": {
        "scope": {
          "enum": [
            "lot",
            "suburb"
          ],
          "type": "string",
          "title": "Scope",
          "default": "lot",
          "description": "lot: this lot; suburb: the suburb this lot is in"
        },
        "row_id": {
          "type": "integer",
          "title": "Row Id",
          "minimum": 1,
          "description": "The lot's row_id, as returned by the lot search or in the list of purchased reports"
        }
      }
    }
    arguments 25 lines
  • mml_unwatch unknown never probed

    Stops a watch by its watch id. MapMyLot sends no more emails about that lot or suburb.

    mcp-tool

    {
      "type": "object",
      "title": "mml_unwatchArguments",
      "required": [
        "watch_id"
      ],
      "properties": {
        "watch_id": {
          "type": "integer",
          "title": "Watch Id",
          "minimum": 1,
          "description": "The watch id, as listed in the account's watches"
        }
      }
    }
    arguments 15 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 049e4e1138a71b8f.

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

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.