Cool property search server!
REMOTE · SUB1.FIND-ME.CASA
Non functional server (yet)
Available components
Last scanned (9 hours ago)
Scores higher than 8% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Communication
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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 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 & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 402. 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.
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.
- 3 Nov 26 −37
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.03 → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 2 Nov 26 −13
- Stability: pass → 0.03 functional
- 1 Nov 26 +50
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 3 Oct 26 −37
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.03 → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 2 Oct 26 60
- Stability: unverified → 0.03 ▲ functional
- 1 Oct 26 0
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Schema quality: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → good ▲ functional
- First check of Tool coverage: 0 functional
- First check of Destructive annotations: 0 functional
- First check of Tool coverage: 100 functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day 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
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://sub1.find-me.casa
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=sub1.find-me.casa | CN=Amazon ECDSA 256 M04,O=Amazon,C=US | 27 Oct 2026 | 12 May 2027 | ECDSA 256 | ECDSA-SHA256 | ab5b34e9a4d000dff2df3a2af4ec929 |
| SANs: sub1.find-me.casa | ||||||
| CN=Amazon ECDSA 256 M04,O=Amazon,C=US (CA) | CN=Amazon Root CA 3,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | ECDSA 256 | ECDSA-SHA256 | 7731272b752ac8adccb0a3027f7dfec18424a |
| CN=Amazon Root CA 3,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | ECDSA 256 | SHA256-RSA | 67f944a30cfcc4f74b5f5306e54d3b7be0ac3 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of sub1.find-me.casa. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| casa. | present | 60588 | 13 | Verified |
| find-me.casa. | absent | 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 |
|---|---|
| HTTP status | 402 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://sub1.find-me.casa | HTTP error | 402 | |
| http (plaintext) | http://sub1.find-me.casa | HTTPS enforced | 301 | https://sub1.find-me.casa/ |
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 →
send_email ~127
Send an email via Resend API. Args: sender_email: Sender email address (must be verified in Resend) to_emails: List of recipient email addresses subject: Email subject line text_content: Plain text content (required if html_content not provided) html_content: HTML content (required if text_content not provided) Returns: API response with email ID on success
| Name | Type | Req | Description |
|---|---|---|---|
| html_content | – | – | – |
| sender_email | string | yes | – |
| subject | string | yes | – |
| text_content | – | – | – |
| to_emails | array | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Cool property search server! MCP server?
Cool property search server! is a hosted endpoint at https://sub1.find-me.casa/, 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 · sub1.find-me.casa
claude mcp add --transport http casa-find-me-sub1-send-email-mcp 'https://sub1.find-me.casa/'
What is the Cool property search server! MCP server?
Cool property search server! is an MCP server listed in the public MCP registry as casa.find-me.sub1/send-email-mcp. Non functional server (yet). This page covers its hosted endpoint (https://sub1.find-me.casa).
Is the Cool property search server! MCP server safe to use?
Cool property search server! scores 23 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 Cool property search server! MCP server expose?
Cool property search server! exposes 1 tool: send_email. Their descriptions and schemas cost roughly 127 tokens of context every time the server is loaded.
Does the Cool property search server! MCP server require authentication?
Its publisher declares that Cool property search server! requires credentials, so you will need to authorise it in your MCP client. We have not been able to confirm that against the live endpoint.
Is the Cool property search server! MCP server still maintained?
Cool property search server! is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.