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

ContinueOps Public MCP

REMOTE · TJCJVXIBSRXIZWUAJYPZ.SUPABASE.CO · SCANNED AUG 3

BC/DR & compliance tools: DORA, NIS2, NIST CSF, GDPR, SOC 2, CMMC, CAF, ISO 27001, FCA/PRA.

+5 this week 68 Trust /100
Trust breakdown (6 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 →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability68
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1155 tokens (~165/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 Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 90% of tool parameters carry a description.Partial
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · tjcjvxibsrxizwuajypz.supabase.co

# add to Claude Code
claude mcp add --transport http com-continueops-continueops-public https://tjcjvxibsrxizwuajypz.supabase.co/functions/v1/mcp
# ~/.codex/config.toml
[mcp_servers.com-continueops-continueops-public]
url = "https://tjcjvxibsrxizwuajypz.supabase.co/functions/v1/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-continueops-continueops-public": {
      "type": "remote",
      "url": "https://tjcjvxibsrxizwuajypz.supabase.co/functions/v1/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-continueops-continueops-public --url https://tjcjvxibsrxizwuajypz.supabase.co/functions/v1/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-continueops-continueops-public:
    url: "https://tjcjvxibsrxizwuajypz.supabase.co/functions/v1/mcp"
// mcp.json
{
  "mcpServers": {
    "com-continueops-continueops-public": {
      "type": "http",
      "url": "https://tjcjvxibsrxizwuajypz.supabase.co/functions/v1/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 3 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Jul 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Jul 26 +1
    • Schema quality: 136 → 165 functional
    • Schema quality: good → excellent functional
  • 27 Jul 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 62

    First indexed and scored.

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 3 Aug 2026 · Probed https://tjcjvxibsrxizwuajypz.supabase.co/functions/v1/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=supabase.co CN=WE1,O=Google Trust Services,C=US 28 Jun 2026 26 Sept 2026 ECDSA 256 ECDSA-SHA256 1d2d53f65d874dfb0eead7aab0301afd
SANs: supabase.co, *.supabase.co
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b
DNSSEC insecure

Validation of tjcjvxibsrxizwuajypz.supabase.co. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
co. present 7786 8 Verified
supabase.co. absent 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=31536000; includeSubDomains; preload
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://tjcjvxibsrxizwuajypz.supabase.co/functions/v1/mcp Verified 200
http (plaintext) http://tjcjvxibsrxizwuajypz.supabase.co/functions/v1/mcp HTTPS enforced 301 https://tjcjvxibsrxizwuajypz.supabase.co/functions/v1/mcp
MCP tools — 7 exposed · ~909 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.

Tool Tokens
browse_runbook_templates ~75

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.

NameTypeReqDescription
limitinteger
querystringOptional free-text filter over template name and description.

No output schema declared.

No examples provided.

dora_readiness_assessment ~223

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.

NameTypeReqDescription
has_documented_bcpbooleanyesIs there a documented Business Continuity Plan?
has_tlpt_programmebooleanyesDoes the org run a Threat-Led Penetration Testing (TLPT) programme?
incident_reporting_processbooleanyesIs there a formal ICT-related incident reporting process?
org_sizestringyesApproximate organisation size.
sectorstringyesIndustry sector (e.g. 'banking', 'insurance', 'payments', 'fintech', 'crypto').
tests_bcp_annuallybooleanyesIs the BCP tested at least once a year?
third_party_registerbooleanyesIs there a register of critical third-party ICT providers?

No output schema declared.

No examples provided.

explore_compliance_framework ~90

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.

NameTypeReqDescription
framework_idstringyesFramework short id.

No output schema declared.

No examples provided.

generate_bcp_plan_structure ~125

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.

NameTypeReqDescription
criticality_tiersarrayyesWhich criticality tiers the plan needs to cover.
org_sizestringyes
regulatedbooleanIs the organisation in a regulated sector (financial, healthcare, critical infrastructure)?
sectorstringyesIndustry sector.

No output schema declared.

No examples provided.

get_continueops_skill ~153

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.

NameTypeReqDescription
docstring'skill' for the full Agent Skill, 'brief' for the condensed llms.txt platform brief.

No output schema declared.

No examples provided.

search_learning_lab ~68

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.

NameTypeReqDescription
limitintegerMax results.
querystringyesFree-text search query.

No output schema declared.

No examples provided.

submit_feedback ~175

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.

NameTypeReqDescription
feedbackstringyesWhat is wrong, and what it should say instead. Be specific — quote the offending text.
kindstringThe category of problem.
pathstringyesThe page path the feedback is about, e.g. '/dora' or '/pricing'. Use the tool name if the problem is in a tool response.

No output schema declared.

No examples provided.