---
title: "Admin Tcc Recovery"
method: GET
path: "/admin/tcc-recovery"
---

# Admin Tcc Recovery

`GET /admin/tcc-recovery`

## Request

- Base URL: `https://api.local-mcp.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.local-mcp.com/admin/tcc-recovery`
- Auth: none declared. Required headers: `x-admin-key`

TCC block→recovery funnel — the churn lever. Of machines that hit a
Calendar/Contacts/Reminders permission wall in the window (a tool of that service
returned permission_denied / tcc_* ), what happened next:
  - recovered: every blocked service is now granted (effective state from outcomes)
  - partial:   some but not all blocked services granted
  - stuck_active: still denied AND still active (last heartbeat <7d) → INTERVENTION TARGET
  - churned_or_inactive: no heartbeat in 7d
The `stuck_machines` list is who to nudge (active, blocked, recoverable).

## Query parameters

- `days` integer

## Headers

- `x-admin-key` string, required

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/local-mcp/apis/lmcp-api.md) · [All operations](https://skmtc.dev/local-mcp/apis/lmcp-api/llms.txt) · [OpenAPI document](https://skmtc.dev/local-mcp/apis/lmcp-api/revisions/f1f1c502623a?raw)