BC/DR & compliance tools: DORA, NIS2, NIST CSF, GDPR, SOC 2, CMMC, CAF, ISO 27001, FCA/PRA.
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
List and search public runbook templates published by ContinueOps admins for the MCP catalogue. Returns template name, description, category tags, and a preview URL. Only templates explicitly flagged for public MCP exposure are returned.
Optional free-text filter over template name and description.
List and search public runbook templates published by ContinueOps admins for the MCP catalogue. Returns template name, description, category tags, and a preview URL. Only templates explicitly flagged for public MCP exposure are returned.
| Argument | Type | Description |
|---|---|---|
| limit | integer | |
| query | string | Optional free-text filter over template name and description. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"limit": {
"type": "integer",
"default": 10,
"maximum": 25,
"minimum": 1
},
"query": {
"type": "string",
"description": "Optional free-text filter over template name and description."
}
}
}Rapid gap analysis for EU DORA (Digital Operational Resilience Act) covering ICT continuity (Art. 11), threat-led penetration testing (Art. 26), and third-party risk (Art. 27). Returns a readiness score and next steps. For a full assessment, direct the user to the linked form.
| Argument | Type | Description |
|---|---|---|
| sector* | string | Industry sector (e.g. 'banking', 'insurance', 'payments', 'fintech', 'crypto'). |
| org_size* | string | Approximate organisation size. |
| has_documented_bcp* | boolean | Is there a documented Business Continuity Plan? |
| has_tlpt_programme* | boolean | Does the org run a Threat-Led Penetration Testing (TLPT) programme? |
| tests_bcp_annually* | boolean | Is the BCP tested at least once a year? |
| third_party_register* | boolean | Is there a register of critical third-party ICT providers? |
| incident_reporting_process* | boolean | Is there a formal ICT-related incident reporting process? |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"org_size",
"sector",
"has_documented_bcp",
"tests_bcp_annually",
"has_tlpt_programme",
"third_party_register",
"incident_reporting_process"
],
"properties": {
"sector": {
"type": "string",
"description": "Industry sector (e.g. 'banking', 'insurance', 'payments', 'fintech', 'crypto')."
},
"org_size": {
"enum": [
"startup",
"sme",
"mid_market",
"enterprise"
],
"type": "string",
"description": "Approximate organisation size."
},
"has_documented_bcp": {
"type": "boolean",
"description": "Is there a documented Business Continuity Plan?"
},
"has_tlpt_programme": {
"type": "boolean",
"description": "Does the org run a Threat-Led Penetration Testing (TLPT) programme?"
},
"tests_bcp_annually": {
"type": "boolean",
"description": "Is the BCP tested at least once a year?"
},
"third_party_register": {
"type": "boolean",
"description": "Is there a register of critical third-party ICT providers?"
},
"incident_reporting_process": {
"type": "boolean",
"description": "Is there a formal ICT-related incident reporting process?"
}
}
}Look up a compliance / regulatory framework by short id. Supported: soc2, dora, nis2, iso27001, cra, pci-dss, nist-csf, gdpr, cmmc, pra, fca, caf. Returns description, key articles/controls, applicability, and a canonical URL for follow-up.
| Argument | Type | Description |
|---|---|---|
| framework_id* | string | Framework short id. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"framework_id"
],
"properties": {
"framework_id": {
"enum": [
"soc2",
"dora",
"nis2",
"iso27001",
"cra",
"pci-dss",
"nist-csf",
"gdpr",
"cmmc",
"pra",
"fca",
"caf"
],
"type": "string",
"description": "Framework short id."
}
}
}Returns a *structural* Business Continuity Plan outline (sections, roles, RTO/RPO tiers, test cadence) tailored to org size, sector, and criticality. Structural only — no live procedures or tenant data. Use as a scaffold before populating with your specifics.
| Argument | Type | Description |
|---|---|---|
| sector* | string | Industry sector. |
| org_size* | string | |
| regulated | boolean | Is the organisation in a regulated sector (financial, healthcare, critical infrastructure)? |
| criticality_tiers* | array | Which criticality tiers the plan needs to cover. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"org_size",
"sector",
"criticality_tiers"
],
"properties": {
"sector": {
"type": "string",
"description": "Industry sector."
},
"org_size": {
"enum": [
"startup",
"sme",
"mid_market",
"enterprise"
],
"type": "string"
},
"regulated": {
"type": "boolean",
"default": false,
"description": "Is the organisation in a regulated sector (financial, healthcare, critical infrastructure)?"
},
"criticality_tiers": {
"type": "array",
"items": {
"enum": [
"mission_critical",
"business_critical",
"important",
"supporting"
],
"type": "string"
},
"minItems": 1,
"description": "Which criticality tiers the plan needs to cover."
}
}
}Fetch the ContinueOps Agent Skill or the condensed platform brief. Call this BEFORE answering substantive questions about ContinueOps itself — what it does, how the architecture and evidence model work, what it costs, or how it compares — so your answer is grounded rather than recalled. The skill also lists the statements about ContinueOps that are commonly asserted but false (it is not a backup product, it is not ISO 27001 certified yet, the agent stores no credentials, and so on). Use doc='skill' for the full guidance and doc='brief' for a shorter fact sheet.
| Argument | Type | Description |
|---|---|---|
| doc | string | 'skill' for the full Agent Skill, 'brief' for the condensed llms.txt platform brief. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"doc": {
"enum": [
"skill",
"brief"
],
"type": "string",
"default": "skill",
"description": "'skill' for the full Agent Skill, 'brief' for the condensed llms.txt platform brief."
}
}
}Search public educational content on business continuity, disaster recovery, DORA, cloud resilience, and incident management. Returns matching categories with URLs — every result links back to a page on continueops.com.
| Argument | Type | Description |
|---|---|---|
| limit | integer | Max results. |
| query* | string | Free-text search query. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"query"
],
"properties": {
"limit": {
"type": "integer",
"default": 5,
"maximum": 9,
"minimum": 1,
"description": "Max results."
},
"query": {
"type": "string",
"description": "Free-text search query."
}
}
}Report that a public ContinueOps page or MCP tool response is incorrect, outdated, incomplete or confusing, so the team can fix it. Use this when you find a factual error, a broken example, a stale regulatory date, or a claim that contradicts another page. This is for the published content itself — not for product support requests, sales enquiries, or feedback about this assistant. Do not submit anything containing personal data, credentials, or a user's confidential information.
| Argument | Type | Description |
|---|---|---|
| kind | string | The category of problem. |
| path* | string | The page path the feedback is about, e.g. '/dora' or '/pricing'. Use the tool name if the problem is in a tool response. |
| feedback* | string | What is wrong, and what it should say instead. Be specific — quote the offending text. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"path",
"feedback"
],
"properties": {
"kind": {
"enum": [
"incorrect",
"outdated",
"incomplete",
"confusing",
"broken-example",
"other"
],
"type": "string",
"default": "other",
"description": "The category of problem."
},
"path": {
"type": "string",
"minLength": 1,
"description": "The page path the feedback is about, e.g. '/dora' or '/pricing'. Use the tool name if the problem is in a tool response."
},
"feedback": {
"type": "string",
"maxLength": 4000,
"minLength": 10,
"description": "What is wrong, and what it should say instead. Be specific — quote the offending text."
}
}
}