_ registry / mcp http-sse · checked 47m ago

Lotlytics

https://lotlytics-mcp-production.up.railway.app

Registry code: 0fe772449cf24b0c

api record

You have access to Lotlytics real estate market data for 894 US cities and metros — https://www.lotlytics.us

Free tier covers the top 50 markets — no API key needed.

endpoint
https://lotlytics-mcp-production.up.railway.app/mcp
protocol
http-sse ·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 Lotlytics live?
Yes — it answered the hub's last check (checked 47m ago). It answered 100% of checks over the last 30 days.
Is Lotlytics free to use?
Yes — the hub reached it with no key and no payment.
What tools does Lotlytics have?
5 tools: get_market_summary, get_market_health, compare_markets, list_markets, search_markets.
Is Lotlytics 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
99.8%

90 days 99.7%· all time 99.7%

latency
286ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 611 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • get real estate market health score
  • get market summary for a us city
  • compare two housing markets
  • rank markets by investment criteria
takes → gives
text, data → data
tools
5 reads
_ 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 5 tools
2 open 3 never probed 2 of 5 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.

  • list_markets reads open 14h ago

    List the US markets this server can report on, optionally filtered to one state. Example: state='TX'

    mcp-tool

    {
      "type": "object",
      "title": "list_marketsArguments",
      "properties": {
        "state": {
          "type": "string",
          "title": "State",
          "default": "",
          "description": "Optional state filter, e.g. 'TX'. Omit for every available market."
        }
      }
    }
    arguments 12 lines
  • search_markets reads open 14h ago

    Rank US markets by investment criteria; no filters returns the top-ranked markets nationally. Requires API key (Investor plan) — https://www.lotlytics.us/pricing ; key at https://www.lotlytics.us/settings/api-keys Example: state='TX', max_price=300000, min_rental_yield=6

    mcp-tool

    {
      "type": "object",
      "title": "search_marketsArguments",
      "properties": {
        "limit": {
          "type": "integer",
          "title": "Limit",
          "default": 10,
          "description": "Markets to return, 1-25 (clamped). Default 10."
        },
        "state": {
          "type": "string",
          "title": "State",
          "default": "",
          "description": "Optional state filter, e.g. 'TX'. Omit = national, which samples only the first 20 markets."
        },
        "max_price": {
          "type": "number",
          "title": "Max Price",
          "default": 0,
          "description": "Max median price in dollars, e.g. 300000. 0 = no cap."
        },
        "min_appreciation": {
          "type": "number",
          "title": "Min Appreciation",
          "default": -999,
          "description": "Min YoY appreciation %, e.g. 3. Negatives allowed; -999 = no floor."
        },
        "min_rental_yield": {
          "type": "number",
          "title": "Min Rental Yield",
          "default": 0,
          "description": "Min gross rental yield %, e.g. 6. 0 = no floor."
        },
        "max_price_to_income": {
          "type": "number",
          "title": "Max Price To Income",
          "default": 999,
          "description": "Max price-to-income ratio, e.g. 4.5. 999 = no cap."
        }
      }
    }
    arguments 42 lines
  • get_market_summary reads unknown 11h ago

    Full market report for one US city or metro. Example: city='Austin', state='TX' returns Austin's median price, appreciation, rental yield, momentum and migration.

    mcp-tool

    {
      "type": "object",
      "title": "get_market_summaryArguments",
      "required": [
        "city",
        "state"
      ],
      "properties": {
        "city": {
          "type": "string",
          "title": "City",
          "description": "City or metro, e.g. 'Austin'. Case-insensitive."
        },
        "state": {
          "type": "string",
          "title": "State",
          "description": "US state, 2-letter or full, e.g. 'TX'. Required — city names repeat."
        }
      }
    }
    arguments 20 lines
  • get_market_health reads unknown 11h ago

    Investment health score (1-10) for a US market, with a label (Strong Buy / Favorable / Neutral / Caution / Avoid) and the signals behind it. Example: city='Tampa', state='FL'

    mcp-tool

    {
      "type": "object",
      "title": "get_market_healthArguments",
      "required": [
        "city",
        "state"
      ],
      "properties": {
        "city": {
          "type": "string",
          "title": "City",
          "description": "City or metro, e.g. 'Tampa'. Case-insensitive."
        },
        "state": {
          "type": "string",
          "title": "State",
          "description": "US state, 2-letter or full, e.g. 'FL'. Required — city names repeat."
        }
      }
    }
    arguments 20 lines
  • compare_markets reads unknown 14h ago

    Compare two US markets side by side, with a winner marked on price, yield and appreciation. Requires API key (Investor plan) — https://www.lotlytics.us/pricing ; key at https://www.lotlytics.us/settings/api-keys Example: city_a='Austin', state_a='TX', city_b='Nashville', state_b='TN'

    mcp-tool

    {
      "type": "object",
      "title": "compare_marketsArguments",
      "required": [
        "city_a",
        "state_a",
        "city_b",
        "state_b"
      ],
      "properties": {
        "city_a": {
          "type": "string",
          "title": "City A",
          "description": "First city or metro, e.g. 'Austin'."
        },
        "city_b": {
          "type": "string",
          "title": "City B",
          "description": "Second city or metro, e.g. 'Nashville'."
        },
        "state_a": {
          "type": "string",
          "title": "State A",
          "description": "State of the FIRST city, e.g. 'TX'."
        },
        "state_b": {
          "type": "string",
          "title": "State B",
          "description": "State of the SECOND city, e.g. 'TN'."
        }
      }
    }
    arguments 32 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 0fe772449cf24b0c.

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

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.