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

houses-with-land

https://houseswithland.co.uk

Registry code: a1b90f671c164a1c

api record

Search UK houses with land and manage your private saved-homes board.

from a public catalogue that lists it, not from the operator

endpoint
https://houseswithland.co.uk/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 houses-with-land live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is houses-with-land free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does houses-with-land have?
6 tools: board_update, get_home, home_buyer_questions, board_save, search_homes, board_list.
Is houses-with-land 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
803ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 1 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 6 tools
1 open1 auth-required 4 never probed 2 of 6 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.

  • search_homes open 1h ago

    Search currently available houses with land. Logged-out. Uses the same eligible inventory and filters as /for-sale/.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "q": {
      "type": "string",
      "maxLength": 80,
      "description": "keywords matched against title, county, town and summary"
    },
    "kind": {
      "enum": [
        "bungalow",
        "cottage",
        "smallholding",
        "house",
        "croft",
        "equestrian",
        ""
      ],
      "type": "string"
    },
    "limit": {
      "type": "integer",
      "default": 10,
      "maximum": 24,
      "minimum": 1
    },
    "region": {
      "type": "string",
      "description": "county or nation slug, e.g. shropshire, devon, wales"
    },
    "max_price": {
      "type": "integer",
      "maximum": 10000000,
      "minimum": 0
    },
    "min_price": {
      "type": "integer",
      "maximum": 10000000,
      "minimum": 0
    },
    "min_bedrooms": {
      "type": "integer",
      "maximum": 20,
      "minimum": 1
    },
    "min_plot_acres": {
      "type": "number",
      "maximum": 1000,
      "minimum": 0
    }
  },
  "additionalProperties": false
}
    arguments 54 lines
  • board_list auth-required 1h ago

    List the caller's private saved-homes board. Requires Bearer token.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {},
  "additionalProperties": false
}
    arguments 6 lines
  • board_update unknown never probed

    Move a saved home between stages or edit private notes. Requires Bearer token. Stages: saved, researching, viewing, shortlist, offer, passed.

    mcp-tool

    {
  "type": "object",
  "required": [
    "saved_id",
    "stage"
  ],
  "properties": {
    "notes": {
      "type": "string",
      "maxLength": 2000
    },
    "stage": {
      "enum": [
        "saved",
        "researching",
        "viewing",
        "shortlist",
        "offer",
        "passed"
      ],
      "type": "string"
    },
    "saved_id": {
      "type": "integer",
      "minimum": 1
    }
  },
  "additionalProperties": false
}
    arguments 29 lines
  • get_home unknown 1h ago

    Full public detail for one home: price, land, source, evidence, save link. Logged-out. Only rights-cleared published homes resolve.

    mcp-tool

    {
  "type": "object",
  "required": [
    "property_id"
  ],
  "properties": {
    "property_id": {
      "type": "integer",
      "minimum": 1,
      "description": "stable numeric id, e.g. the 1 in /homes/slug-1"
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • home_buyer_questions unknown never probed

    The 20 rural buyer due-diligence questions for one home, with only source-checked answers filled in. Missing coverage is reported as unassessed, never asserted.

    mcp-tool

    {
  "type": "object",
  "required": [
    "property_id"
  ],
  "properties": {
    "property_id": {
      "type": "integer",
      "minimum": 1
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • board_save unknown never probed

    Save an available home to the caller's board. Requires Bearer token.

    mcp-tool

    {
  "type": "object",
  "required": [
    "property_id"
  ],
  "properties": {
    "property_id": {
      "type": "integer",
      "minimum": 1
    }
  },
  "additionalProperties": false
}
    arguments 13 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 a1b90f671c164a1c.

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