10 actions in 5 pieces of software · ranked by words, meaning and measured trust · 632 ms
- 1CRA Incident Clockdemo or tutorialno passport yet
MCP serverrecord
- cra_incident_clock_utc_now
- cra_incident_clock_cra_reporting_clock
Calculate EU Cyber Resilience Act (Regulation (EU) 2024/2847) Art. 14 reporting deadlines and draft the three notifications. Returns: Deadlines (UTC), the content each report must carry, a draft payload, a content-hash receipt and the SSX360 next step.
- cra_incident_clock__check_login_status
- 2Skarp CRAfound in code, not yet checkedno passport yet
- report_incident
Open a reportable incident and start its statutory clocks.
- get_reporting_deadlines
Open reporting obligations, soonest first, with hours remaining.
- report_incident
- 3csoai-cra-art14-reporter-mcpfound in code, not yet checkedno passport yet
MCP servercsoai-org/csoai-cra-art14-reporter-mcp
- open_vulnerability_case
Open a CRA Article 14 case and start the three clocks.
- check_clock_status
How many hours remain on each clock for this case?
- check_cra_status
Days remaining until 11 Sept 2026 CRA Article 14 effective date.
- open_vulnerability_case
- 4io.github.CSOAI-ORG/agent-incident-relay-mcpfound in code, not yet checkedno passport yet
- check_clock_status
How many hours remain on each clock for this incident?
- check_clock_status
- 5io.github.CSOAI-ORG/cra-compliance-mcpfound in code, not yet checkedno passport yet
- enforcement_status
Current CRA enforcement timeline + key deadlines.
- enforcement_status
Labels are the instruments' verdict and are never changed by ranking. Agents and robots get this same answer as JSON at /api/v1/find?q=…&answer=1 and through the MCP server.