mcp-registry/com.lebaneselegislation/mcp · v1.1.0
As of 2026-10-27 15:05 UTC, the Lebaneselegislation MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Search and read Lebanese laws, articles, court rulings and the Official Gazette, verbatim.
Point your MCP client at this streamable-http endpoint: https://lebaneselegislation.com/mcp
10 of 10 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
In the last 30 days: 0 tool(s) removed and 5 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.lebaneselegislation%2Fmcp/fixes
{
"name": "get_article",
"description": "Get one article's verbatim Arabic text as in force today (and French, when the Centre published it and no amendment has replaced it), its in-force status, amendment history, and the canonical and source URLs. When an amendment replaced the wording, text_ar is the new wording and centre_text_ar the earlier one the Centre's site still shows. centre_error, when present, notes an error in the Centre's own text (one article repeating another, a stray letter); the text itself is left as published. The",
"inputSchema": {
"type": "object",
"required": [
"law_id",
"number"
],
"properties": {
"law_id": {
"type": "integer",
"description": "the law's id (see get_law)"
},
"number": {
"type": "string",
"description": "the article's printed number, e.g. \"212\", \"12 مكرر\" or \"586-1\" (an article numbered under another; \"586 (1)\" works too)"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_gazette_issue",
"description": "Get one Official Gazette issue by id: its number, publication date, and the laws, decrees and decisions it published. Not legal advice.",
"inputSchema": {
"type": "object",
"required": [
"id"
],
"properties": {
"id": {
"type": "integer",
"description": "the issue's numeric id, from search_legislation"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_law",
"description": "Get a law, decree or similar text's metadata (kind, number, date, status), its table of contents (the chapters: id, parent_id, depth, heading), its articles in order (number, and the section_id of the chapter each sits under) and the texts it amended or was amended by (amended_by / amended: one entry per text and relation, with articles listing the articles of this law it touches, or of the other law for amended; no articles means the whole law). Use get_article to read one article's verbatim te",
"inputSchema": {
"type": "object",
"required": [
"id"
],
"properties": {
"id": {
"type": "integer",
"description": "the law's numeric id, from search_legislation or its URL"
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.lebaneselegislation/mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.lebaneselegislation/mcp"}) over MCP.
get_links ~487 tokenslist_legislation ~350 tokenslist_gazette_issues ~315 tokenssearch_legislation ~305 tokensget_article ~239 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.lebaneselegislation%2Fmcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.lebaneselegislation%2Fmcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.lebaneselegislation%2Fmcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.lebaneselegislation%2Fmcp.svg :target: https://glimind.com/server/mcp-registry%2Fcom.lebaneselegislation%2Fmcp?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:bef32f2400414e58…, first seen 2026-10-27, included at leaf 79846 of 79,969. Version history · verify what your client received.
Compare: most reliable retrieval servers · most reliable knowledge servers · most reliable search servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-27 15:05 UTC, the Lebaneselegislation MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Lebaneselegislation MCP server advertises 10 tools, including get_article, get_gazette_issue, get_law, get_law_texts, get_links.
Point your MCP client at this streamable-http endpoint: https://lebaneselegislation.com/mcp
Glimind scanned all 10 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.