Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.ChangkeunJ/australian-law-mcp

NPM · AUSTRALIAN-LAW-MCP

Read Australian Commonwealth law as it stood on any date, and verify citations against the register

Available components

0 this week 94 Trust /100

Last scanned (9 hours ago)

Scores higher than 97% of npm servers

Category Education and Research

Trust breakdown (7 categories)

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 Security100
  • 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
  • 0 of 4 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to ChangkeunJ/australian-law-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 53 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 667 tokens (~83/item across 8 items; 8 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage81
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 43% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

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 →

Changelog

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.

  • 2 Nov 26 +1
    • Stability: 0.97 → pass security
  • 1 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 26 Oct 26 +1
    • Stability: 0.97 → pass security
  • 25 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 19 Oct 26 +1
    • Stability: 0.97 → pass security
  • 17 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Oct 26 −3
    • Stability: pass → 0.80 functional
Diagnostics

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 5 Nov 2026 · Analysed npm/australian-law-mcp@0.1.5

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo ChangkeunJ/australian-law-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/ChangkeunJ/australian-law-mcp/.github/workflows/release.yml@refs/tags/v0.1.5
Rekor log index 2808536979
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:38b270f00986f42a7474d05ec20c67c1f25ee4b9a29452f04ea5cc2f8f7c970185874f06b8b6798733a0ba4aa7feae6c9cdd0186c8f295d5d92d55129

Background: How many MCP packages publish verified provenance →

Dependencies 4 packages
Packages resolved 4
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 8 exposed · ~608 tokens

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 →

Tool Tokens
check_frl_health ~30

Pings the Federal Register of Legislation API and reports latency, so failures elsewhere can be attributed.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

compare_versions ~95

Shows what changed in an act between two dates: which sections were added, removed or reworded. Give a section number for a line-by-line diff of that provision.

NameTypeReqDescription
dateAstringyesyyyy-mm-dd, the earlier date
dateBstringyesyyyy-mm-dd, the later date
pageinteger––
sectionstring––
titleIdstringyes–

No output schema declared.

No examples provided.

get_amendment_status ~50

Reports whether a title is in force, what its latest compilation incorporates, whether commenced amendments are still unincorporated, and which acts have amended it.

NameTypeReqDescription
titleIdstringyes–

No output schema declared.

No examples provided.

get_law_as_at ~82

Returns the compilation of a Commonwealth act that was in force on the given date — the register keeps every historical version. Same output shape as get_law_text.

NameTypeReqDescription
datestringyesyyyy-mm-dd
fullboolean––
pageinteger––
sectionstring––
titleIdstringyes–

No output schema declared.

No examples provided.

get_law_text ~117

Returns the latest compilation of a Commonwealth act or instrument. Without a section number it lists the table of sections; with one it returns that provision. Set full=true for the whole text, paginated.

NameTypeReqDescription
fullboolean–Return the full text instead of the table of sections
pageinteger––
sectionstring–Section number, e.g. "3A" or "90-5"
titleIdstringyesRegister title id, e.g. C2004A03348

No output schema declared.

No examples provided.

search_full_text ~77

Searches the body text of every act and instrument on the register for a phrase, ranked by relevance. Slower and broader than search_law.

NameTypeReqDescription
limitinteger––
matchstring–exact = the phrase verbatim (default), all = every word, any = any word
phrasestringyes–

No output schema declared.

No examples provided.

search_law ~71

Finds Commonwealth acts and legislative instruments on the Federal Register of Legislation by title. Returns title ids for the other tools. Falls back to full-text matching when nothing matches by name.

NameTypeReqDescription
limitinteger––
querystringyesWords from the title, e.g. "income tax rates"

No output schema declared.

No examples provided.

verify_citations ~86

Extracts Australian statute citations from text and checks each against the Federal Register of Legislation: does the act exist, is it still in force, does the cited section exist in the current compilation. Use before presenting legal citations to a user. An upstream failure is reported as UNVERIFIED, never as a missing law.

NameTypeReqDescription
textstringyesText containing the citations to check

No output schema declared.

No examples provided.

Install

How do I install the io.github.ChangkeunJ/australian-law-mcp server?

io.github.ChangkeunJ/australian-law-mcp runs locally as an npm package, launched with npx -y australian-law-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 · australian-law-mcp

# add to Claude Code
claude mcp add changkeunj-australian-law-mcp -- npx -y australian-law-mcp
Common questions

What is the io.github.ChangkeunJ/australian-law-mcp server?

io.github.ChangkeunJ/australian-law-mcp is listed in the public MCP registry as io.github.ChangkeunJ/australian-law-mcp. Read Australian Commonwealth law as it stood on any date, and verify citations against the register. This page covers its npm package (australian-law-mcp).

Is the io.github.ChangkeunJ/australian-law-mcp server safe to use?

io.github.ChangkeunJ/australian-law-mcp scores 94 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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.ChangkeunJ/australian-law-mcp server expose?

io.github.ChangkeunJ/australian-law-mcp exposes 8 tools: search_law, get_law_text, get_law_as_at, get_amendment_status, compare_versions, and 3 more. Their descriptions and schemas cost roughly 608 tokens of context every time the server is loaded.

Is the io.github.ChangkeunJ/australian-law-mcp server still maintained?

io.github.ChangkeunJ/australian-law-mcp is still listed as active in the MCP registry. We last reached this channel on 5 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.ChangkeunJ/australian-law-mcp server under?

io.github.ChangkeunJ/australian-law-mcp 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.ChangkeunJ/australian-law-mcp server?

VerifyMCP ran 16 checks on io.github.ChangkeunJ/australian-law-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. 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.