CaseDaleel — UAE legal information
REMOTE · CASEDALEEL.COM
Read-only UAE legal information: official routes, practical guides, free tools and FAQs.
Available components
Last scanned (6 hours ago)
Scores higher than 89% of remote servers
Unreachable for 2 days in a row. Last reached 3 Nov 2026.
Category Education and Research
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- 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 not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- 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 we couldn't connect to verify it. 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.
- 4 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Stability: 0.73 → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 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.
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://casedaleel.com/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of casedaleel.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| casedaleel.com. | 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 |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://casedaleel.com/mcp | Unreachable | ||
| http (plaintext) | http://casedaleel.com/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 →
about_casedaleel About CaseDaleel ~56
What CaseDaleel is and is not (not a law firm, no referral commission, no outcome promise), who it is for, when a licensed advocate is needed, how to start, and how to contact it.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_guide Get a CaseDaleel guide ~74
Returns the full text (Markdown) of one published CaseDaleel guide or composite case study, by slug from list_guides, with its canonical URL and dates. Cite the URL when using it.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Guide slug, e.g. "uae-gratuity-calculation-basic-salary". |
No output schema declared.
No examples provided.
list_guides List CaseDaleel guides ~39
Lists CaseDaleel's published UAE legal preparation guides and clearly labelled fictional composite case studies, with titles, one-line summaries, dates and URLs.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_faq Search the CaseDaleel UAE legal FAQ ~134
Keyword search over CaseDaleel's published FAQ about UAE salary and gratuity, rent and eviction, cheques and debt, family matters, hiring a lawyer, and how the platform works. Returns matching questions and answers with the canonical page URL and the official authority to verify against. General information, not legal advice.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Answer language: en (English) or ar (Arabic). |
| limit | integer | – | Maximum number of results. |
| query | string | yes | What the user wants to know, in plain words, e.g. "unpaid salary deadline" or "Dubai eviction notice". |
No output schema declared.
No examples provided.
How do I install the CaseDaleel — UAE legal information MCP server?
CaseDaleel — UAE legal information is a hosted endpoint at https://casedaleel.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 · casedaleel.com
claude mcp add --transport http com-casedaleel-uae-legal-info 'https://casedaleel.com/mcp'
What is the CaseDaleel — UAE legal information MCP server?
CaseDaleel — UAE legal information is an MCP server listed in the public MCP registry as com.casedaleel/uae-legal-info. Read-only UAE legal information: official routes, practical guides, free tools and FAQs. This page covers its hosted endpoint (https://casedaleel.com/mcp).
Is the CaseDaleel — UAE legal information MCP server safe to use?
CaseDaleel — UAE legal information scores 84 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 CaseDaleel — UAE legal information MCP server expose?
CaseDaleel — UAE legal information exposes 4 tools: search_faq, list_guides, get_guide, about_casedaleel. Their descriptions and schemas cost roughly 303 tokens of context every time the server is loaded.
Does the CaseDaleel — UAE legal information MCP server require authentication?
Its publisher declares no required credentials for CaseDaleel — UAE legal information. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the CaseDaleel — UAE legal information MCP server still maintained?
CaseDaleel — UAE legal information is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 3 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.