io.github.Vaquill-AI/canlii-mcp

MCPcommunitylive
v0.1.0io.github.Vaquill-AIUnknownUpdated 4mo agoGitHub

MCP for CanLII: Canadian case law and legislation metadata (federal, provincial, territorial).

An MCP (Model Context Protocol) server for the CanLII Canadian legal information API. Gives AI assistants access to Canadian case law and legislation metadata across all federal, provincial, and territorial jurisdictions. Forked from tomilashy/canlii-mcp. This fork adds bring-your-own-key (BYOK) auth, a route, and a hosted endpoint at . Tools are unchanged. Note: The CanLII API provides metadata…

Endpoint healthlive
checked 9 days ago · 565ms · auth required
100% of the last 5 checks reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
5GitHub stars
1Forks
4mo agoLast update
Package
Authorio.github.Vaquill-AI
LicenseUnknown
Version0.1.0
Sourcemcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface7 tools · none privileged
Security scan✓ CleanvHEAD · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

7 tools · none privileged
Statically extracted from the published packagevHEAD · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

list_case_databasesNo description published

This tool published no description. Forge does not invent one.

list_casesNo description published

This tool published no description. Forge does not invent one.

get_caseNo description published

This tool published no description. Forge does not invent one.

get_case_citationsNo description published

This tool published no description. Forge does not invent one.

list_legislation_databasesNo description published

This tool published no description. Forge does not invent one.

list_legislationNo description published

This tool published no description. Forge does not invent one.

get_legislationNo description published

This tool published no description. Forge does not invent one.

0 of 7 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

An MCP (Model Context Protocol) server for the CanLII Canadian legal information API. Gives AI assistants access to Canadian case law and legislation metadata across all federal, provincial, and territorial jurisdictions. Forked from tomilashy/canlii-mcp. This fork adds bring-your-own-key (BYOK) auth, a route, and a hosted endpoint at . Tools are unchanged. Note: The CanLII API provides metadata only — titles, citations, dates, keywords, and citation relationships. Full document text is not…

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.