# Juriset Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## Juriset

Look up cited US and Canadian employment and payroll rules by state, province or city.

- Record: https://musedirectory.ai/connector/juriset
- Category: Legal
- Developer: Juriset (https://juriset.dev)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 245ms, checked 2026-11-09T18:36:14Z
- Endpoint: https://mcp.juriset.dev/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-11-09T18:36:14Z)
- Source: Found in the official MCP Registry (dev.juriset/juriset) https://registry.modelcontextprotocol.io/v0/servers?search=dev.juriset%2Fjuriset

Connects to Juriset's registry of employment and payroll rules for the US and Canada. Muse can pull the minimum wage or overtime rule for a state, province or city, show the official source and excerpt, compare jurisdictions, check what applied on a past date, and trace how a rule changed over time.

Example request: "What is the minimum wage in Washington right now, and how does overtime stack with the federal rule?"

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Juriset to help me. It is a free service with an MCP server at https://mcp.juriset.dev/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- list_jurisdictions: List the US and Canadian jurisdictions Juriset covers, or find one by name. The other Juriset tools take slugs, not names. Each entry has the slug, name, level (`country`, `state`, `province`, `county` or `city`) and parent. Examples: `Washington` or `WA` → `us-wa`; `Alberta` → `
- list_rule_types: List the kinds of rule Juriset publishes. Each entry has its slug (the `rule_type` argument of the other tools), domain, description, how jurisdiction levels combine (`override`, `max` or `stack`) and the JSON Schema of its `data`, with every field described. Examples: `minimum_w
- get_rule: Get the rule in force today for one rule type in one jurisdiction, with its citation: source URL, verbatim excerpt and the snapshot Juriset stored. Example: `{"rule_type": "minimum_wage", "jurisdiction": "us-wa"}`. The response is the API's: `data` holds the values (described by 
- get_rule_as_of: Get the rule that was (or will be) in effect on a date, in the same shape as get_rule. Example: `{"rule_type": "minimum_wage", "jurisdiction": "us-wa", "as_of": "2025-06-30"}`. Use it to see what applied when a past decision was made. A date before Juriset's coverage of that juri
- get_rule_history: List every version ever published of one jurisdiction's rule, with its effective dates, values, citation and whether it is current, superseded or withdrawn. Example: `{"rule_type": "minimum_wage", "jurisdiction": "us-wa"}`. Covers that jurisdiction's own rule only; other levels t
- compare_jurisdictions: Get one rule type across jurisdictions in one call, each entry in the same shape as get_rule. Example: `{"rule_type": "minimum_wage", "jurisdictions": ["us-wa", "us-or", "us-ca"]}`. Without `jurisdictions`, every state and province (or the `level` you name) is returned: about 3 K
- list_changes: List changes to published rules, oldest first: new versions, amendments, corrections and repeals, each naming the rule, the versions moved from and to, the effective date and the version id to pass to resolve_version. Example: `{"since": "2026-10-01", "jurisdictions": ["us", "us-
- resolve_version: Get exactly the version a stored id names, forever, even after it was superseded or withdrawn: the values, effective dates, citation, verification record and its status today. Version ids (`rv_…`) come from the `id` of any rule response. Use it to re-check the value a decision re

Screening checks:
- MCP handshake: pass (Answered in 245ms)
- Domain against threat feeds (Cloudflare security DNS): pass (mcp.juriset.dev, juriset.dev not flagged)
- Published packages against the OSV malicious-package database: pass (No malicious-package advisories)
- Hidden instructions or invisible characters in tool text: pass (8 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)