mcpbeat Sign in

Reglyze MCP Server

by reglyze Your server? Claim it
answering

Reglyze is answering right now. Last checked 9 min ago. It exposes 7 tools.

NIS2 tools: scope check, EU transposition, incident deadlines, and your own org's status (token).

Uptime history 91 days of history · worst day 93%
91 days agonow
100.0%
Uptime 24h
91 of 91 checks
7
Tools
read from the server
281 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 35

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 21 August 2026. No other catalogue keeps this.

6 Nov a tool changed version
5 Nov 3 tools changed the parameters they ask for incident_deadline_formats, scope_check, transposition_status
30 Oct 3 tools changed the parameters they ask for18 times that day incident_deadline_formats, scope_check, transposition_status
29 Oct 3 tools changed the parameters they ask for4 times that day incident_deadline_formats, scope_check, transposition_status
29 Oct a tool description was rewritten incident_deadline_formats
28 Oct 3 tools changed the parameters they ask for incident_deadline_formats, scope_check, transposition_status
23 Oct a tool description was rewritten scope_check
23 Oct a tool changed the parameters it asks for scope_check
16 Oct a tool changed version
21 Sep a tool changed version
and 17 more, back to 21 August 2026

Reglyze missed 2 checks this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

run in your terminal
claude mcp add mcp --transport http https://api.reglyze.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://api.reglyze.com/mcp
~/.codex/config.toml
[mcp_servers.mcp]
url = "https://api.reglyze.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://api.reglyze.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "mcp": {
      "type": "http",
      "url": "https://api.reglyze.com/mcp"
    }
  }
}

Available tools 7

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

compliance
compliance_status
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.
documents
documents_list
Requires a Reglyze API token. Lists YOUR organization's compliance documents (title, type, status, current version). Metadata only, not document content.
incident
incident_deadline_formats
NIS2 incident-notification deadlines for a country: the 24h/72h/1-month stages with their national legal basis, the competent authority/CSIRT and portal, the sector routing (a sector CSIRT or authority that receives instead of, or with, the national one; pass `sector` for the recipient of one organisation), and the national severity vocabulary (e.g. Italy's ACN IS-1..IS-4 typologies, with their entity-class applicability).
incidents
incidents_list
Requires a Reglyze API token. Lists YOUR organization's recorded incidents (title, status, severity, detection date).
open
open_tasks
Requires a Reglyze API token. Lists YOUR organization's open remediation tasks. Optional filters: status, severity, overdue.
scope
scope_check
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, size-independent types (DNS, TLD, trust services, public electronic communications; cloud, data-centre and CDN providers follow the size test). Returns classification, reasoning, the national transposition law with its deviations, and next-step links.
transposition
transposition_status
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.

Endpoints

URLTransportStateLatencyChecked
https://api.reglyze.com/mcp streamable-http answering 216 ms 9 min ago

Alternatives to Reglyze

same job, measured the same way
Uptimepage
by uptimepage

Monitor uptime and incidents, run checks, and publish status updates from your Uptimepage org.

41 tools answering
Devops Status MCP Server
by cyanheads

Vendor status pages, TLS cert inspection, DNS propagation checks, and incident-response playbooks.

618 installs/wk 7 tools answering
FlareWarden
by flarewarden

Check if a site or service like Stripe is down, and monitor your sites, cron jobs and status pages.

65 tools answering
ForgeOps
by getforgeops

Production errors and incidents for your agent: stack traces, breadcrumbs, likely causes, triage.

answering
Moltline RegClock
by moltlinestudio

Incident-reporting deadlines from the law: CRA, NIS2, DORA, GDPR, HIPAA, SEC 8-K. 6 of 9 tools free.

9 tools answering
MCP API Change Monitor
by mambabuilt

API changelog, deprecation, status, OpenAPI, and Sunset header changes since your last run.

279 installs/wk local only
openstatus
by openstatus

Manage monitors, status pages, incidents and maintenances in your openstatus workspace.

answering
losclouds
by losclouds

Cloud and SaaS service status, plus your team's monitors, status pages, incidents, and alerts.

answering

Reglyze — questions

Answers built from our own checks of this server.

What can Reglyze do?
It exposes 7 tools, read directly from the server on our last check. Among them: compliance_status, documents_list, incident_deadline_formats, incidents_list, open_tasks, scope_check and 1 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Reglyze working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 281 ms. The bar chart above shows every period we have measured.
How do I connect Reglyze?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Reglyze need an API key?
No. Reglyze completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 7 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Reglyze?
It answers our handshake in 281 ms on average, which is faster than 50% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.