com.reglyze/mcp
REMOTE · API.REGLYZE.COM · SCANNED SEP 24
NIS2 tools: scope check, EU transposition, incident deadlines, and your own org's status (token).
Available components
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 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 Usability72
- 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the com.reglyze/mcp server?
com.reglyze/mcp is a hosted endpoint at https://api.reglyze.com/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 · api.reglyze.com
claude mcp add --transport http com-reglyze-mcp 'https://api.reglyze.com/mcp'
{
"mcpServers": {
"com-reglyze-mcp": {
"url": "https://api.reglyze.com/mcp"
}
}
} {
"servers": {
"com-reglyze-mcp": {
"type": "http",
"url": "https://api.reglyze.com/mcp"
}
}
} [mcp_servers.com-reglyze-mcp] url = "https://api.reglyze.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-reglyze-mcp": {
"type": "remote",
"url": "https://api.reglyze.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-reglyze-mcp --url 'https://api.reglyze.com/mcp' --transport streamable-http
mcp_servers:
com-reglyze-mcp:
url: "https://api.reglyze.com/mcp" {
"McpServers": {
"com-reglyze-mcp": {
"Transport": "http",
"Url": "https://api.reglyze.com/mcp"
}
}
} assistant mcp add com-reglyze-mcp -t streamable-http -u 'https://api.reglyze.com/mcp'
{
"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.
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.
- 22 Sept 26 0
- Server version: 1.3.0 → 1.4.0 functional
- 26 Aug 26 78
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 22 Aug 26 0
- Server version: 1.2.0 → 1.3.0 functional
- 11 Aug 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
- 8 Aug 26 0
- Server version: 1.1.0 → 1.2.0 functional
- 31 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
- 28 Jul 26 0
- Server version: 1.0.0 → 1.1.0 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 24 Sept 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 |
Background: What to check on a remote MCP endpoint →
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
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 |
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 →
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 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 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).
| 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 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.
| 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.
| 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.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | ISO-2 country code; omit for all tracked countries |
| language | string | – | – |
No output schema declared.
No examples provided.
What is the com.reglyze/mcp server?
com.reglyze/mcp is listed in the public MCP registry as com.reglyze/mcp. NIS2 tools: scope check, EU transposition, incident deadlines, and your own org's status (token). This page covers its hosted endpoint (https://api.reglyze.com/mcp).
Is the com.reglyze/mcp server safe to use?
com.reglyze/mcp scores 78 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 com.reglyze/mcp server expose?
com.reglyze/mcp exposes 7 tools: scope_check, transposition_status, incident_deadline_formats, compliance_status, documents_list, and 2 more. Their descriptions and schemas cost roughly 594 tokens of context every time the server is loaded.
Does the com.reglyze/mcp server require authentication?
No. We connected to com.reglyze/mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.reglyze/mcp server still maintained?
com.reglyze/mcp is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.