BC/DR & compliance tools: DORA, NIS2, NIST CSF, GDPR, SOC 2, CMMC, CAF, ISO 27001, FCA/PRA.
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read from a real MCP initialize → tools/list handshake against the declared endpoint. No tool was ever invoked — tools/list is the read-only introspection call the protocol defines for this. It reflects what the server advertised at that moment; a hosted endpoint is not pinned to any version and can change without notice.
https://tjcjvxibsrxizwuajypz.supabase.co/functions/v1/mcp7 tools · 4335msdora_readiness_assessmentRapid 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.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.
| Parameter | Type | Description |
|---|---|---|
| org_size* | string | Approximate organisation size. |
| sector* | string | Industry sector (e.g. 'banking', 'insurance', 'payments', 'fintech', 'crypto'). |
| has_documented_bcp* | boolean | Is there a documented Business Continuity Plan? |
| tests_bcp_annually* | boolean | Is the BCP tested at least once a year? |
| has_tlpt_programme* | boolean | Does the org run a Threat-Led Penetration Testing (TLPT) programme? |
| 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? |
explore_compliance_frameworkLook 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.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.
| Parameter | Type | Description |
|---|---|---|
| framework_id* | string | Framework short id. |
generate_bcp_plan_structureReturns 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.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.
| Parameter | Type | Description |
|---|---|---|
| org_size* | string | — |
| sector* | string | Industry sector. |
| criticality_tiers* | array | Which criticality tiers the plan needs to cover. |
| regulated | boolean | Is the organisation in a regulated sector (financial, healthcare, critical infrastructure)? |
search_learning_labSearch 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.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.
| Parameter | Type | Description |
|---|---|---|
| query* | string | Free-text search query. |
| limit | integer | Max results. |
browse_runbook_templatesList 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.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.
| Parameter | Type | Description |
|---|---|---|
| query | string | Optional free-text filter over template name and description. |
| limit | integer | — |
get_continueops_skillFetch 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 a…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 a…
| Parameter | Type | Description |
|---|---|---|
| doc | string | 'skill' for the full Agent Skill, 'brief' for the condensed llms.txt platform brief. |
submit_feedbackReport 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 —…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 —…
| Parameter | Type | Description |
|---|---|---|
| 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. |
| kind | string | The category of problem. |
7 of 7 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
BC/DR & compliance tools: DORA, NIS2, NIST CSF, GDPR, SOC 2, CMMC, CAF, ISO 27001, FCA/PRA.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.