Other · Remote MCP server
ContinueOps Public MCP
BC/DR & compliance tools: DORA, NIS2, NIST CSF, GDPR, SOC 2, CMMC, CAF, ISO 27001, FCA/PRA.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.continueops/continueops-public- Version
- 0.2.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-07-06
- Updated
- 2026-07-06
- Publisher
- com.continueops
- Namespace
- Namespace verified by the MCP Registry via the domain continueops.com · how
- Website
- www.continueops.com
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://tjcjvxibsrxizwuajypz.supabase.co/functions/v1/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- continueops-public 0.2.0 · protocol 2025-06-18
- Tools discovered
- 7:
dora_readiness_assessment,explore_compliance_framework,generate_bcp_plan_structure,search_learning_lab,browse_runbook_templates,get_continueops_skill,submit_feedback - Checked on
- 2026-10-05
How to connect ContinueOps Public MCP
ContinueOps Public MCP is a remote MCP server: there is nothing to install. Its endpoint is https://tjcjvxibsrxizwuajypz.supabase.co/functions/v1/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| ContextDB Customer MemoryCustomer memory with recall, confirmation, forgetting, and pre-action evidence checks. | Remote · HTTPLive check: sign-in required |
| ContextDB MemoryLocal-first durable AI memory with policy-bound recall and a typed project graph. | Local · stdio |
| ContextOverflowDescribe what's going wrong with your AI; get the named technique both of you can read. No auth. | Remote · HTTPLive check: ✓ handshake |
| Contextual MCP ServerRAG-enabled MCP server using Contextual AI. Supports single-agent and multi-agent modes. | Local · stdio |
| ContinuityPrivate story bible for fiction writers, shared with AI assistants over MCP. | Remote · HTTPLive check: ✓ handshake |
| Continuity EvidenceA bounded local evidence tool with current agent permission checks and durable retry handling. | Local · stdio |
| ContrackoImport, review and track renewals on your business contracts from your AI assistant. | Remote & Local · HTTP, stdioLive check: sign-in required |
| Contract Clause Library AssembleAssemble a contract from a searchable clause library, with variables filled in or flagged as missing. | Local · stdio |