com.reglyze/mcp

REMOTE · API.REGLYZE.COM · SCANNED AUG 3

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

Available components

+6 this week 65 65 Trust /100

Trust breakdown (6 categories)

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 →

Endpoint Security63

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
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 Usability66

AI-judged instruction clarity (good).Pass
Tool/resource definitions use about 594 tokens (~84/item across 7 items; 7 tools + 0 resources), lean.Pass
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management27

Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage77

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
32% of tool parameters carry a description.Partial

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · api.reglyze.com

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http com-reglyze-mcp https://api.reglyze.com/mcp

# ~/.codex/config.toml

[mcp_servers.com-reglyze-mcp]
url = "https://api.reglyze.com/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-reglyze-mcp": {
      "type": "remote",
      "url": "https://api.reglyze.com/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add com-reglyze-mcp --url https://api.reglyze.com/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  com-reglyze-mcp:
    url: "https://api.reglyze.com/mcp"

// mcp.json

{
  "mcpServers": {
    "com-reglyze-mcp": {
      "type": "http",
      "url": "https://api.reglyze.com/mcp"
    }
  }
}

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

Changelog

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.

2 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
31 Jul 26 +3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
29 Jul 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
28 Jul 26 +1
- Server version: 1.0.0 → 1.1.0 functional
27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
26 Jul 26 59

First indexed and scored.

Show 5 earlier entries Hide earlier entries

Diagnostics

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 3 Aug 2026 · Probed https://api.reglyze.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=reglyze.com	CN=YE2,O=Let's Encrypt,C=US	31 Jul 2026	29 Oct 2026	ECDSA 256	ECDSA-SHA384	6191b2ee5524743ffc33678e74d39bd02f7
SANs: *.reglyze.com, reglyze.com
CN=YE2,O=Let's Encrypt,C=US (CA)	CN=Root YE,O=ISRG,C=US	3 Sept 2025	2 Sept 2028	ECDSA 384	ECDSA-SHA384	4df3b15dd6c0784c507cd37b58e6f115
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

DNSSEC insecure

Validation of api.reglyze.com. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
com.	present	19718	13	Verified
reglyze.com.	absent			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

Header	Value
strict-transport-security	max-age=15552000; includeSubDomains
x-content-type-options	nosniff

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://api.reglyze.com/mcp	Verified	200
http (plaintext)	http://api.reglyze.com/mcp	HTTPS enforced	301	https://api.reglyze.com/mcp

MCP tools — 7 exposed · ~594 tokens

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.

Tool Tokens

compliance_status My Reglyze compliance status ~43

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.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

documents_list My Reglyze compliance documents ~38

Requires a Reglyze API token. Lists YOUR organization's compliance documents (title, type, status, current version). Metadata only, not document content.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

incident_deadline_formats Incident notification deadlines per country ~95

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).

Input Output Examples

Name	Type	Req	Description
country	string	yes	ISO-2 country code
language	string	—	—

No output schema declared.

No examples provided.

incidents_list My Reglyze incidents ~31

Requires a Reglyze API token. Lists YOUR organization's recorded incidents (title, status, severity, detection date).

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

open_tasks My Reglyze open remediation tasks ~53

Requires a Reglyze API token. Lists YOUR organization's open remediation tasks. Optional filters: status, severity, overdue.

Input Output Examples

Name	Type	Req	Description
overdue	boolean	—	—
severity	string	—	—
status	string	—	—

No output schema declared.

No examples provided.

scope_check NIS2 scope check ~251

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 links.

Input Output Examples

Name	Type	Req	Description
additional_sectors	array	—	—
annual_balance_sheet_meur	number	—	—
annual_turnover_meur	number	—	Annual turnover in millions of EUR
cloud_provider	boolean	—	—
country	string	yes	ISO-2 country code of the organization (e.g. IT, PL, FR)
dns_provider	boolean	—	—
employee_count	integer	yes	—
language	string	—	—
qualified_trust_service_provider	boolean	—	—
sector	string	yes	Primary NIS2 sector id (see the sector list in the tool description)
sole_provider	boolean	—	Sole provider of a service essential to society in its Member State
tld_registry	boolean	—	—

No output schema declared.

No examples provided.

transposition_status NIS2 transposition status ~83

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.

Input Output Examples

Name	Type	Req	Description
country	string	—	ISO-2 country code; omit for all tracked countries
language	string	—	—

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	59
27 Jul	59
28 Jul	60
29 Jul	61
30 Jul	61
31 Jul	64
1 Aug	64
2 Aug	65
3 Aug	65