Discovery, Auth, scope, and session failures
- Enter only https://tidyboard.org/mcp; remove headers and OAuth credentials.
- No Auth: verify the Tidyboard issuer plus S256/CIMD metadata and no registration endpoint.
- Callback failure: verify https://tidyboard.org/oauth/callback on the facade client.
- 403: follow exact-scope step-up consent. 401: reconnect.
Restrictions that are intentional, not bugs
A child account only sees its own missed work and can't act for another member. In finance, a child can manage only permitted own-wallet actions and create pending external-funding or purchase requests; approval-only actions return forbidden or approval_required.
Nothing on the meal plan counts toward macros until confirmed (confirm_planned_meal) or logged off-plan (log_macros) — the plan is only a projection.
A financial goal reaching funded does not spend the wallet. A child purchase request stays pending, while an owner/admin direct purchase request applies immediately. Tidyboard does not connect to a bank or verify wallet amounts against cash or statements.
Tool returns forbidden or not found for a record
Confirm the signed-in user belongs to the expected household and has permission for that record.