Version
READ

get_recovery_readiness

Read the Disaster Recovery readiness checklist for the creator the token acts for — every line with its state, and the totals the dashboard card shows. Takes no input.

Answer "how ready is this account for the next ban?". The checklist is the one the Disaster Recovery → Readiness page shows. The account's own lines come first: a second factor and a backup sign-in account. Then each installed connector's lines, worded by that connector and named by connector (Telegram's: a standby bot for every project, a standby for every channel and group, automatic failover, a live mirror). Last the two reminders: a copy of the content kept elsewhere, and a second human administrator in every space. Each line says whether it is in place, whether the plan lacks the feature (locked), the state in words and where the fix lives; the totals say how many verifiable lines are done. The payload is exactly what GET /v1/recovery/readiness returns.

The token behind the MCP session must hold it, or the call is refused with TOKEN_MISSING_ABILITY.

Runs the same action as

The REST endpoint and this tool share one action, so validation, permissions and events are identical.

Annotations

Read-only

It reads and never changes anything.

Arguments

This tool takes no arguments.

What it returns

{  "data": {    "prevention": true,    "completed": 4,    "total": 6,    "complete": false,    "items": [      {        "key": "second_factor",        "connector": null,        "connector_name": null,        "label": "Two-Factor Authentication or a Passkey",        "description": "Recovery moves your identity, so the account that runs it should be hard to take over.",        "icon": "shield-check",        "prevention": false,        "reminder": false,        "done": true,        "locked": false,        "detail": "Enabled",        "url": "https://app.subscriby.net/settings/security"      }    ]  },  "meta": {}}

done is true, false, or null when the platform can only remind (reminder: true); reminders never count toward total.

How it fails

AUTHENTICATION_REQUIRED

no authenticated user on the request.

TOKEN_MISSING_ABILITY

token lacks project-recovery:view-any.

How is this guide?

Last updated on