Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.reglyze/mcp

REMOTE · API.REGLYZE.COM

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

Available components

−1 this week 78 Trust /100

Last scanned (21 hours ago)

Scores higher than 72% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Security

Trust breakdown (7 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 → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 915 tokens (~130/item across 7 items; 7 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage83
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 48% 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
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation 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.

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 →

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.

  • 18 Nov 26 0
    • Tool “incident_deadline_formats” rewrote its description, which is the text the model reads security
  • 17 Nov 26 −1
    • Tool “scope_check” rewrote its description, which is the text the model reads security
    • Schema quality: pass → fail ▼ functional
    • “scope_check” added an optional parameter “managed_security_service_provider” cosmetic
  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 9 Nov 26 +1
    • Stability: 0.97 → pass security
  • 8 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 7 Nov 26 0
    • Server version: 1.6.0 → 1.7.0 functional
  • 6 Nov 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
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 21 Nov 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 28 Sept 2026 27 Dec 2026 ECDSA 256 ECDSA-SHA384 663527cecc4025bfb51f6f8027fbb3a8202
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. DS published 19718 13 Verified
reglyze.com. 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
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
MCP tools · 7 exposed · ~915 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. 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 →

Tool Tokens
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 ~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 ~192

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 incident vocabulary (e.g. Italy's ACN IS-1..IS-4 incident typologies, which are types and not a severity scale, with their entity-class applicability).

NameTypeReqDescription
countrystringyesISO-2 country code
languagestring––
sectorstring–NIS2 sector id of the organisation. When given, `recipients` names who receives its notification: some countries route a whole sector to another body, and a rule over part of a sector comes back as a…

No output schema declared.

No examples provided.

incidents_list ~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 ~53

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

NameTypeReqDescription
overdueboolean––
severitystring––
statusstring––

No output schema declared.

No examples provided.

scope_check ~475

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), and whether the organization provides managed security services (essential from the small-enterprise size in Poland, and when medium-sized in Romania). Returns classification, reasoning, the national transposition law with its deviations, and next-step links.

NameTypeReqDescription
additional_sectorsarray––
annual_balance_sheet_meurnumber––
annual_turnover_meurnumber–Annual turnover in millions of EUR
cloud_providerboolean–Cloud computing provider: Annex I digital infrastructure, size-tested like any other entity (not size-independent)
countrystringyesISO-2 country code of the organization (e.g. IT, PL, FR)
dns_providerboolean––
employee_countintegeryes–
languagestring––
managed_security_service_providerboolean–Provides managed security services (incident handling, security tests, information-system audits, security consulting). Size-tested under the directive; in Poland an essential entity from the small-e…
public_ecn_providerboolean–Provider of public electronic communications networks or services: in scope regardless of size, essential from medium size (Art. 3(1)(c))
qualified_trust_service_providerboolean––
sectorstringyesPrimary NIS2 sector id (see the sector list in the tool description)
sole_providerboolean–Sole provider of a service essential to society in its Member State
tld_registryboolean––
trust_service_providerboolean–Trust service provider (eIDAS), qualified or not: in scope regardless of size; non-qualified ones are important unless large

No output schema declared.

No examples provided.

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.

NameTypeReqDescription
countrystring–ISO-2 country code; omit for all tracked countries
languagestring––

No output schema declared.

No examples provided.

Install

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

# add to Claude Code
claude mcp add --transport http com-reglyze-mcp 'https://api.reglyze.com/mcp'
Common questions

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 915 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 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 com.reglyze/mcp server?

VerifyMCP ran 12 checks on com.reglyze/mcp, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about com.reglyze/mcp: Authorization. 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.