# Juriset (remote · mcp.juriset.dev)

Verified, cited US and Canadian employment and payroll rules, each value with its official source.

- Trust score: 75/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `mcp.juriset.dev`: 75/100 (this document), [markdown](https://verifymcp.io/servers/dev-juriset-juriset/mcp.md), [page](https://verifymcp.io/servers/dev-juriset-juriset/mcp)
- npm · `juriset-mcp`: 39/100, [markdown](https://verifymcp.io/servers/dev-juriset-juriset/juriset-mcp.md), [page](https://verifymcp.io/servers/dev-juriset-juriset/juriset-mcp)
- pypi · `juriset-mcp`: 75/100, [markdown](https://verifymcp.io/servers/dev-juriset-juriset/juriset-mcp-2.md), [page](https://verifymcp.io/servers/dev-juriset-juriset/juriset-mcp-2)

## Channel facts

- Endpoint: `https://mcp.juriset.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.3`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1792 tokens (~224/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Juriset MCP server?

Juriset is a hosted endpoint at https://mcp.juriset.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http dev-juriset-juriset 'https://mcp.juriset.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-juriset-juriset": {
      "url": "https://mcp.juriset.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-juriset-juriset": {
      "type": "http",
      "url": "https://mcp.juriset.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-juriset-juriset]
url = "https://mcp.juriset.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-juriset-juriset": {
      "type": "remote",
      "url": "https://mcp.juriset.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-juriset-juriset --url 'https://mcp.juriset.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-juriset-juriset:
    url: "https://mcp.juriset.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-juriset-juriset": {
      "Transport": "http",
      "Url": "https://mcp.juriset.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-juriset-juriset -t streamable-http -u 'https://mcp.juriset.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-juriset-juriset": {
      "type": "http",
      "url": "https://mcp.juriset.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 75, +1)

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

### 2026-11-17 (score 74, +1)

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

### 2026-11-15 (score 73, +1)

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

### 2026-11-14 (score 72, 0)

- [functional] Server version: 0.1.2 → 0.1.3

### 2026-11-13 (score 72, +1)

- [security] Tool “get_rule” rewrote its description, which is the text the model reads

### 2026-11-12 (score 71, 0)

- [functional] Server version: 0.1.0 → 0.1.2

### 2026-11-11 (score 71, +1)

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

### 2026-11-10 (score 70, 0)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (8)

### `list_jurisdictions` (~153 tokens)

Find a jurisdiction

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` → `ca-ab`; the federal levels are `us` and `ca`. Omit `query` for all of them. Reads the registry; no rule lookup.

Input parameters:

- `query` (string): A name, postal abbreviation or slug, any case: `Washington`, `WA`, `us-wa`. Omit to list every jurisdiction.

### `list_rule_types` (~122 tokens)

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_wage` and `overtime` (domain `employment`). Optional `domain` filter. Reads the registry; no rule lookup.

Input parameters:

- `domain` (string): Only this domain's rule types, e.g. `employment` or `payroll`.

### `get_rule` (~358 tokens)

Get the current 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 the JSON Schema at `schema_url`), `effective_from` and `verified_at` date them, `id` is the version id to record with any decision that relies on it (see resolve_version), and `verification` says which models extracted and checked it and whether a person reviewed it. `verified_at` is when the sources were last re-fetched and found unchanged, not the review date (`verification.reviewed_at`); it is null until a newly fetched source has been re-checked once. Read `data` with its schema: optional fields carry defaults there, e.g. a `minimum_wage` tier or exception without `per_unit` is per hour. Where levels stack (e.g. US federal and state overtime) every level comes back as its own entry in `layers`; Juriset never merges them. Informational only, not legal advice (`disclaimer`).

Input parameters:

- `domain` (string): The rule type's domain, e.g. `employment`. Optional: when omitted it is looked up from the rule type.
- `jurisdiction` (string, required): Jurisdiction slug from list_jurisdictions, e.g. `us-wa` (Washington), `us` (US federal), `ca-ab` (Alberta).
- `rule_type` (string, required): Rule type slug from list_rule_types, e.g. `minimum_wage`, `overtime`.

### `get_rule_as_of` (~245 tokens)

Get the rule on a date

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 jurisdiction is answered with an error that says where coverage starts. Informational only, not legal advice. If the API key's plan does not include as-of queries the error says so.

Input parameters:

- `as_of` (string, required): The date, `YYYY-MM-DD`, past or future.
- `domain` (string): The rule type's domain, e.g. `employment`. Optional: when omitted it is looked up from the rule type.
- `jurisdiction` (string, required): Jurisdiction slug from list_jurisdictions, e.g. `us-wa` (Washington), `us` (US federal), `ca-ab` (Alberta).
- `rule_type` (string, required): Rule type slug from list_rule_types, e.g. `minimum_wage`, `overtime`.

### `get_rule_history` (~204 tokens)

Get a rule's version 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 that apply (e.g. `us`) are separate calls. Each entry's `id` can be passed to resolve_version. Informational only, not legal advice.

Input parameters:

- `domain` (string): The rule type's domain, e.g. `employment`. Optional: when omitted it is looked up from the rule type.
- `jurisdiction` (string, required): Jurisdiction slug from list_jurisdictions, e.g. `us-wa` (Washington), `us` (US federal), `ca-ab` (Alberta).
- `rule_type` (string, required): Rule type slug from list_rule_types, e.g. `minimum_wage`, `overtime`.

### `compare_jurisdictions` (~271 tokens)

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 KB each, 50+ entries. Entries are never merged or ranked. Informational only, not legal advice. `as_of` needs an API key whose plan includes as-of queries.

Input parameters:

- `as_of` (string): A date, `YYYY-MM-DD`, instead of today.
- `domain` (string): The rule type's domain, e.g. `employment`. Optional: when omitted it is looked up from the rule type.
- `jurisdictions` (array): Up to 100 jurisdiction slugs, any level, e.g. `["us-wa", "us-or", "us-ca"]`. Not with `level`.
- `level` (array): Instead of `jurisdictions`: every jurisdiction at these levels, e.g. `["state", "province"]` (the default).
- `rule_type` (string, required): Rule type slug from list_rule_types, e.g. `minimum_wage`.

### `list_changes` (~291 tokens)

List rule 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-wa"]}`. Each jurisdiction matches its own rules only, so for everything that changes Washington's answer pass the federal level too. While `has_more` is true, call again with the response's `cursor`. Needs an API key whose plan includes the change feed; otherwise the error says so. Informational only, not legal advice.

Input parameters:

- `cursor` (string): The `cursor` of the previous response, to continue or to poll for new changes.
- `domain` (string): Only this domain, e.g. `employment`.
- `jurisdictions` (array): Jurisdiction slugs, e.g. `["us", "us-wa"]`; each matches its own rules only.
- `limit` (integer): Changes per call, 1 to 500.
- `rule_type` (string): Only this rule type, e.g. `overtime`.
- `since` (string): Where to start: an ISO 8601 date or date-time, e.g. `2026-10-01` (midnight UTC). Give this or `cursor`.

### `resolve_version` (~148 tokens)

Resolve a version id

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 relied on, or to show an auditor which rule applied. Example: `{"version_id": "rv_000000000000000000000000F2"}`. Informational only, not legal advice.

Input parameters:

- `version_id` (string, required): A version id from a rule response's `id`, e.g. `rv_000000000000000000000000F2`.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-juriset-juriset/mcp#diagnostics

## Score history

- 2026-11-21: 75
- 2026-11-20: 75
- 2026-11-19: 74
- 2026-11-18: 74
- 2026-11-17: 74
- 2026-11-16: 73
- 2026-11-15: 73
- 2026-11-14: 72
- 2026-11-13: 72
- 2026-11-12: 71
- 2026-11-11: 71
- 2026-11-10: 70
- 2026-11-09: 70

## Common questions

### What is the Juriset MCP server?

Juriset is an MCP server listed in the public MCP registry as dev.juriset/juriset. Verified, cited US and Canadian employment and payroll rules, each value with its official source. This page covers its hosted endpoint (https://mcp.juriset.dev/mcp).

### Is the Juriset MCP server safe to use?

Juriset scores 75 out of 100 on VerifyMCP. 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 Juriset MCP server expose?

Juriset exposes 8 tools: list_jurisdictions, list_rule_types, get_rule, get_rule_as_of, get_rule_history, and 3 more. Their descriptions and schemas cost roughly 1,792 tokens of context every time the server is loaded.

### Does the Juriset MCP server require authentication?

No. We connected to Juriset without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Juriset MCP server still maintained?

Juriset is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Juriset MCP server?

VerifyMCP ran 13 checks on Juriset, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://mcp.juriset.dev/mcp
- Repository: https://github.com/juriset/mcp-server
- Website: https://juriset.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-juriset-juriset/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-juriset-juriset/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/dev-juriset-juriset/mcp.json
- HTML version of this page: https://verifymcp.io/servers/dev-juriset-juriset/mcp
