_ registry / mcp streamable-http · checked 52m ago

myporta

https://www.myporta.ai

Registry code: 9cbc7fd240d4bfc8

api record

MyPorta searches homes for sale and to rent across the UK and has area guides for UK towns and villages. Prices are as advertised; a rent shows its period only when the advert states it. Homes found on an agent's own website link to that agent.

endpoint
https://www.myporta.ai/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 myporta live?
Yes — it answered the hub's last check (checked 52m ago). It answered 100% of checks over the last 30 days.
Is myporta free to use?
Yes — the hub reached it with no key and no payment.
What tools does myporta have?
4 tools: search_homes, compare_homes, get_area_guide, get_home.
Is myporta 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
77ms

last good check

priced tools
0

of 4 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 4 tools
4 never probed 0 of 4 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 unknown never probed

    Use this when the user wants to find homes for sale or to rent in the UK. Give a place (town, area or postcode) and any budget, bedrooms or type they mention. Put what they want from the home or area in their own words in `wishes` (for example "a garden", "walk to a station", "good primary schools nearby", "within 45 minutes of King's Cross"); homes are then ranked by fit, each with a 0-100 match score and the evidence behind it (station and school distances, advertised features). Put a physical feature they insist on and an advert would state ("garage", "annexe") in `must_haves`; anything about lifestyle or the area ("near the sea", "wild swimming", "good schools") always goes in `wishes`. Returns up to 10 homes with price, bedrooms, agent and a link, and for each home what is nearby: the nearest primary and secondary schools with their Ofsted grade, station, park, GP surgery, supermarket and broadband.

    mcp-tool

    {
      "type": "object",
      "required": [
        "place"
      ],
      "properties": {
        "sort": {
          "enum": [
            "best_match",
            "newest",
            "price_low",
            "price_high"
          ],
          "type": "string"
        },
        "limit": {
          "type": "integer",
          "maximum": 10,
          "minimum": 1,
          "description": "Default 6."
        },
        "place": {
          "type": "string",
          "description": "One UK place: a town, city, district, county, region, national park, National Landscape, named coast, island or postcode, e.g. \"Harrogate\", \"Dorset\", \"the Lake District\", \"the South West\", \"the south coast\", \"Jersey\", \"LS6\". Each is searched as one whole area. \"near Totnes\" takes in about 3 miles around it."
        },
        "wishes": {
          "type": "array",
          "items": {
            "type": "string",
            "maxLength": 200
          },
          "maxItems": 8,
          "description": "What the user wants, in their words. Homes are ranked by how well they match."
        },
        "max_beds": {
          "type": "integer",
          "maximum": 10,
          "minimum": 0
        },
        "min_beds": {
          "type": "integer",
          "maximum": 10,
          "minimum": 0
        },
        "max_price": {
          "type": "number",
          "description": "Pounds. For rent, per calendar month."
        },
        "min_price": {
          "type": "number",
          "description": "Pounds. For rent, per calendar month."
        },
        "must_haves": {
          "type": "array",
          "items": {
            "type": "string",
            "maxLength": 60
          },
          "maxItems": 6,
          "description": "A physical feature the advert must state word for word, e.g. \"garage\". Never lifestyle or area wishes: those go in wishes."
        },
        "buy_or_rent": {
          "enum": [
            "buy",
            "rent"
          ],
          "type": "string",
          "description": "Default buy."
        },
        "property_type": {
          "enum": [
            "house",
            "flat",
            "bungalow",
            "land",
            "park home",
            "room"
          ],
          "type": "string"
        }
      },
      "additionalProperties": false
    }
    arguments 83 lines
  • compare_homes unknown 52m ago

    Use this when the user wants to compare two to four homes from search_homes results side by side: price, rooms, key facts, nearby schools with their Ofsted grade, station, park, GP surgery, supermarket, broadband and agent. Takes the homes' ids.

    mcp-tool

    {
      "type": "object",
      "required": [
        "home_ids"
      ],
      "properties": {
        "home_ids": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "maxItems": 4,
          "minItems": 2,
          "description": "Ids from search_homes."
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
  • get_area_guide unknown 52m ago

    Use this when the user asks what a UK town, village or neighbourhood is like to live in. Returns MyPorta's area guide summary and a link to the full guide.

    mcp-tool

    {
      "type": "object",
      "required": [
        "place"
      ],
      "properties": {
        "place": {
          "type": "string",
          "description": "Town, village or neighbourhood name."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • get_home unknown 52m ago

    Use this when the user asks about one home from search_homes results: what the advert says, rooms, tenure, lease, service charge, ground rent, council tax band, EPC rating, parking, heating, nearby schools with their Ofsted grade, station, park, GP surgery, supermarket, broadband or agent. Takes the home's id.

    mcp-tool

    {
      "type": "object",
      "required": [
        "home_id"
      ],
      "properties": {
        "home_id": {
          "type": "string",
          "description": "The id from search_homes."
        }
      },
      "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 9cbc7fd240d4bfc8.

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

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.