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

l50-property

https://property.l50automation.com

Registry code: 0accf9da57af7a04

api record

UK property data by area for AI agents: Land Registry sold prices by property type with yearly change, EPC energy ratings and police.uk crime per postcode district, and EPC rating shares by council. Area-level only. Paid per call with x402 in USDC on Base. Paid tools cost a few cents each in USDC on Base via x402; bad input is refused for free and failed calls are not charged. All L50 tools in one server: https://api.l50automation.com/mcp

endpoint
https://property.l50automation.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 l50-property live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is l50-property free to use?
Yes — the hub reached it with no key and no payment.
What tools does l50-property have?
2 tools: epc_areas, property_area.
Is l50-property 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
364ms

last good check

priced tools
0

of 2 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

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.

  • epc_areas unknown 1h ago

    Energy-rating (EPC) statistics for one council in England or Wales: share of homes or commercial buildings rated A to G, per postcode district. Area-level only, no addresses. Costs $0.05 per call, paid in USDC on Base with x402.

    mcp-tool

    {
  "type": "object",
  "required": [
    "council"
  ],
  "properties": {
    "months": {
      "type": "integer",
      "maximum": 60,
      "minimum": 1
    },
    "council": {
      "type": "string",
      "description": "Council name, e.g. Bristol, Manchester, Cornwall"
    },
    "groupBy": {
      "enum": [
        "postcode_district",
        "council",
        "constituency"
      ],
      "type": "string"
    },
    "buildingType": {
      "enum": [
        "domestic",
        "non_domestic"
      ],
      "type": "string"
    },
    "minCertificates": {
      "type": "integer",
      "maximum": 1000,
      "minimum": 1
    }
  }
}
    arguments 37 lines
  • property_area unknown 1h ago

    UK property report for one postcode district in England or Wales: Land Registry sold prices by property type with change on the previous period, EPC energy ratings and police.uk crime. Area-level, no addresses. Costs $0.05 per call, paid in USDC on Base with x402.

    mcp-tool

    {
  "type": "object",
  "required": [
    "district"
  ],
  "properties": {
    "crime": {
      "type": "boolean",
      "description": "Include crime (default true)"
    },
    "energy": {
      "type": "boolean",
      "description": "Include EPC energy ratings (default true)"
    },
    "months": {
      "type": "integer",
      "maximum": 36,
      "minimum": 3,
      "description": "Period in months, compared with the same period before (default 12)"
    },
    "district": {
      "type": "string",
      "pattern": "^[A-Za-z]{1,2}[0-9][A-Za-z0-9]?( ?[0-9][A-Za-z]{2})?$",
      "description": "Postcode district like M20 or BS9 (a full postcode works too)"
    }
  }
}
    arguments 27 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 0accf9da57af7a04.

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

_ also on l50automation.com 5 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.