MCP HeartbeatTHE MCP OBSERVATORY
Public workspace

Explore

Evidence for your next connection.

Independent measurements of remote MCP servers. Every observation has a timestamp.

Read-only probes

MCP server · Code & DevOps

com.reglyze/mcp

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

Checks passed
11 / 22

3 failed · 8 not measured

Median response
121 ms

Median of successful probes over 7 days

30-day uptime
Not measured

Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.

Discovered tools
7

Tool definitions returned by this server

Independent monitoring

Health & checks

Status history

Responded

The server completed its last measured handshake. This is an observation, not a guarantee.

Last checked
Check summary by test group
Test areaPassedFailedUnmeasured
ConnectionCan a client connect and discover tools?
500
Reliability & speedDoes it respond consistently and quickly?
004
Access & authenticationWhat is required to use this server?
102
Tool qualityAre the tool definitions usable by an agent?
220
Publisher identityCan the publisher be traced to its source?
312

Unmeasured means there is not enough evidence to decide. How these checks work

Inspect individual checks 22 recorded

Core

  • Pass
    Reachable

    Latest probe returned HTTP 200 in 121 ms.

  • Pass
    Valid handshake

    protocolVersion 2025-11-25, serverInfo.name reglyze.

  • Pass
    Lists tools

    tools/list returned 7 tools.

  • Pass
    Current protocol

    Negotiated 2025-11-25. The bar is 2025-06-18 or newer.

  • Pass
    HTTPS

    The endpoint URL is https.

Performance

  • Not measured
    Fast (p50)

    Median latency 121 ms over 1 samples in 7 days. The bar is 1000 ms. Need at least 5 samples.

  • Not measured
    Consistent (p95)

    95th percentile 121 ms over 1 samples in 7 days. The bar is 3000 ms. Need at least 20 samples.

  • Not measured
    Reliable (uptime)

    1 of 1 attempts returned a tool list in 30 days (100%). The bar is 99%. Need at least 30 samples.

  • Not measured
    Stable tool list

    Fewer than two successful probes in 30 days, so tool-list stability is not measured.

Access

  • Pass
    Open access

    tools/list succeeded with no credential, and the record declares none.

  • Not measured
    Standard auth

    Auth is not required, so the OAuth metadata check does not apply.

  • Not measured
    Free tier cited

    No publisher quote has been checked.

Tools

  • Pass
    Tools described

    Every tool description is at least 20 characters.

  • Pass
    Valid input schemas

    Every inputSchema is a JSON Schema object.

  • Fail
    Parameters documented

    10 of 22 parameters have a description (45%). The bar is 80%.

  • Fail
    Safety hints

    7 tools set neither readOnlyHint nor destructiveHint.

Publisher

  • Pass
    Verified namespace

    Listed in the Official MCP Registry.

  • Pass
    Website matches publisher

    The website host matches the reverse-domain namespace.

  • Fail
    Source repo linked

    No repository URL is on file.

  • Not measured
    Repo owner matches

    This namespace is not an io.github login, so the owner comparison does not apply.

  • Pass
    Recently updated

    Updated 2026-07-15T13:32:18.137071Z, within 180 days.

  • Not measured
    Open-source licence

    No GitHub repository to ask about a licence.

Start using com.reglyze/mcp

Connect to this server

Choose your client, copy the configuration, then enable the server in your client’s MCP settings.

Run this command in your terminal, then restart Claude Code.

Claude Code

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

Capabilities

Tools 7

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.

Discovered
documents_list

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

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

Discovered
incidents_list

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

Discovered
open_tasks

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

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

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

Discovered

Recent measurements

Probe history

View status
Latest stored probes. Raw probe rows are kept for 14 days.
CheckedResultResponseTools
Connected121 ms7