Local MCP capabilities provider for Expo
Reglyze is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
NIS2 tools: scope check, EU transposition, incident deadlines, and your own org's status (token).
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http reglyze-mcp https://api.reglyze.com/mcp
# 2 — ask your agent for something these tools do
# scope_check, transposition_status, incident_deadline_formats and 4 more
Reglyze costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http reglyze-mcp https://api.reglyze.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
7 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Determine whether NIS2 (and its national transposition) applies to an organization, and whether it is an essential or important entity. Inputs: EU/EEA country (ISO-2), primary NIS2 sector, headcount, turnover/balance sheet in M EUR, special categories (DNS, TLD, cloud, qualified trust services). Returns classification, reasoning, the national transposition law with its deviations, and next-step li
| Parameter | Type | Required | Notes |
|---|---|---|---|
| country | string | yes | ISO-2 country code of the organization (e.g. IT, PL, FR) |
| sector | string | yes | Primary NIS2 sector id (see the sector list in the tool description) |
| additional_sectors | array | no | — |
| employee_count | integer | yes | — |
| annual_turnover_meur | number | no | Annual turnover in millions of EUR |
| annual_balance_sheet_meur | number | no | — |
| dns_provider | boolean | no | — |
| tld_registry | boolean | no | — |
| cloud_provider | boolean | no | — |
| qualified_trust_service_provider | boolean | no | — |
| sole_provider | boolean | no | Sole provider of a service essential to society in its Member State |
| language | string | no | — |
Current NIS2 transposition status per EU/EEA country (law, stage, competent authority, sources), from the Reglyze transposition tracker (curated + weekly auto-updated). Omit the country for the full map.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| country | string | no | ISO-2 country code; omit for all tracked countries |
| language | string | no | — |
NIS2 incident-notification deadlines for a country: the 24h/72h/1-month stages with their national legal basis, the competent authority/CSIRT and portal, and the national severity vocabulary (e.g. Italy's ACN IS-1..IS-4 typologies, with their entity-class applicability).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| country | string | yes | ISO-2 country code |
| language | string | no | — |
Requires a Reglyze API token. Returns YOUR organization's current compliance score, implementation/documentation sub-scores, open-task counts, and the national-framework per-objective view.
No parameter schema on file.
Requires a Reglyze API token. Lists YOUR organization's compliance documents (title, type, status, current version). Metadata only, not document content.
No parameter schema on file.
Requires a Reglyze API token. Lists YOUR organization's open remediation tasks. Optional filters: status, severity, overdue.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status | string | no | — |
| severity | string | no | — |
| overdue | boolean | no | — |
Requires a Reglyze API token. Lists YOUR organization's recorded incidents (title, status, severity, detection date).
No parameter schema on file.
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Reglyze or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.1.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Reglyze can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.