Straply
REMOTE · MCP.STRAPLY.COM
Live U.S. property data: 147M homes, ZIP market stats, daily listing changes, address lookup.
Available components
Last scanned (15 hours ago)
Scores higher than 59% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Maps and Location
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 Security74
- 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1035 tokens (~172/item across 6 items; 6 tools + 0 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 Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- “search_properties” added an optional parameter “confirmedWithinHours” cosmetic
- 16 Nov 26 +37
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 100 functional
- 13 Nov 26 33
First indexed and scored.
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 Nov 2026 · Probed https://mcp.straply.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=straply.com | CN=WE1,O=Google Trust Services,C=US | 13 Nov 2026 | 11 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | de034bdb6db91b0d0e2e138f643ad9fe |
| SANs: straply.com, mcp.straply.com, *.mcp.straply.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.straply.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| straply.com. | No DS | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.straply.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.straply.com/mcp | HTTPS enforced | 301 | https://mcp.straply.com/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 →
get_change_summary Market change summary ~104
Get counts of U.S. market events over the last 1-30 days (new listings, price cuts and increases, sales, relistings, delistings), without returning individual properties. If the result has a 'note', pass it on to the user. Cheap — use this before get_recent_changes to size a question, or to answer 'how active is the market right now?'
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | How many days of changes to summarize |
No output schema declared.
No examples provided.
get_market_stats ZIP market stats ~121
Get a market snapshot for a ZIP code: homes for sale (active and coming soon) with the median asking price and median price per square foot, overall and by property type; rentals with the median monthly rent; sales in the last 12 months with the median sale price where sale prices are public; and the number of off-market homes. Use this for market-level questions like 'how's the market in 90210?' or 'how many homes are for sale in 78704?'
| Name | Type | Req | Description |
|---|---|---|---|
| zip_code | string | yes | Five-digit ZIP code |
No output schema declared.
No examples provided.
get_property Get property ~112
Get a single property by its Straply ID (an opaque string like 'stp_x7Kd9Qm2Rb', as returned by search_properties). Returns the full property record including address, price, beds/baths, square footage, year built, lot size, property type, listing status, price history (all listing/sale/price-change events), and tax history.
| Name | Type | Req | Description |
|---|---|---|---|
| property_id | string | yes | Straply property ID (e.g. 'stp_x7Kd9Qm2Rb') |
No output schema declared.
No examples provided.
get_recent_changes Recent market changes ~264
Get recent market changes: new listings, price cuts, price increases, homes that just sold, went pending, fell through, came back on the market, or were delisted. Filter by state, ZIP, or change type. Each event carries the Straply property ID, so follow up with get_property for full details and history. Use this for questions like 'what just sold in Austin?', 'any price cuts in 90210 this week?', or 'show me new listings in Texas'.
| Name | Type | Req | Description |
|---|---|---|---|
| changeType | string | – | Filter to one kind of change. Omit for all market events. Comma-separate for several (e.g. 'price_cut,just_sold'). |
| days | integer | – | How many days of changes to include (1 = the most recent day) |
| includeAll | boolean | – | Include non-market data churn (mostly reference-price movement on off-market homes). Off by default — it is ~76% of raw changes and is rarely what a question is about. |
| limit | integer | – | Max events to return (default 50) |
| offset | integer | – | Pagination offset |
| state | string | – | Two-letter state code (e.g. 'CA') |
| zipCode | string | – | Five-digit ZIP code |
No output schema declared.
No examples provided.
lookup_property_by_address Look up property by address ~98
Find a property by street address and ZIP code. Use this when you know the address but not the Straply ID. Returns the full property record.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | City name (optional, improves matching) |
| state | string | – | Two-letter state code (optional) |
| street | string | yes | Street address (e.g. '1005 Benedict Canyon Dr') |
| zipCode | string | yes | Five-digit ZIP code |
No output schema declared.
No examples provided.
search_properties Search properties ~258
Search for real estate properties by ZIP code, city, state, status, property type, price range, bedrooms, bathrooms, and more. Returns up to 25 properties per call with address, price, beds, baths, square footage, year built, listing status, and price history.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | City name |
| confirmedWithinHours | integer | – | Only homes whose on-market status was confirmed within this many hours (e.g. 48). Each result's market.listing_confirmed_at says when. |
| limit | integer | – | Results per page (1-100, default 25) |
| maxBeds | integer | – | Maximum bedrooms |
| maxPrice | integer | – | Maximum price filter |
| minBeds | integer | – | Minimum bedrooms |
| minPrice | integer | – | Minimum price filter |
| offset | integer | – | Pagination offset |
| order | string | – | Sort direction |
| propertyType | string | – | Property type filter |
| sort | string | – | Sort field |
| state | string | – | Two-letter state code (e.g. 'CA') |
| status | string | – | Listing status filter |
| zipCode | string | – | Five-digit ZIP code (e.g. '90210') |
No output schema declared.
No examples provided.
How do I install the Straply MCP server?
Straply is a hosted endpoint at https://mcp.straply.com/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 · mcp.straply.com
claude mcp add --transport http com-straply-straply 'https://mcp.straply.com/mcp'
What is the Straply MCP server?
Straply is an MCP server listed in the public MCP registry as com.straply/straply. Live U.S. property data: 147M homes, ZIP market stats, daily listing changes, address lookup. This page covers its hosted endpoint (https://mcp.straply.com/mcp).
Is the Straply MCP server safe to use?
Straply scores 73 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 Straply MCP server expose?
Straply exposes 6 tools: search_properties, get_property, lookup_property_by_address, get_market_stats, get_recent_changes, get_change_summary. Their descriptions and schemas cost roughly 957 tokens of context every time the server is loaded.
Does the Straply MCP server require authentication?
No. We connected to Straply without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Straply MCP server still maintained?
Straply is still listed as active in the MCP registry. We last reached this channel on 21 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 Straply MCP server?
VerifyMCP ran 13 checks on Straply, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.