Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Legis-Link is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
8
tools declared
remote
at its publisher
—
calls last 7d
What it does
Compliance answers for 10 construction trades in AU, UK, US, CA and EU: codes, licensing, RAMS.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http legis-link-mcp https://legis-link.com/mcp
# 2 — ask your agent for something these tools do
# check_compliance, get_code_reference, list_supported_regions and 5 more
Legis-Link costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
LLAll 1 server
legis-link1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http legis-link-mcp https://legis-link.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
Nothing is required, but it can take X-API-Key header (Optional Legis-Link Pro key (the licence key from your Gumroad receipt). Leave empty for the free tier.) if you want to set it.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
8 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Answers construction trade compliance questions with exact code references and clause citations. Use this tool when a tradesperson or engineer asks whether a specific installation, practice, or configuration is compliant with local regulations. Returns a COMPLIANT, NON_COMPLIANT, or REQUIRES_VERIFICATION status with the precise standard (e.g. AS/NZS 3000:2018 Clause 3.2.4) and any critical caveats
| Parameter | Type | Required | Notes |
|---|---|---|---|
| trade | string | yes | The construction trade relevant to the question. Must match a supported trade exactly. |
| region | string | yes | Use the state, province or country where the user works; if they have not said, ask them - never assume NSW or Australia. Jurisdiction for the compliance check. Examples: 'NSW', 'England', 'Texas', 'O |
| question | string | yes | The compliance question in plain English. Be specific: include voltages, distances, materials, or load values where relevant. Example: 'Is 2.5mm2 TPS cable compliant for a 20A circuit in a wall cavity |
| role | string | no | The role of the person asking. Affects the depth and terminology of the answer. |
| api_key | string | no | Legis-Link API key. Optional: leave empty for the free tier (50 requests/day); Pro users paste their ll_p_ key. Get a free key at https://legis-link.com |
Retrieves specific code sections, standards, and regulatory references for a construction trade topic. Use this tool when you need to cite the exact standard document, clause number, table reference, or regulatory instrument — without asking a yes/no compliance question. Returns the standard name, edition year, specific clause or table, and a plain-English summary of what that clause requires. Use
| Parameter | Type | Required | Notes |
|---|---|---|---|
| trade | string | yes | The construction trade for which you need a code reference. |
| region | string | yes | Use the state, province or country where the user works; if they have not said, ask them - never assume NSW or Australia. Jurisdiction. Determines which edition of the standard applies. Examples: 'NSW |
| topic | string | yes | The specific topic or subject to look up. Example: 'cable sizing for final sub-circuits', 'maximum water heater temperature', 'roof pitch minimums'. |
| api_key | string | no | Legis-Link API key. Optional: leave empty for the free tier (50 requests/day); Pro users paste their ll_p_ key. |
Lists all jurisdictions and regions supported by Legis-Link for a specific trade. Use this tool before calling other tools to confirm that the target region is supported, or to discover available regions when the user has not specified one. Returns a structured list of countries and their sub-regions (states, provinces, nations) along with the primary standards that apply in each region.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| trade | string | yes | The trade for which to list supported regions. |
| api_key | string | no | Legis-Link API key. Optional: leave empty for the free tier (50 requests/day); Pro users paste their ll_p_ key. |
[PRO] Performs numerical technical calculations for construction trades with code-compliant results. Use this tool when a specific measurement, size, rating, or capacity needs to be calculated — not just checked for compliance. Returns the calculated value with units, the method or formula used, relevant derating or correction factors, and the code reference that governs the calculation. Supports:
| Parameter | Type | Required | Notes |
|---|---|---|---|
| trade | string | yes | The trade for this calculation. Determines the applicable standard and units. |
| region | string | yes | Use the state, province or country where the user works; if they have not said, ask them - never assume NSW or Australia. Jurisdiction. Affects which standard and units apply (e.g. mm2 for AU/UK, AWG |
| calculation | string | yes | Describe the calculation needed with all relevant parameters. Include: load/flow value, distance/length, voltage/pressure, installation method, ambient conditions. Example: 'Cable size for 45A, 30m ru |
| role | string | no | User role. Affects detail level of the output. |
| api_key | string | no | Pro API key required. Get at https://rickyfarmer.gumroad.com/l/Legis-LinkPro |
[PRO] Generates a numbered safety checklist for a specific construction task with PPE requirements, hazard controls, and regulatory citations for each item. Use this tool when a foreman or safety officer needs a task-specific checklist before work begins. Each checklist item includes: the safety requirement, the specific control measure, and the regulation or standard that mandates it (e.g. WHS Ac
| Parameter | Type | Required | Notes |
|---|---|---|---|
| trade | string | yes | The trade performing the task. |
| region | string | yes | Use the state, province or country where the user works; if they have not said, ask them - never assume NSW or Australia. Jurisdiction. Determines which WHS/HSE regulations and codes of practice apply |
| task | string | yes | Specific task description. Be precise about the activity, location, and any known hazards. Example: 'Installing 415V switchboard in an occupied commercial building, working at 3m height'. |
| role | string | no | Role of the person who will use the checklist. |
| api_key | string | no | Pro API key required. |
[PRO] Generates a complete Risk Assessment and Method Statement (RAMS) document — called a Job Hazard Analysis (JHA) in the USA or Safe Work Method Statement (SWMS) in Australia. Use this tool when a foreman or PM needs a formal safety document before a high-risk task. Output includes: Section 1 — Hazard Register (tabular, with severity/likelihood/risk rating/controls/regulations), Section 2 — Met
| Parameter | Type | Required | Notes |
|---|---|---|---|
| trade | string | yes | The trade performing the work. |
| region | string | yes | Use the state, province or country where the user works; if they have not said, ask them - never assume NSW or Australia. Jurisdiction. Determines applicable WHS/CDM/OSHA legislation cited in the docu |
| task | string | yes | Full description of the task requiring the RAMS. Include: what work, where, at what height or voltage, any confined space, any hot work. The more detail, the more accurate the hazard register. |
| company_name | string | no | Optional. Company name to include in the document header. |
| site_address | string | no | Optional. Site address to include in the document header. |
| role | string | no | Role of the person generating the RAMS. Foreman or PM recommended. |
| api_key | string | no | Pro API key required. |
[PRO] Checks whether a specific material, product, or component meets the code requirements for a given trade application and jurisdiction. Returns COMPLIANT, NON_COMPLIANT, or REQUIRES_VERIFICATION with the specific clause that governs the material selection, and — if non-compliant — the compliant alternative. Use this tool BEFORE ordering materials to avoid costly substitutions on site. Do NOT u
| Parameter | Type | Required | Notes |
|---|---|---|---|
| trade | string | yes | The trade context for this material check. |
| region | string | yes | Use the state, province or country where the user works; if they have not said, ask them - never assume NSW or Australia. Jurisdiction. Determines which product standards and approval schemes apply. |
| material | string | yes | The material or product to check. Include: product name or type, specification or rating, and manufacturer if known. Example: '2.5mm2 TPS twin and earth, 450/750V rating, PVC insulation'. |
| use_case | string | no | Where and how the material will be used. Include installation method, environmental conditions, load. Example: 'underground direct burial, 20A circuit, 30m run, clay soil'. |
| role | string | no | Role of the person checking the material. |
| api_key | string | no | Pro API key required. |
[PRO] Returns all mandatory inspection hold points, sign-off authorities, certificates to be issued, and notification requirements for a construction installation in a specific jurisdiction. Use this tool when a foreman or PM needs to know: who must inspect, at what stage work must stop, what certificate is issued, and which regulation mandates the inspection. Prevents costly rework caused by cove
| Parameter | Type | Required | Notes |
|---|---|---|---|
| trade | string | yes | The trade performing the installation. |
| region | string | yes | Use the state, province or country where the user works; if they have not said, ask them - never assume NSW or Australia. Jurisdiction. Inspection authorities and certificate types vary significantly |
| installation | string | yes | Description of the installation requiring inspection. Be specific about scope. Example: 'new 3-bedroom residential electrical installation including switchboard, circuits, and solar inverter connectio |
| role | string | no | Role of the person requesting the inspection requirements. |
| api_key | string | no | Pro API key required. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Legis-Link or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 3.31.0 · scanned 2 Nov 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digestc8d557f46c10aa095a4b62c926099153826804251c8f2bf432624518cc5189fc
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| check_compliance | no tags | |
| get_code_reference | no tags | |
| list_supported_regions | no tags | |
| calculate_technical_spec | no tags | |
| generate_safety_checklist | no tags | |
| generate_rams | no tags | |
| verify_material_compliance | no tags | |
| get_inspection_requirements | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestc8d557f46c10aa09
Scanned2026-11-02
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 3.31.0.
3.31.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Legis-Link can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.