Legis-Link MCP server
com.legis-link/legis-linklegis-link.comstreamable-httpv3.31.0Scanned
Compliance answers for 10 construction trades in AU, UK, US, CA and EU: codes, licensing, RAMS.
8 tools: 5 change things and 3 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 2 findings
Tools listed without sign-in. Remote posture
With Anlyon
5 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Legis-Link MCP server can do
The Legis-Link MCP server is published by legis-link.com, a domain the MCP Registry verified. It has 8 tools. It can create or change data (5 tools: check_compliance, calculate_technical_spec, generate_safety_checklist, generate_rams and 1 more), but cannot delete data. 3 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 2 findings (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 15, 2026, version 3.31.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
8 tools
Changes things 5Claude Code: ask
calculate_technical_spec[PRO] Performs numerical technical calculations for construction trades with code-compliant results.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it [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: cable/conductor sizing (mm2 or AWG), voltage drop (%), pipe sizing (mm or inches), HVAC duct sizing (CFM/L/s), heat load calculations, load current calculations, and more. Example inputs: 'Cable size for 32A circuit, 25m run, 240V single phase, clipped direct', 'Pipe size for 40 fixture units copper hot water supply', 'Duct size for 1200 CFM round duct'.
Annotations the server declares
- title: Calculate a technical spec (Pro)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
check_complianceAnswers construction trade compliance questions with exact code references and clause citations.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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. Covers electrical, plumbing, HVAC, welding, carpentry, roofing, gas fitting, solar, fire protection, and concrete trades across Australia, UK, USA, Canada, and EU. Do NOT use this tool for numerical calculations (use calculate_technical_spec instead) or for generating safety checklists or RAMS documents.
Annotations the server declares
- title: Check compliance
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
generate_rams[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.1 finding
Why it is in this group
- The name "generate_rams" says "generate": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "generate_rams" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "generate_rams" says "generate": a word for a change.
Description, as the server wrote it [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 — Method Statement (numbered sequential steps), Section 3 — Required Qualifications and Certifications. The document is formatted for printing or inclusion in a site safety file. This tool produces a longer output than other tools — expect 800-1500 words. Example tasks: 'Electrical switchboard installation in commercial building NSW', 'Gas line installation in residential kitchen UK', 'Roof framing timber frame residential NSW'.
Annotations the server declares
- title: Generate RAMS (Pro)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
generate_safety_checklist[PRO] Generates a numbered safety checklist for a specific construction task with PPE requirements, hazard controls, and regulatory citations for each item.1 finding
Why it is in this group
- The name "generate_safety_checklist" says "generate": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "generate_safety_checklist" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "generate_safety_checklist" says "generate": a word for a change.
Description, as the server wrote it [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 Act 2011, CDM 2015, OSHA 29 CFR 1926). Do NOT use this tool to generate a full RAMS document — use generate_rams for that. Example tasks: 'working at height on a residential roof', 'hot work near fuel lines', 'isolating and working on a 415V switchboard'.
Annotations the server declares
- title: Generate a safety checklist (Pro)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
verify_material_compliance[PRO] Checks whether a specific material, product, or component meets the code requirements for a given trade application and jurisdiction.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it [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 use this tool for general compliance questions — use check_compliance instead. Example inputs: '2.5mm2 TPS cable for 20A underground direct burial circuit NSW', 'Class 12 copper pipe for domestic hot water NSW', 'R3.5 glasswool batts for external wall cavity UK Building Regs'.
Annotations the server declares
- title: Verify material compliance (Pro)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 3Show 3 read-only tools
get_code_referenceRetrieves specific code sections, standards, and regulatory references for a construction trade topic.No findings
Why it is in this group
- The name "get_code_reference" says "get": a word for reading.
Description, as the server wrote it 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. Useful for pre-populating compliance documents, RAMS, or certificates. Examples: 'AS/NZS 3008 cable sizing tables', 'CDM 2015 notification thresholds', 'NEC Article 210 branch circuits'.
Annotations the server declares
- title: Look up a code or standard
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_inspection_requirements[PRO] Returns all mandatory inspection hold points, sign-off authorities, certificates to be issued, and notification requirements for a construction installation in a specific jur…No findings
Why it is in this group
- The name "get_inspection_requirements" says "get": a word for reading.
Description, as the server wrote it [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 covering work before mandatory inspection. Returns a numbered list of inspection stages with: inspector role/authority, certificate type and form number, regulatory reference, and notification timing. Example installations: 'residential electrical installation NSW', 'timber frame residential build NSW', 'gas fitting domestic kitchen UK'.
Annotations the server declares
- title: Get inspection requirements (Pro)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_supported_regionsLists all jurisdictions and regions supported by Legis-Link for a specific trade.No findings
Why it is in this group
- The name "list_supported_regions" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: List supported regions
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:23 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 5
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 5 tools that change things (5 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://legis-link.com/mcp: tools/list returned 8 tools to an anonymous client, including check_compliance (write), calculate_technical_spec (write), generate_safety_checklist (write), generate_rams (write), verify_material_compliance (write)
Findings
Matches of fixed checks, with the text they matched.
The server marks "generate_safety_checklist" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "generate_safety_checklist" says "generate": a word for a change.
- Warngenerate_rams
The server marks "generate_rams" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "generate_rams" says "generate": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools3 changed.~3 changedView diff
- Changed:check_complianceChanges thingsinputSchema
- Changed:get_code_referenceOnly readsinputSchema
- Changed:list_supported_regionsOnly readsinputSchema
Install
Pinned to version 3.31.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http legis-link https://legis-link.com/mcpclaude mcp add --transport http legis-link https://legis-link.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__legis-link__get_code_reference",
"mcp__legis-link__list_supported_regions",
"mcp__legis-link__get_inspection_requirements"
],
"ask": [
"mcp__legis-link__check_compliance",
"mcp__legis-link__calculate_technical_spec",
"mcp__legis-link__generate_safety_checklist",
"mcp__legis-link__generate_rams",
"mcp__legis-link__verify_material_compliance"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as legis-link. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.legis-link/legis-link/verify?hash=259b7e402a5d982bbc8ab8fa5d394b71c70a94641699b53c13e79ee09a5ed145" | jq -e '.changed == false'Pinned hash 259b7e402a5d, from Nov 15, 2026, 06:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.legis-link/legis-link/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.legis-link/legis-link)Source: MCP Registry · repository. Synced Nov 2, 2026, 04:17 UTC.
Legis-Link MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Legis-Link MCP server safe?
- No scan can promise that. What its definitions show: 8 tools, 5 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Legis-Link MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Legis-Link MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Legis-Link MCP server have?
- 8 tools: 5 write, 3 read. check_compliance, calculate_technical_spec, generate_safety_checklist, generate_rams, verify_material_compliance, get_code_reference, list_supported_regions and get_inspection_requirements.
Does the Legis-Link MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Legis-Link MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Legis-Link MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 15, 2026. Every change is on this page and in its Atom feed.