Australian Law MCP vs PolicyForge MCP Server | AllMCPs
Side-by-Side Model Context Protocol Comparison
Australian Law MCP vs PolicyForge MCP Server
In-depth architectural comparison of the Australian Law MCP and PolicyForge MCP Server MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Australian Law MCP
Legal · Local stdio
Quality: 57/100 (Good) | Auth: No auth required
PolicyForge MCP Server
Legal · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
Verdict Summary: Choose Australian Law MCP if you need specialized Legal tools running via a local process. Choose PolicyForge MCP Server if your workspace requires Legal integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Australian Law MCP when:
You need dedicated capabilities in the Legal domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Find acts and instruments by name. Returns the title ids the other tools take.
get_law_text
The current compilation: the table of provisions, one section, or the full text paginated. Schedules are addressable too (`section="Schedule 7"`), which is where rate tables and forms actually live.
get_law_as_at
The same, but as the law stood on any past date.
verify_citations
Pull statute citations out of text and check each against the register: does the act exist, is it in force, does the cited section exist. Upstream failures come back as UNVERIFIED, never as a missing law.
get_amendment_status
In force or repealed, what the latest compilation incorporates, whether commenced amendments are still unincorporated, and what has amended it.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Australian Law MCP is categorized under Legal and uses a local stdio subprocess. In contrast, PolicyForge MCP Server belongs to Legal using local stdio subprocess. Select Australian Law MCP when you need capabilities focused on legal and PolicyForge MCP Server when you require tools for legal.
What changed between two dates: sections added, removed, reworded — or a line diff of one section.
search_full_text
Relevance-ranked search over the body text of every title on the register.
check_frl_health
Ping the register API so failures elsewhere can be attributed.
PolicyForge MCP Server Tools (15)
generate_policy
Generate a policy and return its Markdown content + hosted URL. Consumes one policy from your quota.
generate_baa
Generate a HIPAA Business Associate Agreement between a covered entity and a vendor handling PHI. Built from the clauses required by 45 CFR 164.504(e) and validated clause by clause. Pro plan; never publicly hosted. Consumes one policy from your quota.
regenerate_policy
Re-run the AI engine with changed business context — same ID and hosted URL, previous content saved as a version.
update_policy
Hand-edit a policy in place — same ID and hosted URL, so published links keep working.
audit_compliance
Gap analysis: compare what the code does (your scanned manifest) with what a policy discloses.
check_policy_freshness
Drift detection: diff the current codebase scan against the manifest stored at generation time.
list_policy_versions
Version history — a snapshot is saved before every update, regeneration, or restore.
restore_policy_version
Roll a policy back to any previous version (itself reversible).
list_policies
List policies on your account (filter by type/status, paginate).
get_policy
Fetch a single policy by ID, including full content.
delete_policy
Permanently delete a policy (its hosted URL stops working).
get_usage
Check your tier and remaining generation quota before generating.