Familia
REMOTE · MCP.FAMILY.ASYNQ.ORG · SCANNED SEP 21
Private family planner for schedules, tasks, checklists, attachments, and availability.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security91
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 4820 tokens (~192/item across 25 items; 25 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
- Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 99% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 26 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Familia MCP server?
Familia is a hosted endpoint at https://mcp.family.asynq.org/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.family.asynq.org
claude mcp add --transport http com-familiaplanner-familia 'https://mcp.family.asynq.org/mcp'
{
"mcpServers": {
"com-familiaplanner-familia": {
"url": "https://mcp.family.asynq.org/mcp"
}
}
} {
"servers": {
"com-familiaplanner-familia": {
"type": "http",
"url": "https://mcp.family.asynq.org/mcp"
}
}
} [mcp_servers.com-familiaplanner-familia] url = "https://mcp.family.asynq.org/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-familiaplanner-familia": {
"type": "remote",
"url": "https://mcp.family.asynq.org/mcp",
"enabled": true
}
}
} openclaw mcp add com-familiaplanner-familia --url 'https://mcp.family.asynq.org/mcp' --transport streamable-http
mcp_servers:
com-familiaplanner-familia:
url: "https://mcp.family.asynq.org/mcp" {
"McpServers": {
"com-familiaplanner-familia": {
"Transport": "http",
"Url": "https://mcp.family.asynq.org/mcp"
}
}
} assistant mcp add com-familiaplanner-familia -t streamable-http -u 'https://mcp.family.asynq.org/mcp'
{
"mcpServers": {
"com-familiaplanner-familia": {
"type": "http",
"url": "https://mcp.family.asynq.org/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “familia_batch_write” rewrote its description, which is the text the model reads security
- Tool “familia_create_list_task” rewrote its description, which is the text the model reads security
- Tool “familia_create_plan” rewrote its description, which is the text the model reads security
- Tool “familia_create_task” rewrote its description, which is the text the model reads security
- Tool “familia_delete_plan” rewrote its description, which is the text the model reads security
- Tool “familia_update_plan” rewrote its description, which is the text the model reads security
- Tool “familia_update_task” rewrote its description, which is the text the model reads security
- Tool “familia_create_list_task” is now declared destructive security
- Tool “familia_create_plan” is now declared destructive security
- Tool “familia_create_task” is now declared destructive security
- Server version: 0.10.3 → 0.10.4 functional
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 0
- Server version: 0.9.0 → 0.10.3 functional
- “familia_get_day_overview” added an optional parameter “includeCompleted” cosmetic
- “familia_search_items” added an optional parameter “offset” cosmetic
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Probed https://mcp.family.asynq.org/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=asynq.org | CN=WE1,O=Google Trust Services,C=US | 31 Aug 2026 | 29 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 75c04a731054fb5a0ea21ea61c46f05c |
| SANs: asynq.org, mcp.family.asynq.org, *.mcp.family.asynq.org | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.family.asynq.org. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| org. | present | 26974 | 8 | Verified |
| asynq.org. | present | 2371 | 13 | Verified |
| mcp.family.asynq.org. | Verified address RRset verified with the apex keys |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://mcp.family.asynq.org/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://mcp.family.asynq.org/.well-known/oauth-protected-resource"Protected resource metadata
| Document | https://mcp.family.asynq.org/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.family.asynq.org |
| Authorisation server | https://api.family.asynq.org |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.family.asynq.org/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.family.asynq.org/mcp | HTTPS enforced | 301 | https://mcp.family.asynq.org/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
familia_attach_image Attach image ~230
Use this when the user asks to attach a JPEG, PNG, or WebP image to an existing Familia task or plan. Provide either dataUrl or base64Data plus mimeType. Do not use for non-image files.
| Name | Type | Req | Description |
|---|---|---|---|
| base64Data | string | – | Raw base64 image bytes when dataUrl is not provided. |
| dataUrl | string | – | Image data URL, e.g. data:image/png;base64,... |
| fileName | string | – | Optional image filename shown in attachment metadata. |
| height | integer | – | Optional image height in pixels. |
| mimeType | string | – | Required when base64Data is provided without a dataUrl. |
| replaceExistingPhoto | boolean | – | When true, replaces the latest existing photo attachment for the target. |
| targetId | string | yes | Task id when targetType is task, or plan item id when targetType is plan. |
| targetType | string | yes | Type of Familia item that should receive the image. |
| timezone | string | – | IANA timezone used by the backend request. |
| width | integer | – | Optional image width in pixels. |
| Name | Type | Req | Description |
|---|---|---|---|
| attachment | object | – | – |
| attachmentId | string | yes | – |
| link | string | – | – |
| targetId | string | – | – |
| targetType | string | – | – |
No examples provided.
familia_batch_write Batch write Familia items ~216
Use this when the user explicitly asks to create or modify multiple Familia tasks, list tasks, plans, or task attachments in one request, or when one prompt contains multiple standalone dated actions that should become separate tasks. When the same task or plan repeats, use repeatRule/rrule on one operation instead of creating duplicate one-time operations. For a main event/trip plus clearly related dated actions, prefer one create_plan operation with relatedTasks. Internally this runs bounded individual write operations one by one; it does not create a backend transaction. Operations can queue assignment notifications and reminders; delivered notifications cannot be recalled.
| Name | Type | Req | Description |
|---|---|---|---|
| continueOnError | boolean | – | When true, continue after a failed operation and return partial-success results. Defaults to false. |
| idempotencyKey | – | – | – |
| operations | array | yes | Ordered write operations to run. Later operations cannot reference IDs created by earlier operations in the same batch unless the user already provided those IDs. |
| timezone | string | – | Default IANA timezone for operations that omit their own timezone. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| failed | integer | yes | – |
| results | array | yes | – |
| succeeded | integer | yes | – |
No examples provided.
familia_cancel_task Cancel task ~88
Use this only when the user explicitly asks to cancel, archive, or hide an existing Familia task without permanently deleting the record. Do not use to mark a task done; use familia_update_task instead.
| Name | Type | Req | Description |
|---|---|---|---|
| agreementId | string | yes | Familia task id to cancel. This field is named agreementId for legacy backend compatibility. |
| timezone | string | – | IANA timezone used by the backend request. |
| Name | Type | Req | Description |
|---|---|---|---|
| agreementId | string | yes | – |
| deleted | boolean | yes | – |
| deletionType | string | – | – |
| link | string | yes | – |
| status | string | – | – |
| taskId | string | – | – |
No examples provided.
familia_create_list_attachment Create list attachment ~138
Use this when the user asks to add a new checklist, shopping list, packing list, or structured subtasks to an existing Familia task or plan. Do not use for editing an existing attachment.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | Checklist/list items to attach. Supports nested subtasks. |
| targetId | string | yes | Task id when targetType is task, or plan item id when targetType is plan. |
| targetType | string | yes | Type of Familia item that should receive the list. |
| timezone | string | – | IANA timezone used by the backend request. |
| title | string | – | Optional title shown on the attached checklist/list. |
| Name | Type | Req | Description |
|---|---|---|---|
| attachment | object | – | – |
| attachmentId | string | yes | – |
| link | string | – | – |
| targetId | string | – | – |
| targetType | string | – | – |
No examples provided.
familia_create_list_task Create list task ~488
Use this when the user asks to create a shopping list, packing list, checklist, or Familia task with list items. If the same list task repeats across several days, weeks, or months, provide repeatRule and create one recurring list task instead of multiple one-time tasks. Do not use when editing an existing list attachment. Assigning to another household member queues a push notification; schedules can also queue reminders, and delivered notifications cannot be recalled.
| Name | Type | Req | Description |
|---|---|---|---|
| allDay | boolean | – | Whether the due date is an all-day task. |
| assigneeUserId | string | – | Optional Familia user id responsible for the task. |
| description | string | – | Optional task details, notes, or context. |
| dueAt | string | – | Accepts YYYY-MM-DD for all-day items or an RFC 3339 datetime. When using a datetime without an offset, provide timezone. |
| householdId | string | yes | Familia household id where the list task should be created. |
| idempotencyKey | string | – | Optional stable retry key. Reusing the same key for the same create operation returns the original result instead of creating a duplicate. |
| items | array | yes | Checklist items to attach to the new task. Supports nested subtasks. |
| leadMinutes | integer | – | Reminder lead time in minutes before dueAt. Defaults to 0. |
| listTitle | string | – | Optional title shown on the attached list. Defaults to the task title. |
| ownerUserId | string | – | Optional Familia user id that owns the task. |
| recurrenceEndDate | string | – | Optional YYYY-MM-DD end date for a recurring schedule. Use this for bounded repeats such as "this week", "for three days", or "until Sunday". |
| repeatRule | string | – | Optional RFC 5545 RRULE, e.g. FREQ=DAILY;INTERVAL=2 or FREQ=WEEKLY;BYDAY=MO,WE. Use this when the user says the same task or plan repeats across days, weeks, or months; create one recurring schedule… |
| timezone | string | – | IANA timezone for dueAt, e.g. Europe/Prague. |
| title | string | yes | Task title, e.g. “Groceries” or “Pack for trip”. |
| Name | Type | Req | Description |
|---|---|---|---|
| agreementId | string | yes | – |
| attachmentCreated | boolean | – | – |
| attachmentError | string | – | – |
| deeplink | string | yes | – |
| schedule | object | – | – |
| taskId | string | – | – |
| todoListAttachment | – | – | – |
No examples provided.
familia_create_plan Create plan ~591
Use this when the user asks to create a Familia plan item for an event, trip, holiday, school, activity, care coverage, travel, chore block, or other scheduled family plan. If the same plan repeats across several days, weeks, or months, provide rrule and create one recurring plan instead of multiple one-time plans. If the user gives multiple dated or timed actions that clearly belong to the plan, such as flights, leaving for the airport, pickup, packing, check-in, or return travel, put the main event/trip in the plan and create each dated action as a relatedTasks entry instead of stuffing them all into notes. Do not use for standalone responsibility-style task reminders; use familia_create_task or familia_batch_write instead. Related tasks assigned to another household member can queue push notifications; schedules can trigger reminders, and delivered notifications cannot be recalled.
| Name | Type | Req | Description |
|---|---|---|---|
| agreementIds | array | – | Optional existing related task ids to link to the plan. |
| allDay | boolean | – | Whether the plan is all-day. |
| endAt | string | – | Optional ISO datetime. |
| householdId | string | yes | Familia household id where the plan should be created. |
| idempotencyKey | – | – | – |
| kind | string | – | Plan category. Use event when no more specific category fits. |
| location | string | – | Optional location, venue, or address. |
| notes | string | – | Optional plan notes or context. Do not use notes as the only place for separate dated actions; use relatedTasks for each distinct action with its own date or time. |
| participantUserIds | array | – | Optional Familia user ids participating in the plan. |
| recurrenceEndDate | string | – | Optional YYYY-MM-DD end date for a recurring schedule. Use this for bounded repeats such as "this week", "for three days", or "until Sunday". |
| relatedTasks | array | – | Optional new tasks to create and link to this plan. Use one related task per distinct dated or timed action, such as leaving for an airport, outbound flight, return flight, pickup, packing, or check-… |
| requiresConfirmation | boolean | – | Whether participants should confirm coverage or attendance. |
| rrule | string | – | Optional RFC 5545 RRULE, e.g. FREQ=DAILY;INTERVAL=2 or FREQ=WEEKLY;BYDAY=MO,WE. Use this when the user says the same task or plan repeats across days, weeks, or months; create one recurring schedule… |
| startAt | string | – | Optional ISO datetime. |
| timezone | string | – | IANA timezone for startAt/endAt, e.g. Europe/Prague. |
| title | string | yes | Short plan title, e.g. "School concert" or "Long weekend trip". |
| Name | Type | Req | Description |
|---|---|---|---|
| link | string | yes | – |
| occurrenceIds | array | yes | – |
| planItemId | string | yes | – |
| relatedTaskIds | array | – | – |
| relatedTasks | array | – | – |
| schedule | object | – | – |
No examples provided.
familia_create_task Create task ~493
Use this when the user asks to create a responsibility-style Familia task, agreement, reminder, or chore. If the same task repeats across several days, weeks, or months, provide repeatRule and create one recurring task instead of multiple one-time tasks. Do not use for calendar-style events, trips, school activities, or holidays; use familia_create_plan instead. When the primary intent is a shopping list, packing list, or standalone checklist, use familia_create_list_task. Assigning to another household member queues a push notification; schedules can also queue reminders, and delivered notifications cannot be recalled.
| Name | Type | Req | Description |
|---|---|---|---|
| allDay | boolean | – | Whether the due date is an all-day task. |
| assigneeUserId | string | – | Optional Familia user id responsible for the task. |
| description | string | – | Optional task details, notes, or context. |
| dueAt | string | – | Accepts YYYY-MM-DD for all-day items or an RFC 3339 datetime. When using a datetime without an offset, provide timezone. |
| householdId | string | yes | Familia household id where the task should be created. |
| idempotencyKey | string | – | Optional stable retry key. Reusing the same key for the same create operation returns the original result instead of creating a duplicate. |
| leadMinutes | integer | – | Reminder lead time in minutes before dueAt. Defaults to 0. |
| ownerUserId | string | – | Optional Familia user id that owns the task. |
| recurrenceEndDate | string | – | Optional YYYY-MM-DD end date for a recurring schedule. Use this for bounded repeats such as "this week", "for three days", or "until Sunday". |
| repeatRule | string | – | Optional RFC 5545 RRULE, e.g. FREQ=DAILY;INTERVAL=2 or FREQ=WEEKLY;BYDAY=MO,WE. Use this when the user says the same task or plan repeats across days, weeks, or months; create one recurring schedule… |
| timezone | string | – | IANA timezone for dueAt, e.g. Europe/Prague. |
| title | string | yes | Short task title, e.g. "Pay school fee" or "Take bins out". |
| todoList | object | – | Optional checklist/list to attach to the created task. |
| Name | Type | Req | Description |
|---|---|---|---|
| agreementId | string | yes | – |
| attachmentCreated | boolean | – | – |
| attachmentError | string | – | – |
| deeplink | string | yes | – |
| schedule | object | – | – |
| taskId | string | – | – |
| todoListAttachment | – | – | – |
No examples provided.
familia_delete_attachment Delete attachment ~70
Use this only when the user explicitly asks to delete or remove an existing Familia photo, checklist, or list attachment. Do not use for hiding or summarizing attachments.
| Name | Type | Req | Description |
|---|---|---|---|
| attachmentId | string | yes | Familia attachment id to delete. |
| timezone | string | – | IANA timezone used by the backend request. |
| Name | Type | Req | Description |
|---|---|---|---|
| attachmentId | string | yes | – |
| deleted | boolean | yes | – |
No examples provided.
familia_delete_plan Delete plan ~100
Use this only when the user explicitly asks to delete, remove, or cancel an existing Familia plan item. Do not use to reschedule or complete a plan; use familia_update_plan instead. Cancelling a shared plan can update existing guest copies and queue cancellation notifications; delivered notifications cannot be recalled.
| Name | Type | Req | Description |
|---|---|---|---|
| planItemId | string | yes | Familia plan item id to delete or cancel. |
| timezone | string | – | IANA timezone used by the backend request. |
| Name | Type | Req | Description |
|---|---|---|---|
| deleted | boolean | – | – |
| link | string | yes | – |
| planItemId | string | yes | – |
No examples provided.
familia_delete_task Permanently delete task ~84
Use this only when the user explicitly asks to permanently delete or hard delete an existing Familia task. This removes the record and related task schedules, occurrences, reminders, and attachments.
| Name | Type | Req | Description |
|---|---|---|---|
| agreementId | string | yes | Familia task id to permanently delete. This field is named agreementId for legacy backend compatibility. |
| timezone | string | – | IANA timezone used by the backend request. |
| Name | Type | Req | Description |
|---|---|---|---|
| agreementId | string | yes | – |
| deleted | boolean | yes | – |
| deletionType | string | – | – |
| link | string | yes | – |
| status | string | – | – |
| taskId | string | – | – |
No examples provided.
familia_find_free_days Find consecutive free days ~251
Use this when the user asks to find free days, open dates, vacation windows, long weekends, or consecutive days without hard Familia availability blockers. Do not use for listing tasks on one known date.
| Name | Type | Req | Description |
|---|---|---|---|
| blockingPolicy | string | – | availability ignores soft reminders such as chores, checklists, birthdays/name days and ordinary tasks; strict treats any timeline item as busy. |
| busyEndHour | integer | – | End hour of the day window to consider busy. Defaults to 24. |
| busyStartHour | integer | – | Start hour of the day window to consider busy. Defaults to 0. |
| consecutiveDays | integer | – | Required length of each free-day run. Defaults to 4. |
| horizonDays | integer | – | How many days to scan forward from startDate. Defaults to 120. |
| householdId | string | – | Optional Familia household id. Omit to use all accessible households. |
| limit | integer | – | Maximum number of free-day runs to return. Defaults to 8. |
| startDate | string | – | YYYY-MM-DD or ISO datetime. Defaults to today. |
| timezone | string | – | IANA timezone used for day boundaries, e.g. Europe/Prague. |
| Name | Type | Req | Description |
|---|---|---|---|
| blockingPolicy | string | yes | – |
| caveat | string | yes | – |
| consecutiveDays | integer | yes | – |
| count | integer | yes | – |
| horizonDays | integer | yes | – |
| runs | array | yes | – |
| securityNotice | string | yes | – |
| startDate | string | yes | – |
| timezone | string | yes | – |
No examples provided.
familia_get_day_overview Get day overview ~176
Use this when the user asks for Familia items on a specific date or in a specific time window. Includes tasks, plans, and connected calendar events. Do not use for broad text search or multi-week availability.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Date as YYYY-MM-DD, ISO datetime, or omitted for today in the selected timezone. |
| endAt | string | – | Optional ISO datetime for a narrower time window. Defaults to one hour after startAt. |
| householdId | string | – | Optional Familia household id. Omit to aggregate across all accessible memberships. |
| includeCompleted | boolean | – | Include completed tasks when looking through history. |
| startAt | string | – | Optional ISO datetime for a narrower time window. |
| timezone | string | – | IANA timezone, defaults to ASYNQ_TIMEZONE or the local runtime timezone. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| counts | object | yes | – |
| date | string | yes | – |
| householdId | string|null | yes | – |
| intent | string | – | – |
| items | array | yes | – |
| links | object | yes | – |
| overdueSummary | – | yes | – |
| securityNotice | string | yes | – |
| timezone | string | yes | – |
| window | – | yes | – |
No examples provided.
familia_get_inbox Inbox / needs attention ~107
Use this when the user asks for inbox, items needing attention, overdue tasks, past leftovers, unfinished responsibilities, or what is waiting on them.
| Name | Type | Req | Description |
|---|---|---|---|
| householdId | string | – | Optional Familia household id. Omit to use all accessible households. |
| limit | integer | – | Maximum number of attention items to return. Defaults to 20. |
| timezone | string | – | IANA timezone, e.g. Europe/Prague. Defaults to ASYNQ_TIMEZONE or runtime timezone. |
| Name | Type | Req | Description |
|---|---|---|---|
| categories | – | yes | – |
| count | integer | yes | – |
| date | string | yes | – |
| householdId | string|null | yes | – |
| items | array | yes | – |
| timezone | string | yes | – |
No examples provided.
familia_get_next_up Next up ~163
Use this when the user asks what is next, what they should do now, their next task, or the next upcoming family item. Defaults to personal assigned items; use household scope only for family-wide wording. Never describe owner-only tasks as assigned to the current user.
| Name | Type | Req | Description |
|---|---|---|---|
| householdId | string | – | Optional Familia household id. Omit to use all accessible households. |
| limit | integer | – | Maximum number of upcoming items to return. Defaults to 5. |
| scope | string | – | Use personal for “my”, “for me”, or “what should I do”; use household for family-wide next items. |
| timezone | string | – | IANA timezone, e.g. Europe/Prague. Defaults to ASYNQ_TIMEZONE or runtime timezone. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| currentUserId | string|null | yes | – |
| householdId | string|null | yes | – |
| items | array | yes | – |
| now | string | yes | – |
| otherHouseholdItems | array | – | – |
| overdueSummary | object | yes | – |
| scope | string | yes | – |
| timezone | string | yes | – |
No examples provided.
familia_get_today_schedule What am I doing today? ~99
Use this when the user asks about today's agenda, today's tasks, what they are doing today, or what they should do today. Includes tasks, plans, Google/calendar events, and an overdue summary.
| Name | Type | Req | Description |
|---|---|---|---|
| householdId | string | – | Optional Familia household id. Omit to use all accessible households. |
| timezone | string | – | IANA timezone, e.g. Europe/Prague. Defaults to ASYNQ_TIMEZONE or runtime timezone. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| counts | object | yes | – |
| date | string | yes | – |
| householdId | string|null | yes | – |
| intent | string | – | – |
| items | array | yes | – |
| links | object | yes | – |
| overdueSummary | – | yes | – |
| securityNotice | string | yes | – |
| timezone | string | yes | – |
| window | – | yes | – |
No examples provided.
familia_get_tomorrow_schedule What am I doing tomorrow? ~102
Use this when the user asks about tomorrow's agenda, tomorrow's tasks, tomorrow's plans, or what they should prepare for tomorrow. Includes tasks, plans, Google/calendar events, and an overdue summary.
| Name | Type | Req | Description |
|---|---|---|---|
| householdId | string | – | Optional Familia household id. Omit to use all accessible households. |
| timezone | string | – | IANA timezone, e.g. Europe/Prague. Defaults to ASYNQ_TIMEZONE or runtime timezone. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| counts | object | yes | – |
| date | string | yes | – |
| householdId | string|null | yes | – |
| intent | string | – | – |
| items | array | yes | – |
| links | object | yes | – |
| overdueSummary | – | yes | – |
| securityNotice | string | yes | – |
| timezone | string | yes | – |
| window | – | yes | – |
No examples provided.
familia_get_weekly_overview Weekly overview ~133
Use this when the user asks about this week, the next week, upcoming days, family schedule for the week, or a multi-day planning overview.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Number of days to include, from 1 to 14. Defaults to 7. |
| householdId | string | – | Optional Familia household id. Omit to use all accessible households. |
| startDate | string | – | YYYY-MM-DD or ISO datetime. Defaults to today. |
| timezone | string | – | IANA timezone, e.g. Europe/Prague. Defaults to ASYNQ_TIMEZONE or runtime timezone. |
| Name | Type | Req | Description |
|---|---|---|---|
| dayOverviews | array | yes | – |
| days | integer | yes | – |
| endDate | string | yes | – |
| householdId | string|null | yes | – |
| overdueSummary | object | yes | – |
| startDate | string | yes | – |
| timezone | string | yes | – |
No examples provided.
familia_list_attachments List attachments ~105
Use this when the user asks what photos, checklists, or list attachments are attached to an existing Familia task or plan. Use before editing an existing list attachment when the attachment id is unknown.
| Name | Type | Req | Description |
|---|---|---|---|
| targetId | string | yes | Task id when targetType is task, or plan item id when targetType is plan. |
| targetType | string | yes | Type of Familia item that owns the attachments. |
| timezone | string | – | IANA timezone used by the backend request. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| items | array | yes | – |
| targetId | string | yes | – |
| targetType | string | yes | – |
No examples provided.
familia_list_household_members List Familia household members ~77
Use this when a task or plan must be assigned to, owned by, or shared with a named household member and their Familia user id is not already known.
| Name | Type | Req | Description |
|---|---|---|---|
| householdId | string | yes | Familia household id whose active and pending members should be listed. |
| timezone | string | – | IANA timezone used by the backend request. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| householdId | string | yes | – |
| members | array | yes | – |
No examples provided.
familia_list_households List Familia households ~53
Use this when the user asks which Familia households, families, or shared boards are available. Includes member names and user ids for assigning tasks or plans. Do not use for listing tasks, plans, or calendar events.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| configuration | object | yes | – |
| currentUser | – | – | – |
| households | array | yes | – |
| selectedHouseholdId | string|null | yes | – |
No examples provided.
familia_list_past_due List past leftovers ~114
Use this when the user asks for overdue items, past leftovers, missed tasks, unfinished items from previous days, or Czech “resty”. Calendar events are excluded.
| Name | Type | Req | Description |
|---|---|---|---|
| householdId | string | – | Optional Familia household id. Omit to use all accessible households. |
| limit | integer | – | Maximum number of past-due items to return. Defaults to 20. |
| timezone | string | – | IANA timezone, e.g. Europe/Prague. Defaults to ASYNQ_TIMEZONE or runtime timezone. |
| Name | Type | Req | Description |
|---|---|---|---|
| categories | – | yes | – |
| count | integer | yes | – |
| date | string | yes | – |
| householdId | string|null | yes | – |
| items | array | yes | – |
| timezone | string | yes | – |
No examples provided.
familia_search_items Search family board items ~141
Use this when the user asks to find Familia tasks, plans, or connected calendar events by title, notes, description, or location. Do not use for public web search or unrelated document search.
| Name | Type | Req | Description |
|---|---|---|---|
| householdId | string | – | Optional Familia household id. Omit to search all accessible households. |
| limit | integer | – | Maximum number of matches to return. Defaults to 12. |
| offset | integer | – | Pagination offset, defaults to 0. |
| query | string | yes | Search text, e.g. "dentist", "school trip", or "groceries". |
| timezone | string | – | IANA timezone used when formatting matched timeline items. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| hasMore | boolean | yes | – |
| matches | array | yes | – |
| query | string | yes | – |
| securityNotice | string | yes | – |
| totalCount | integer | yes | – |
No examples provided.
familia_update_list_attachment Update list attachment ~113
Use this when the user asks to edit, add, remove, reorder, or mark items in an existing Familia checklist/list attachment. This replaces the existing list content; list attachments first if the attachment id is unknown.
| Name | Type | Req | Description |
|---|---|---|---|
| attachmentId | string | yes | Familia attachment id for the checklist/list to replace. |
| items | array | yes | Full replacement checklist/list content. Supports nested subtasks. |
| timezone | string | – | IANA timezone used by the backend request. |
| title | string | – | Optional replacement list title. |
| Name | Type | Req | Description |
|---|---|---|---|
| attachment | object | – | – |
| attachmentId | string | yes | – |
| link | string | – | – |
| targetId | string | – | – |
| targetType | string | – | – |
No examples provided.
familia_update_plan Update plan ~253
Use this when the user asks to rename, reschedule, move, update location, link tasks, change participants, or otherwise edit an existing Familia plan. Do not use to create a new plan. Updates can synchronize copies already imported by invited guests and queue notifications; delivered notifications cannot be recalled.
| Name | Type | Req | Description |
|---|---|---|---|
| agreementIds | array | – | Replacement related task ids. |
| allDay | boolean | – | Whether the replacement schedule is all-day. |
| endAt | string|null | – | ISO datetime for replacement end time; null clears end time. |
| kind | string | – | Replacement plan category. |
| location | – | – | Replacement location; null clears location. |
| notes | – | – | Replacement plan notes; null clears notes. |
| participantUserIds | array | – | Replacement participant user ids. |
| planItemId | string | yes | Familia plan item id to update. |
| requiresConfirmation | boolean|null | – | Whether participants should confirm coverage or attendance; null clears the setting. |
| startAt | string | – | ISO datetime. When provided, replaces the plan schedule with a one-time schedule. |
| timezone | string | – | IANA timezone for startAt/endAt, e.g. Europe/Prague. |
| title | string | – | Replacement plan title. |
| Name | Type | Req | Description |
|---|---|---|---|
| link | string | yes | – |
| planItemId | string | yes | – |
| updated | boolean | yes | – |
No examples provided.
familia_update_task Update task ~263
Use this when the user asks to rename, reschedule, reassign, complete, cancel, or otherwise edit an existing Familia task. When status is done, this completes the next actionable occurrence so recurring tasks continue. Do not use to create a new task. Updates may notify household members and reschedule reminders; delivered notifications cannot be recalled.
| Name | Type | Req | Description |
|---|---|---|---|
| agreementId | string | yes | Familia task id to update. This field is named agreementId for legacy backend compatibility. |
| assigneeUserId | string|null | – | Replacement assignee user id; null clears the assignee. |
| description | – | – | Replacement task details; null clears the description. |
| dueAt | string|null | – | ISO datetime, null to clear. |
| ownerUserId | string|null | – | Replacement owner user id; null clears the owner. |
| repeatRule | string|null | – | Replacement recurrence rule; null clears recurrence. |
| status | string | – | Replacement task status. Use done to complete the next actionable occurrence, not to close a recurring task series. |
| timezone | string | – | IANA timezone for dueAt, e.g. Europe/Prague. |
| title | string | – | Replacement task title. |
| visibleToHousehold | boolean | – | Whether the task is visible to the whole household. |
| Name | Type | Req | Description |
|---|---|---|---|
| agreementId | string | yes | – |
| link | string | yes | – |
| taskId | string | – | – |
| updated | boolean | yes | – |
No examples provided.
What is the Familia MCP server?
Familia is an MCP server listed in the public MCP registry as com.familiaplanner/familia. Private family planner for schedules, tasks, checklists, attachments, and availability. This page covers its hosted endpoint (https://mcp.family.asynq.org/mcp).
Is the Familia MCP server safe to use?
Familia scores 85 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Familia MCP server expose?
Familia exposes 25 tools: familia_list_households, familia_list_household_members, familia_get_day_overview, familia_get_today_schedule, familia_get_tomorrow_schedule, and 20 more. Their descriptions and schemas cost roughly 4,648 tokens of context every time the server is loaded.
Does the Familia MCP server require authentication?
Yes. Familia asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Familia MCP server still maintained?
Familia is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.