io.github.CloudCorpRecords/cedarlaw
NPM · @RENETURCIOS/CEDARLAW · 2 COMPONENTS
Lebanese legislation corpus: laws, articles, rulings and Gazette issues, verbatim.
Available components
Last scanned (12 hours ago)
Scores higher than 39% of npm servers
Category Education and Research
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2107 tokens (~210/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 18 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 17 Nov 26 53
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 21 Nov 2026 · Analysed npm/@reneturcios/cedarlaw@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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_article ~261
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 text is copied exactly from the database; nothing here is AI-written. Laws with ids from 2000000000 are ones the Lebanese University has not published yet, read by machine from scans of the Official Gazette's pages (unofficial copies, page images on the law's page); where the two readings differ the text shows both as ⟦reading one | reading two⟧: quote neither as certain. Not legal advice.
| Name | Type | Req | Description |
|---|---|---|---|
| law_id | integer | yes | the law's id (see get_law) |
| number | string | yes | the article's printed number, e.g. "212", "12 مكرر" or "586-1" (an article numbered under another; "586 (1)" works too) |
No output schema declared.
No examples provided.
get_gazette_issue ~57
Get one Official Gazette issue by id: its number, publication date, and the laws, decrees and decisions it published. Not legal advice.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | the issue's numeric id, from search_legislation |
No output schema declared.
No examples provided.
get_law ~188
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 text, or get_law_texts to read all of them. title_en is an unofficial English title (a model's rendering of the Arabic one); the Arabic title and text are official and more accurate. Not legal advice.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | the law's numeric id, from search_legislation or its URL |
No output schema declared.
No examples provided.
get_law_texts ~145
Get the verbatim texts of a law's articles in order, a page at a time: for each article its number, section_id, note, and the same text fields as get_article (text_ar in force today, text_fr, centre_text_ar when an amendment replaced the wording, version, repealed). Follow next_offset until it is absent to read the whole law. Amendment history stays in get_article. Not legal advice.
| Name | Type | Req | Description |
|---|---|---|---|
| law_id | integer | yes | the law's numeric id |
| limit | integer | – | articles per page, at most 200 |
| offset | integer | – | how many articles to skip (next_offset of the previous page) |
No output schema declared.
No examples provided.
get_links ~371
Get the graph edges into or out of one item: a law, an article, a ruling, an opinion, a research study or a Gazette issue. Use this to walk citations and amendments directly, instead of only what get_law and get_article attach automatically. For a law key ("law/<id>") the default scope "all" includes the edges of its articles too (each link keeps its real to_key, e.g. "law/244611/art/37"); scope "law" is the law itself only. Newest first by the date of the text each edge comes from; page with offset and next_offset, total is the number of edges. Not legal advice.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | "to" (edges that name this item as their target) or "from" (edges this item itself carries) |
| key | string | yes | the item's key: "law/<id>", "law/<id>/art/<number>", "ruling/<id>", "opinion/<id>", "research/<id>" or "gazette/<id>" |
| limit | integer | – | at most this many edges. quote is cut to 600 characters when longer (quote_truncated: true); get_article has the full wording |
| offset | integer | – | how many edges to skip (next_offset of the previous page) |
| order | string | – | by the date of the text the edge comes from (Gazette date, else issue date) |
| relation | string | – | narrow to one relation (e.g. "cites", "amend", "repeal"); omit for all |
| scope | string | – | for a law key only: "all" (default) adds the edges to or from its articles, "law" is the law itself only |
No output schema declared.
No examples provided.
get_ruling ~125
Get one court ruling (judgment) by id: court, number, date, panel, and its verbatim text when the Centre holds it as typed text. When available, pages returns the scanned judgment's machine reading, with low_confidence: true on hard-to-read pages where errors are expected. pdf_url is the full judgment's scan on the Lebanese University's site: always give it to the user with any answer about the ruling, so they can open the original. Not legal advice.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | the ruling's numeric id, from search_legislation |
No output schema declared.
No examples provided.
list_gazette_issues ~221
List Official Gazette issues by publication date, newest first, with the number of texts each carries (text_count) and where the issue comes from: source "centre" (the Lebanese University's Centre, whose issues stop about a year back) or "scans" (issues seen in Gazette scans, ids from 2000000000, which cover recent months). since and until accept YYYY, YYYY-MM or YYYY-MM-DD, inclusive; "everything since January 2025" is since "2025-01". Page with offset and next_offset. get_gazette_issue reads one issue's texts. Not legal advice.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | issues per page, at most 100 |
| offset | integer | – | how many issues to skip (next_offset of the previous page) |
| order | string | – | by publication date |
| since | string | – | first date, inclusive: YYYY, YYYY-MM or YYYY-MM-DD |
| until | string | – | last date, inclusive: YYYY, YYYY-MM or YYYY-MM-DD |
No output schema declared.
No examples provided.
list_legislation ~298
List laws, decrees and decisions by date, newest first: for "everything published since January 2025" call with since "2025-01". The date is the publication date: the Official Gazette date, else the issue date (each entry's date, with gazette_number, gazette_date and gazette_issue_id). Recent texts come from machine readings of Gazette scans (ids from 2000000000, unofficial) because the Lebanese University's Centre lags about a year, so a recent period lists mostly those. since and until accept YYYY, YYYY-MM or YYYY-MM-DD, inclusive. kind narrows to one kind, in Arabic ("قانون", "مرسوم") or English ("Law", "Decree"). Page with offset and next_offset; total is the whole count. Not legal advice.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | the kind of text, Arabic or English (e.g. "قانون" or "Law", "Decree") |
| limit | integer | – | texts per page, at most 100 |
| offset | integer | – | how many texts to skip (next_offset of the previous page) |
| order | string | – | by publication date |
| since | string | – | first date, inclusive: YYYY, YYYY-MM or YYYY-MM-DD (e.g. "2025-01") |
| until | string | – | last date, inclusive: YYYY, YYYY-MM or YYYY-MM-DD |
No output schema declared.
No examples provided.
possibly_affected ~72
Get the general repeals that may touch a law: earlier texts with a "all provisions contrary to this law are repealed" clause pointing at it. A list to check, never a finding that anything was actually repealed. Not legal advice.
| Name | Type | Req | Description |
|---|---|---|---|
| law_id | integer | yes | the law's numeric id |
No output schema declared.
No examples provided.
search_legislation ~369
Search Lebanese legislation (laws, decrees, decisions), their articles, court rulings, or Official Gazette issues, by keyword: Arabic words, French words (articles the Centre published in French, and the codes' French or English names), or a law's numeric id. Returns verbatim snippets from the Lebanese University's database, never an AI-written summary. A ruling hit's pdf_url is its full judgment's scan on the Lebanese University's site: always pass it on with any answer that cites the ruling. English words work too: they are read into Arabic through a glossary, matched against the unofficial English titles, and when nothing matches the result says what was searched instead (searched_instead). A code named in the query ("قانون العقوبات 670", "أصول محاكمات مدنية صورية") narrows the articles to that code; when none of its articles holds the other words, articles_not_in_code names it and the articles listed are from other texts. Each law carries title_en, an unofficial English title a model wrote from the Arabic title alone: the Arabic title and text are official and more accurate; cite the Arabic. A search of the gazette category with a bare year ("2025") lists that year's issues, and "22/2025" is issue 22 of 2025; to list texts by date use list_legislation instead. Not legal advice.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | narrow to one category; omit to search all four |
| limit | integer | – | results per category, at most 20 |
| query | string | yes | words to search for, Arabic, English or French, or a law's id |
| year | integer | – | only laws issued this year; for the gazette category, only issues published this year |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/cedarlaw MCP server?
io.github.CloudCorpRecords/cedarlaw runs locally as an npm package, launched with npx -y @reneturcios/cedarlaw mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @reneturcios/cedarlaw
claude mcp add cloudcorprecords-cedarlaw -- npx -y @reneturcios/cedarlaw mcp
What is the io.github.CloudCorpRecords/cedarlaw MCP server?
io.github.CloudCorpRecords/cedarlaw is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/cedarlaw. Lebanese legislation corpus: laws, articles, rulings and Gazette issues, verbatim. This page covers its npm package (@reneturcios/cedarlaw).
Is the io.github.CloudCorpRecords/cedarlaw MCP server safe to use?
io.github.CloudCorpRecords/cedarlaw scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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 io.github.CloudCorpRecords/cedarlaw MCP server expose?
io.github.CloudCorpRecords/cedarlaw exposes 10 tools: search_legislation, get_law, get_article, get_law_texts, get_ruling, and 5 more. Their descriptions and schemas cost roughly 2,107 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/cedarlaw MCP server still maintained?
io.github.CloudCorpRecords/cedarlaw is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.CloudCorpRecords/cedarlaw MCP server under?
io.github.CloudCorpRecords/cedarlaw declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.CloudCorpRecords/cedarlaw MCP server?
VerifyMCP ran 15 checks on io.github.CloudCorpRecords/cedarlaw, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.CloudCorpRecords/cedarlaw: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.