club.lity/lity
REMOTE · MCP.LITY.CLUB · SCANNED SEP 27
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 → 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 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 Usability80
- AI-judged instruction clarity (excellent).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 Management47
- Stability observed for 14 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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 club.lity/lity MCP server?
club.lity/lity is a hosted endpoint at https://mcp.lity.club/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.lity.club
claude mcp add --transport http club-lity-lity 'https://mcp.lity.club/mcp'
{
"mcpServers": {
"club-lity-lity": {
"url": "https://mcp.lity.club/mcp"
}
}
} {
"servers": {
"club-lity-lity": {
"type": "http",
"url": "https://mcp.lity.club/mcp"
}
}
} [mcp_servers.club-lity-lity] url = "https://mcp.lity.club/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"club-lity-lity": {
"type": "remote",
"url": "https://mcp.lity.club/mcp",
"enabled": true
}
}
} openclaw mcp add club-lity-lity --url 'https://mcp.lity.club/mcp' --transport streamable-http
mcp_servers:
club-lity-lity:
url: "https://mcp.lity.club/mcp" {
"McpServers": {
"club-lity-lity": {
"Transport": "http",
"Url": "https://mcp.lity.club/mcp"
}
}
} assistant mcp add club-lity-lity -t streamable-http -u 'https://mcp.lity.club/mcp'
{
"mcpServers": {
"club-lity-lity": {
"type": "http",
"url": "https://mcp.lity.club/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.
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 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
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 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.
- 18 Sept 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.
- 16 Sept 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.
- 15 Sept 26 0
- Server version: 1.0.3 → 1.0.5 functional
- 14 Sept 26 +1
- Stability: unverified → 0.03 ▲ 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 27 Sept 2026 · Probed https://mcp.lity.club/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.lity.club | CN=Amazon RSA 2048 M04,O=Amazon,C=US | 13 Sept 2026 | 29 Mar 2027 | RSA 2048 | SHA256-RSA | 34629a5063fd38cf0f91b8cce52ca45 |
| SANs: mcp.lity.club | ||||||
| CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 773124f2a952e3ed18a58bdb85d1bc0ce5f27 |
| 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 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.lity.club. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| club. | present | 54682 | 8 | Verified |
| lity.club. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.lity.club/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.lity.club/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 →
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.
What is the club.lity/lity MCP server?
club.lity/lity is an MCP server listed in the public MCP registry as club.lity/lity. AI legal copilot for foreigners in Spain: immigration and housing rental, cited to Spanish law. This page covers its hosted endpoint (https://mcp.lity.club/mcp).
Is the club.lity/lity MCP server safe to use?
club.lity/lity scores 72 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 club.lity/lity MCP server expose?
club.lity/lity exposes 2 tools: get_lity_info, submit_early_access_request. Their descriptions and schemas cost roughly 168 tokens of context every time the server is loaded.
Does the club.lity/lity MCP server require authentication?
No. We connected to club.lity/lity without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the club.lity/lity MCP server still maintained?
club.lity/lity is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.