Lotlytics — US Real Estate Market Data & Investment Analytics
REMOTE · LOTLYTICS-MCP-PRODUCTION.UP.RAILWAY.APP · SCANNED SEP 21
US real estate market data for AI agents: prices, yields, forecasts and scores for 894 markets.
Available components
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 893 tokens (~127/item across 7 items; 5 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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'
{
"mcpServers": {
"us-lotlytics-lotlytics-mcp": {
"url": "https://lotlytics-mcp-production.up.railway.app/mcp"
}
}
} {
"servers": {
"us-lotlytics-lotlytics-mcp": {
"type": "http",
"url": "https://lotlytics-mcp-production.up.railway.app/mcp"
}
}
} [mcp_servers.us-lotlytics-lotlytics-mcp] url = "https://lotlytics-mcp-production.up.railway.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"us-lotlytics-lotlytics-mcp": {
"type": "remote",
"url": "https://lotlytics-mcp-production.up.railway.app/mcp",
"enabled": true
}
}
} openclaw mcp add us-lotlytics-lotlytics-mcp --url 'https://lotlytics-mcp-production.up.railway.app/mcp' --transport streamable-http
mcp_servers:
us-lotlytics-lotlytics-mcp:
url: "https://lotlytics-mcp-production.up.railway.app/mcp" {
"McpServers": {
"us-lotlytics-lotlytics-mcp": {
"Transport": "http",
"Url": "https://lotlytics-mcp-production.up.railway.app/mcp"
}
}
} assistant mcp add us-lotlytics-lotlytics-mcp -t streamable-http -u 'https://lotlytics-mcp-production.up.railway.app/mcp'
{
"mcpServers": {
"us-lotlytics-lotlytics-mcp": {
"type": "http",
"url": "https://lotlytics-mcp-production.up.railway.app/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 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
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +1
- 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 +1
- 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 +9
- 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
- 2 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
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 21 Sept 2026 · Probed https://lotlytics-mcp-production.up.railway.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.up.railway.app | CN=YE1,O=Let's Encrypt,C=US | 29 Jul 2026 | 27 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 6da79bb561da3efeb0e751ca21abd3999fe |
| SANs: *.up.railway.app, up.railway.app | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
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. | present | 23684 | 8 | Verified |
| railway.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
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 | Verified | 200 | |
| http (plaintext) | http://lotlytics-mcp-production.up.railway.app/mcp | HTTPS enforced | 301 | https://lotlytics-mcp-production.up.railway.app/mcp |
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.
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?
No. We connected to Lotlytics — US Real Estate Market Data & Investment… without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Lotlytics — US Real Estate Market Data & Investment… MCP server still maintained?
Lotlytics — US Real Estate Market Data & Investment… is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.