Lotlytics — US Real Estate Market Data & Investment Analytics
REMOTE · LOTLYTICS-MCP-PRODUCTION.UP.RAILWAY.APP
US real estate market data for AI agents: prices, yields, forecasts and scores for 894 markets.
Available components
Last scanned (15 hours ago)
Scores higher than 97% of remote servers
Unreachable for 1 day in a row. Last reached 4 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (3)
- HTTPS
- DNSSEC
- Transport
Checks we could not complete (8)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- TLS certificate in Endpoint SecurityTLS not yet verified: we couldn't open a connection to check the certificate.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HSTS header in Endpoint SecurityHSTS not yet verified: we couldn't read the response headers to check for it.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Sept 26 0
- Tool “get_market_summary” rewrote its description, which is the text the model reads security
- 10 Sept 26 0
- Stability: 0.97 → pass security
- 5 Sept 26 0
- Tool “compare_markets” rewrote its description, which is the text the model reads security
- Tool “get_market_health” rewrote its description, which is the text the model reads security
- Tool “get_market_summary” rewrote its description, which is the text the model reads security
- Tool “list_markets” rewrote its description, which is the text the model reads security
- Tool “search_markets” rewrote its description, which is the text the model reads security
- Schema quality: 142 → 127 ▲ functional
- “get_market_health” reworded the description of “city” cosmetic
- “get_market_health” reworded the description of “state” cosmetic
- “get_market_summary” reworded the description of “city” cosmetic
- “get_market_summary” reworded the description of “state” cosmetic
- “list_markets” reworded the description of “state” cosmetic
- “search_markets” reworded the description of “max_price” cosmetic
- “search_markets” reworded the description of “max_price_to_income” cosmetic
- “search_markets” reworded the description of “min_appreciation” cosmetic
- “search_markets” reworded the description of “min_rental_yield” cosmetic
- “search_markets” reworded the description of “state” cosmetic
- 4 Sept 26 0
- Tool “compare_markets” rewrote its description, which is the text the model reads security
- Tool “get_market_health” rewrote its description, which is the text the model reads security
- Tool “get_market_summary” rewrote its description, which is the text the model reads security
- Tool “list_markets” rewrote its description, which is the text the model reads security
- Tool “search_markets” rewrote its description, which is the text the model reads security
- Schema quality: 195 → 142 ▲ functional
- “compare_markets” reworded the description of “city_a” cosmetic
- “compare_markets” reworded the description of “city_b” cosmetic
- “compare_markets” reworded the description of “state_a” cosmetic
- “compare_markets” reworded the description of “state_b” cosmetic
- “get_market_health” reworded the description of “city” cosmetic
- “get_market_health” reworded the description of “state” cosmetic
- “get_market_summary” reworded the description of “city” cosmetic
- “get_market_summary” reworded the description of “state” cosmetic
- “list_markets” reworded the description of “state” cosmetic
- “search_markets” reworded the description of “limit” cosmetic
- “search_markets” reworded the description of “max_price” cosmetic
- “search_markets” reworded the description of “max_price_to_income” cosmetic
- “search_markets” reworded the description of “min_appreciation” cosmetic
- “search_markets” reworded the description of “min_rental_yield” cosmetic
- “search_markets” reworded the description of “state” cosmetic
- 3 Sept 26 0
- Authorization: unverified → partial ▲ security
- Tool “compare_markets” rewrote its description, which is the text the model reads security
- Tool “get_market_health” rewrote its description, which is the text the model reads security
- Tool “get_market_summary” rewrote its description, which is the text the model reads security
- Tool “list_markets” rewrote its description, which is the text the model reads security
- Tool “search_markets” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Tool coverage: 0% → 100% ▲ functional
- Schema quality: good → excellent functional
- “compare_markets” reworded the description of “city_a” cosmetic
- “compare_markets” reworded the description of “city_b” cosmetic
- “compare_markets” reworded the description of “state_a” cosmetic
- “compare_markets” reworded the description of “state_b” cosmetic
- “get_market_health” reworded the description of “city” cosmetic
- “get_market_health” reworded the description of “state” cosmetic
- “get_market_summary” reworded the description of “city” cosmetic
- “get_market_summary” reworded the description of “state” cosmetic
- “list_markets” reworded the description of “state” cosmetic
- “search_markets” reworded the description of “limit” cosmetic
- “search_markets” reworded the description of “max_price” cosmetic
- “search_markets” reworded the description of “max_price_to_income” cosmetic
- “search_markets” reworded the description of “min_appreciation” cosmetic
- “search_markets” reworded the description of “min_rental_yield” cosmetic
- “search_markets” reworded the description of “state” cosmetic
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://lotlytics-mcp-production.up.railway.app/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of lotlytics-mcp-production.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| app. | DS published | 23684 | 8 | Verified |
| railway.app. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://lotlytics-mcp-production.up.railway.app/mcp | Unreachable | ||
| http (plaintext) | http://lotlytics-mcp-production.up.railway.app/mcp | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
compare_markets Compare two markets head-to-head ~163
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'
| Name | Type | Req | Description |
|---|---|---|---|
| city_a | string | yes | First city or metro, e.g. 'Austin'. |
| city_b | string | yes | Second city or metro, e.g. 'Nashville'. |
| state_a | string | yes | State of the FIRST city, e.g. 'TX'. |
| state_b | string | yes | State of the SECOND city, e.g. 'TN'. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_market_health Investment health score (1-10) ~105
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'
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | City or metro, e.g. 'Tampa'. Case-insensitive. |
| state | string | yes | US state, 2-letter or full, e.g. 'FL'. Required — city names repeat. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_market_summary Market summary for a US city ~91
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.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | City or metro, e.g. 'Austin'. Case-insensitive. |
| state | string | yes | US state, 2-letter or full, e.g. 'TX'. Required — city names repeat. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_markets List available markets ~55
List the US markets this server can report on, optionally filtered to one state. Example: state='TX'
| Name | Type | Req | Description |
|---|---|---|---|
| state | string | – | Optional state filter, e.g. 'TX'. Omit for every available market. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
search_markets Search markets by investment criteria ~244
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
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Markets to return, 1-25 (clamped). Default 10. |
| max_price | number | – | Max median price in dollars, e.g. 300000. 0 = no cap. |
| max_price_to_income | number | – | Max price-to-income ratio, e.g. 4.5. 999 = no cap. |
| min_appreciation | number | – | Min YoY appreciation %, e.g. 3. Negatives allowed; -999 = no floor. |
| min_rental_yield | number | – | Min gross rental yield %, e.g. 6. 0 = no floor. |
| state | string | – | Optional state filter, e.g. 'TX'. Omit = national, which samples only the first 20 markets. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the Lotlytics — US Real Estate Market Data & Investment… MCP server?
Lotlytics — US Real Estate Market Data & Investment… is a hosted endpoint at https://lotlytics-mcp-production.up.railway.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · lotlytics-mcp-production.up.railway.app
claude mcp add --transport http us-lotlytics-lotlytics-mcp 'https://lotlytics-mcp-production.up.railway.app/mcp'
What is the Lotlytics — US Real Estate Market Data & Investment… MCP server?
Lotlytics — US Real Estate Market Data & Investment… is an MCP server listed in the public MCP registry as us.lotlytics/lotlytics-mcp. US real estate market data for AI agents: prices, yields, forecasts and scores for 894 markets. This page covers its hosted endpoint (https://lotlytics-mcp-production.up.railway.app/mcp).
Is the Lotlytics — US Real Estate Market Data & Investment… MCP server safe to use?
Lotlytics — US Real Estate Market Data & Investment… scores 89 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Lotlytics — US Real Estate Market Data & Investment… MCP server expose?
Lotlytics — US Real Estate Market Data & Investment… exposes 5 tools: get_market_summary, list_markets, get_market_health, compare_markets, search_markets. Their descriptions and schemas cost roughly 658 tokens of context every time the server is loaded.
Does the Lotlytics — US Real Estate Market Data & Investment… MCP server require authentication?
Its publisher declares no required credentials for Lotlytics — US Real Estate Market Data & Investment…. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Lotlytics — US Real Estate Market Data & Investment… MCP server still maintained?
Lotlytics — US Real Estate Market Data & Investment… is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Lotlytics — US Real Estate Market Data & Investment… MCP server?
VerifyMCP ran 3 checks on Lotlytics — US Real Estate Market Data & Investment…, covering HTTPS, DNSSEC and Transport. 8 items could not be completed, a gap on our side rather than a finding about Lotlytics — US Real Estate Market Data & Investment…: TLS certificate, Authorization, HSTS header, Schema quality and 4 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.