CanLII MCP server
online · 100% uptimeMCP for CanLII: Canadian case law and legislation metadata (federal, provincial, territorial).
not scanned yet
6 stars
Reviews
Write oneNobody has reviewed CanLII yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
CanLII tools
Tool list not cached yet. `describe` through the gateway fetches it live.
How CanLII compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 85/100
- higher than 70% of 48,243 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 566 ms
- faster than 29% of 30,027 servers
- GitHub stars
- 6
- more than 85% of 28,706 servers
Release history: 2 versions in the registry since 2026-05-15, latest 2026-10-26, typically one every 164 days.
Install CanLII in Claude Code, Cursor or VS Code
claude mcp add --transport http canlii-mcp https://canlii-mcp.vaquill.ai/mcp
What the publisher says
From the CanLII repository's README, as published. We do not edit it. Read it on GitHub
canlii-mcp
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 /health route, and a hosted endpoint at canlii-mcp.vaquill.ai. Tools are unchanged.
Note: The CanLII API provides metadata only — titles, citations, dates, keywords, and citation relationships. Full document text is not available through the API.
Use the hosted endpoint (no install)
https://canlii-mcp.vaquill.ai/mcpThe hosted instance is public. No Vaquill token is required. Provide your own CanLII key one of two ways:
- Header (recommended, keeps the key out of the URL): X-CanLII-Token:
- URL parameter (simplest; works in header-less clients like the Claude Desktop connector UI and claude.ai web): append ?token= to the URL:
https://canlii-mcp.vaquill.ai/mcp?token=YOUR_CANLII_API_KEYApply for a key via the CanLII API request form. The server never stores your key, and there is no server-side fallback key, so every call counts against your own CanLII quota.
Claude Desktop / Claude Code
{
"mcpServers": {
"canlii": {
"url": "https://canlii-mcp.vaquill.ai/mcp",
"headers": {
"X-CanLII-Token": "YOUR_CANLII_API_KEY"
}
}
}
}Cursor / VS Code / Windsurf
Same pattern: any client supporting MCP streamable HTTP with custom headers works. For stdio-only clients use mcp-remote to proxy.
Authentication
Tools
Requirements
- Node.js 22+
- A CanLII API key — apply here
Usage
stdio via npx (quickest)
{
"mcpServers": {
"canlii": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@tomilashy/canlii-mcp"],
"env": {
"CANLII_API": "your_api_key"
}
}
}
}stdio (from source)
npm install
npm run build
node dist/index.jsAdd to your MCP config:
{
"mcpServers": {
"canlii": {
"command": "node",
"args": ["/path/to/canlii-mcp/dist/index.js"],
"env": {
"CANLII_API": "your_api_key"
}
}
}
}HTTP server
PORT=3000 CANLII_API=your_api_key node dist/index.js --transport httpShortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
CanLII: common questions
- Is CanLII MCP server safe?
- Yes, by our scan: it is graded A (85/100). Read the CanLII safety report
- How do I install CanLII?
- It runs remotely at canlii-mcp.vaquill.ai. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does CanLII need an API key?
- Yes. The registry entry asks for
Authorization,X-CanLII-Token. - Is CanLII maintained?
- The last commit was 52 days ago (2026-09-14). The latest release is v0.1.1.
- Is CanLII up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does CanLII compare with other MCP servers?
- safety score 85/100 (higher than 70% of 48,243 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 566 ms (faster than 29% of 30,027 servers). Full comparison.