Local MCP capabilities provider for Expo
Nothing to run from here
ContinueOps Public is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
7
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
BC/DR & compliance tools: DORA, NIS2, NIST CSF, GDPR, SOC 2, CMMC, CAF, ISO 27001, FCA/PRA.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http continueops-public-mcp https://tjcjvxibsrxizwuajypz.supabase.co/functions/v1/mcp
# 2 — ask your agent for something these tools do
# dora_readiness_assessment, explore_compliance_framework, generate_bcp_plan_structure and 4 more
ContinueOps Public costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
COAll 1 server
continueops1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http continueops-public-mcp https://tjcjvxibsrxizwuajypz.supabase.co/functions/v1/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
7 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 | Required | Notes |
|---|---|---|---|
| org_size | string | yes | Approximate organisation size. |
| sector | string | yes | Industry sector (e.g. 'banking', 'insurance', 'payments', 'fintech', 'crypto'). |
| has_documented_bcp | boolean | yes | Is there a documented Business Continuity Plan? |
| tests_bcp_annually | boolean | yes | Is the BCP tested at least once a year? |
| has_tlpt_programme | boolean | yes | Does the org run a Threat-Led Penetration Testing (TLPT) programme? |
| third_party_register | boolean | yes | Is there a register of critical third-party ICT providers? |
| incident_reporting_process | boolean | yes | 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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| framework_id | string | yes | 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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| org_size | string | yes | — |
| sector | string | yes | Industry sector. |
| criticality_tiers | array | yes | Which criticality tiers the plan needs to cover. |
| regulated | boolean | no | Is the organisation in a regulated sector (financial, healthcare, critical infrastructure)? |
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 | Required | Notes |
|---|---|---|---|
| query | string | yes | Free-text search query. |
| limit | integer | no | Max results. |
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 | Required | Notes |
|---|---|---|---|
| query | string | no | Optional free-text filter over template name and description. |
| limit | integer | no | — |
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 p
| Parameter | Type | Required | Notes |
|---|---|---|---|
| doc | string | no | 'skill' for the full Agent Skill, 'brief' for the condensed llms.txt platform brief. |
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 a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | string | yes | 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 | yes | What is wrong, and what it should say instead. Be specific — quote the offending text. |
| kind | string | no | The category of problem. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install ContinueOps Public or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.2.0.
0.2.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish ContinueOps Public can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.