Is the Lebaneselegislation MCP server down?

mcp-registry/com.lebaneselegislation/mcp · v1.1.0

healthy
Last checked 2026-10-27 15:05 UTC · handshake 309ms

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.

uptime (30d checks)
100%
checks observed
3,060
outages (90d)
0
tools
10

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

Agent-readiness: B (84/100)

B (84/100): 0 error(s), 1 warning(s) across 10 tool(s); ~2,500 tokens of tool definitions.
Scores higher than 42% of 15,808 MCP servers Glimind has audited.
Its tool list costs an agent ~2,500 tokens per session — more than 50% of servers.
85 → 84 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints30
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability80

What to fix (3)

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 →

Tools: get_article, get_gazette_issue, get_law, get_law_texts, get_links and 5 more

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 →

Auto-fix: 9 corrected tool definitions

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

get_article 1 change
{
  "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
  }
}
get_gazette_issue 1 change
{
  "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
  }
}
get_law 1 change
{
  "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 alerted

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.

Passed

Largest tool definitions

Static 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:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.lebaneselegislation%2Fmcp.svg)](https://glimind.com/server/mcp-registry%2Fcom.lebaneselegislation%2Fmcp?ref=badge)
HTML
<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>
reStructuredText
.. 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

Tool-definition log

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.

Tools (10)

Compare: most reliable retrieval servers · most reliable knowledge servers · most reliable search servers

Know before your agent calls it

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.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

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"
    }
  }
}

FAQ

Is the Lebaneselegislation MCP server down right now?

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.

How many tools does Lebaneselegislation MCP server provide?

Lebaneselegislation MCP server advertises 10 tools, including get_article, get_gazette_issue, get_law, get_law_texts, get_links.

How do I install Lebaneselegislation MCP server?

Point your MCP client at this streamable-http endpoint: https://lebaneselegislation.com/mcp

Is the Lebaneselegislation MCP server safe to connect to an AI agent?

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.

Operator of Lebaneselegislation MCP server?

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.

Feedback
Help us improve