club.lity/lity
REMOTE · 8P5DMRJZL1.EXECUTE-API.EU-NORTH-1.AMAZONAWS.COM · SCANNED AUG 3
AI legal copilot for foreigners in Spain: immigration and housing rental, cited to Spanish law.
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 →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 245 tokens (~122/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · 8p5dmrjzl1.execute-api.eu-north-1.amazonaws.com
claude mcp add --transport http club-lity-lity https://8p5dmrjzl1.execute-api.eu-north-1.amazonaws.com/poc/mcp
[mcp_servers.club-lity-lity] url = "https://8p5dmrjzl1.execute-api.eu-north-1.amazonaws.com/poc/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"club-lity-lity": {
"type": "remote",
"url": "https://8p5dmrjzl1.execute-api.eu-north-1.amazonaws.com/poc/mcp",
"enabled": true
}
}
} openclaw mcp add club-lity-lity --url https://8p5dmrjzl1.execute-api.eu-north-1.amazonaws.com/poc/mcp --transport streamable-http
mcp_servers:
club-lity-lity:
url: "https://8p5dmrjzl1.execute-api.eu-north-1.amazonaws.com/poc/mcp" {
"mcpServers": {
"club-lity-lity": {
"type": "http",
"url": "https://8p5dmrjzl1.execute-api.eu-north-1.amazonaws.com/poc/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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 −2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Jul 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.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 62
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 3 Aug 2026 · Probed https://8p5dmrjzl1.execute-api.eu-north-1.amazonaws.com/poc/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.execute-api.eu-north-1.amazonaws.com | CN=Amazon RSA 2048 M01,O=Amazon,C=US | 13 Jan 2026 | 10 Feb 2027 | RSA 2048 | SHA256-RSA | 4f6fd457d5553ddace221984a837ccc |
| SANs: *.execute-api.eu-north-1.amazonaws.com | ||||||
| CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 77312380b9d6688a33b1ed9bf9ccda68e0e0f |
| CN=Amazon Root CA 1,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 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
DNSSEC insecure
Validation of 8p5dmrjzl1.execute-api.eu-north-1.amazonaws.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| amazonaws.com. | 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 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://8p5dmrjzl1.execute-api.eu-north-1.amazonaws.com/poc/mcp | Verified | 200 | |
| http (plaintext) | http://8p5dmrjzl1.execute-api.eu-north-1.amazonaws.com/poc/mcp | HTTPS enforced | 301 | https://8p5dmrjzl1.execute-api.eu-north-1.amazonaws.com/poc/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.
get_lity_info About Lity ~37
What Lity is, coverage (Spain: immigration/extranjería, housing rental), languages, access status and links. Read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
submit_early_access_request Request early access to Lity ~131
Register the user for Lity early access (waitlist). Call ONLY after the user explicitly agreed to share their name and email with Lity; pass consent=true to confirm. Free during early access.
| Name | Type | Req | Description |
|---|---|---|---|
| consent | boolean | yes | MUST be true: the user explicitly agreed to share these details with Lity |
| string | yes | User's email | |
| language | string | — | Preferred language |
| message | string | — | Optional: what legal issue to help with |
| name | string | yes | User's name |
| role | string | — | Who the user is (default client) |
No output schema declared.
No examples provided.