Juriset
REMOTE · MCP.JURISET.DEV · 3 COMPONENTS
Verified, cited US and Canadian employment and payroll rules, each value with its official source.
Available components
Last scanned (14 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Finance and Payments
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. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
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 8 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 20 Nov 26 +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.
- 17 Nov 26 +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.
- 15 Nov 26 +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.
- 14 Nov 26 0
- Server version: 0.1.2 → 0.1.3 functional
- 13 Nov 26 +1
- Tool “get_rule” rewrote its description, which is the text the model reads security
- 12 Nov 26 0
- Server version: 0.1.0 → 0.1.2 functional
- 11 Nov 26 +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.
- 10 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
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 21 Nov 2026 · Probed https://mcp.juriset.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=juriset.dev | CN=YE1,O=Let's Encrypt,C=US | 20 Oct 2026 | 18 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 60e1671ac499d2cb676e879f057c0d162d3 |
| SANs: *.juriset.dev, juriset.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.juriset.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| juriset.dev. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.juriset.dev/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.juriset.dev/mcp | HTTPS enforced | 301 | https://mcp.juriset.dev/mcp |
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 →
compare_jurisdictions Compare jurisdictions ~271
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Rule type slug from list_rule_types, e.g. `minimum_wage`. |
No output schema declared.
No examples provided.
get_rule Get the current rule ~358
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`).
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | The rule type's domain, e.g. `employment`. Optional: when omitted it is looked up from the rule type. |
| jurisdiction | string | yes | Jurisdiction slug from list_jurisdictions, e.g. `us-wa` (Washington), `us` (US federal), `ca-ab` (Alberta). |
| rule_type | string | yes | Rule type slug from list_rule_types, e.g. `minimum_wage`, `overtime`. |
No output schema declared.
No examples provided.
get_rule_as_of Get the rule on a date ~245
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.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | yes | 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 | yes | Jurisdiction slug from list_jurisdictions, e.g. `us-wa` (Washington), `us` (US federal), `ca-ab` (Alberta). |
| rule_type | string | yes | Rule type slug from list_rule_types, e.g. `minimum_wage`, `overtime`. |
No output schema declared.
No examples provided.
get_rule_history Get a rule's version history ~204
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | The rule type's domain, e.g. `employment`. Optional: when omitted it is looked up from the rule type. |
| jurisdiction | string | yes | Jurisdiction slug from list_jurisdictions, e.g. `us-wa` (Washington), `us` (US federal), `ca-ab` (Alberta). |
| rule_type | string | yes | Rule type slug from list_rule_types, e.g. `minimum_wage`, `overtime`. |
No output schema declared.
No examples provided.
list_changes List rule changes ~291
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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`. |
No output schema declared.
No examples provided.
list_jurisdictions Find a jurisdiction ~153
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | A name, postal abbreviation or slug, any case: `Washington`, `WA`, `us-wa`. Omit to list every jurisdiction. |
No output schema declared.
No examples provided.
list_rule_types List rule types ~122
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | Only this domain's rule types, e.g. `employment` or `payroll`. |
No output schema declared.
No examples provided.
resolve_version Resolve a version id ~148
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.
| Name | Type | Req | Description |
|---|---|---|---|
| version_id | string | yes | A version id from a rule response's `id`, e.g. `rv_000000000000000000000000F2`. |
No output schema declared.
No examples provided.
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.
remote · mcp.juriset.dev
claude mcp add --transport http dev-juriset-juriset 'https://mcp.juriset.dev/mcp'
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.