Name: Famboard
Author: CloudCorpRecords

Famboard MCP

Family planner for schedules, tasks, checklists, plans and attachments, shared by household.

Grade A Local · stdio No auth needed 25 tools v0.1.0 MIT

No reviews yet by CloudCorpRecordsnpm 185 Runs on your machine, nothing hosted

99/100

trust score

185

downloads a day

local

runs on your machine

tools declared

What it does

Family planner for schedules, tasks, checklists, plans and attachments, shared by household.

Quickstart

# 1 — add it to Claude Code
claude mcp add --scope user famboard-mcp '--' npx -y @reneturcios/famboard mcp

# 2 — ask your agent for something these tools do
#   familia_list_households, familia_list_household_members, familia_get_day_overview and 22 more

Famboard costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.

Publishernot claimed

CloudCorpRecords381 servers

28 categories

All 381 servers

Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.

Tool surface

What the model actually sees. Descriptions are diffed on every release — see version history.

Only tools that write or reach the network

Read from its source code. A server that builds its tool list when it starts can list more tools than this.

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.

No parameter schema on file.

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.

Parameter	Type	Required	Notes
householdId	string	yes	Familia household id whose active and pending members should be listed.
timezone	string	no	IANA timezone used by the backend request.

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.

Parameter	Type	Required	Notes
includeCompleted	boolean	no	Include completed tasks when looking through history.
date	string	no	Date as YYYY-MM-DD, ISO datetime, or omitted for today in the selected timezone.
startAt	string	no	Optional ISO datetime for a narrower time window.
endAt	string	no	Optional ISO datetime for a narrower time window. Defaults to one hour after startAt.
householdId	string	no	Optional Familia household id. Omit to aggregate across all accessible memberships.
timezone	string	no	IANA timezone, defaults to ASYNQ_TIMEZONE or the local runtime timezone.

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.

Parameter	Type	Required	Notes
householdId	string	no	Optional Familia household id. Omit to use all accessible households.
timezone	string	no	IANA timezone, e.g. Europe/Prague. Defaults to ASYNQ_TIMEZONE or runtime timezone.

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.

Parameter	Type	Required	Notes
householdId	string	no	Optional Familia household id. Omit to use all accessible households.
timezone	string	no	IANA timezone, e.g. Europe/Prague. Defaults to ASYNQ_TIMEZONE or runtime timezone.

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.

Parameter	Type	Required	Notes
householdId	string	no	Optional Familia household id. Omit to use all accessible households.
timezone	string	no	IANA timezone, e.g. Europe/Prague. Defaults to ASYNQ_TIMEZONE or runtime timezone.
scope	string	no	Use personal for “my”, “for me”, or “what should I do”; use household for family-wide next items.
limit	integer	no	Maximum number of upcoming items to return. Defaults to 5.

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.

Parameter	Type	Required	Notes
startDate	string	no	YYYY-MM-DD or ISO datetime. Defaults to today.
days	integer	no	Number of days to include, from 1 to 14. Defaults to 7.
householdId	string	no	Optional Familia household id. Omit to use all accessible households.
timezone	string	no	IANA timezone, e.g. Europe/Prague. Defaults to ASYNQ_TIMEZONE or runtime timezone.

Use this when the user asks for inbox, items needing attention, overdue tasks, past leftovers, unfinished responsibilities, or what is waiting on them.

Parameter	Type	Required	Notes
householdId	string	no	Optional Familia household id. Omit to use all accessible households.
timezone	string	no	IANA timezone, e.g. Europe/Prague. Defaults to ASYNQ_TIMEZONE or runtime timezone.
limit	integer	no	Maximum number of attention items to return. Defaults to 20.

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.

Parameter	Type	Required	Notes
householdId	string	no	Optional Familia household id. Omit to use all accessible households.
timezone	string	no	IANA timezone, e.g. Europe/Prague. Defaults to ASYNQ_TIMEZONE or runtime timezone.
limit	integer	no	Maximum number of past-due items to return. Defaults to 20.

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.

Parameter	Type	Required	Notes
offset	integer	no	Pagination offset, defaults to 0.
query	string	yes	Search text, e.g. "dentist", "school trip", or "groceries".
householdId	string	no	Optional Familia household id. Omit to search all accessible households.
limit	integer	no	Maximum number of matches to return. Defaults to 12.
timezone	string	no	IANA timezone used when formatting matched timeline items.

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,…

Parameter	Type	Required	Notes
householdId	string	yes	Familia household id where the task should be created.
title	string	yes	Short task title, e.g. "Pay school fee" or "Take bins out".
description	string	no	Optional task details, notes, or context.
dueAt	string	no	Accepts YYYY-MM-DD for all-day items or an RFC 3339 datetime. When using a datetime without an offset, provide timezone.
allDay	boolean	no	Whether the due date is an all-day task.
assigneeUserId	string	no	Optional Familia user id responsible for the task.
ownerUserId	string	no	Optional Familia user id that owns the task.
timezone	string	no	IANA timezone for dueAt, e.g. Europe/Prague.
repeatRule	string	no	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 i
recurrenceEndDate	string	no	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".
leadMinutes	integer	no	Reminder lead time in minutes before dueAt. Defaults to 0.
todoList	object	no	Optional checklist/list to attach to the created task.
idempotencyKey	string	no	Optional stable retry key. Reusing the same key for the same create operation returns the original result instead of creating a duplicate.

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…

Parameter	Type	Required	Notes
householdId	string	yes	Familia household id where the list task should be created.
title	string	yes	Task title, e.g. “Groceries” or “Pack for trip”.
listTitle	string	no	Optional title shown on the attached list. Defaults to the task title.
items	array	yes	Checklist items to attach to the new task. Supports nested subtasks.
description	string	no	Optional task details, notes, or context.
dueAt	string	no	Accepts YYYY-MM-DD for all-day items or an RFC 3339 datetime. When using a datetime without an offset, provide timezone.
allDay	boolean	no	Whether the due date is an all-day task.
assigneeUserId	string	no	Optional Familia user id responsible for the task.
ownerUserId	string	no	Optional Familia user id that owns the task.
timezone	string	no	IANA timezone for dueAt, e.g. Europe/Prague.
repeatRule	string	no	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 i
recurrenceEndDate	string	no	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".
leadMinutes	integer	no	Reminder lead time in minutes before dueAt. Defaults to 0.
idempotencyKey	string	no	Optional stable retry key. Reusing the same key for the same create operation returns the original result instead of creating a duplicate.

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.

Parameter	Type	Required	Notes
targetType	string	yes	Type of Familia item that owns the attachments.
targetId	string	yes	Task id when targetType is task, or plan item id when targetType is plan.
timezone	string	no	IANA timezone used by the backend request.

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.

Parameter	Type	Required	Notes
targetType	string	yes	Type of Familia item that should receive the image.
targetId	string	yes	Task id when targetType is task, or plan item id when targetType is plan.
dataUrl	string	no	Image data URL, e.g. data:image/png;base64,...
base64Data	string	no	Raw base64 image bytes when dataUrl is not provided.
mimeType	string	no	Required when base64Data is provided without a dataUrl.
fileName	string	no	Optional image filename shown in attachment metadata.
width	integer	no	Optional image width in pixels.
height	integer	no	Optional image height in pixels.
replaceExistingPhoto	boolean	no	When true, replaces the latest existing photo attachment for the target.
timezone	string	no	IANA timezone used by the backend request.

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.

Parameter	Type	Required	Notes
targetType	string	yes	Type of Familia item that should receive the list.
targetId	string	yes	Task id when targetType is task, or plan item id when targetType is plan.
title	string	no	Optional title shown on the attached checklist/list.
items	array	yes	Checklist/list items to attach. Supports nested subtasks.
timezone	string	no	IANA timezone used by the backend request.

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.

Parameter	Type	Required	Notes
attachmentId	string	yes	Familia attachment id for the checklist/list to replace.
title	string	no	Optional replacement list title.
items	array	yes	Full replacement checklist/list content. Supports nested subtasks.
timezone	string	no	IANA timezone used by the backend request.

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.

Parameter	Type	Required	Notes
attachmentId	string	yes	Familia attachment id to delete.
timezone	string	no	IANA timezone used by the backend request.

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…

Parameter	Type	Required	Notes
householdId	string	yes	Familia household id where the plan should be created.
title	string	yes	Short plan title, e.g. "School concert" or "Long weekend trip".
kind	string	no	Plan category. Use event when no more specific category fits.
notes	string	no	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.
location	string	no	Optional location, venue, or address.
startAt	string	no	Optional ISO datetime.
endAt	string	no	Optional ISO datetime.
allDay	boolean	no	Whether the plan is all-day.
timezone	string	no	IANA timezone for startAt/endAt, e.g. Europe/Prague.
rrule	string	no	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 i
recurrenceEndDate	string	no	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".
participantUserIds	array	no	Optional Familia user ids participating in the plan.
agreementIds	array	no	Optional existing related task ids to link to the plan.
relatedTasks	array	no	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-i
requiresConfirmation	boolean	no	Whether participants should confirm coverage or attendance.
idempotencyKey		no	—

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…

Parameter	Type	Required	Notes
agreementId	string	yes	Familia task id to update. This field is named agreementId for legacy backend compatibility.
title	string	no	Replacement task title.
description		no	Replacement task details; null clears the description.
status	string	no	Replacement task status. Use done to complete the next actionable occurrence, not to close a recurring task series.
dueAt	string/null	no	ISO datetime, null to clear.
repeatRule	string/null	no	Replacement recurrence rule; null clears recurrence.
assigneeUserId	string/null	no	Replacement assignee user id; null clears the assignee.
ownerUserId	string/null	no	Replacement owner user id; null clears the owner.
visibleToHousehold	boolean	no	Whether the task is visible to the whole household.
timezone	string	no	IANA timezone for dueAt, e.g. Europe/Prague.

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.

Parameter	Type	Required	Notes
agreementId	string	yes	Familia task id to cancel. This field is named agreementId for legacy backend compatibility.
timezone	string	no	IANA timezone used by the backend request.

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.

Parameter	Type	Required	Notes
agreementId	string	yes	Familia task id to permanently delete. This field is named agreementId for legacy backend compatibility.
timezone	string	no	IANA timezone used by the backend request.

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…

Parameter	Type	Required	Notes
planItemId	string	yes	Familia plan item id to update.
title	string	no	Replacement plan title.
kind	string	no	Replacement plan category.
notes		no	Replacement plan notes; null clears notes.
location		no	Replacement location; null clears location.
startAt	string	no	ISO datetime. When provided, replaces the plan schedule with a one-time schedule.
endAt	string/null	no	ISO datetime for replacement end time; null clears end time.
allDay	boolean	no	Whether the replacement schedule is all-day.
timezone	string	no	IANA timezone for startAt/endAt, e.g. Europe/Prague.
participantUserIds	array	no	Replacement participant user ids.
agreementIds	array	no	Replacement related task ids.
requiresConfirmation	boolean/null	no	Whether participants should confirm coverage or attendance; null clears the setting.

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…

Parameter	Type	Required	Notes
planItemId	string	yes	Familia plan item id to delete or cancel.
timezone	string	no	IANA timezone used by the backend request.

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…

Parameter	Type	Required	Notes
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.
continueOnError	boolean	no	When true, continue after a failed operation and return partial-success results. Defaults to false.
idempotencyKey		no	—
timezone	string	no	Default IANA timezone for operations that omit their own timezone.

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.

Parameter	Type	Required	Notes
consecutiveDays	integer	no	Required length of each free-day run. Defaults to 4.
startDate	string	no	YYYY-MM-DD or ISO datetime. Defaults to today.
horizonDays	integer	no	How many days to scan forward from startDate. Defaults to 120.
householdId	string	no	Optional Familia household id. Omit to use all accessible households.
timezone	string	no	IANA timezone used for day boundaries, e.g. Europe/Prague.
busyStartHour	integer	no	Start hour of the day window to consider busy. Defaults to 0.
busyEndHour	integer	no	End hour of the day window to consider busy. Defaults to 24.
blockingPolicy	string	no	availability ignores soft reminders such as chores, checklists, birthdays/name days and ordinary tasks; strict treats any timeline item as busy.
limit	integer	no	Maximum number of free-day runs to return. Defaults to 8.

Free

$0 forever

Every tool, no call limit
No card, and mcprush charges nothing for it
Source published under MIT
Runs on your machine — nothing of it reaches our gateway
Nothing to cap, because mcprush bills nothing

Nothing here is billable: mcprush charges nothing to install Famboard or to call it, at any volume.

ATrust score 99 / 100

Release 0.1.0 · scanned 5 Nov 2026

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.

Threat score100

Client score99

Findings0 threat · 0 capability

Capabilityminimal

Coveragesource

Verificationrepo

Surface digestd8401c1b83f28185699ebc8682ab7439392b56537a69a62f6ee18e9efbd89169

Score vectorthreat 100 → client 99

Term	Level	What it prices	Points
capability-exposure	minimal	capability blast radius (minimal) — client exposure if the model is manipulated	−0
verification-discount	repo	publisher verification (public source) — no provenance, but the source is public and inspectable	−1
coverage-honesty	source	inspection depth (source) — how much of the target the scan could see	−0

score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.

What the scan could actually read

A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.

Tool surfacenot available

Implementation sourceread

Package metadataread

Live transportnot available

No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".

Capability — what it could do if the model were manipulated

Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.

Tool	Capability tags	Why the tag was assigned
No per-tool rows for this release — see the note below.

No tool surface was enumerated, so there is nothing to attribute a capability to.

Toxic-flow graph

The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.

The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.

Supply chain and provenance

Integrityfirst-seen

Surface digestd8401c1b83f28185

Scanned2026-11-05

This is the first scan of this surface here, so there is nothing yet to compare it against.

Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.

Where are you running it?

Tool surface

Release history

Famboard MCP

What it does

Quickstart

Where are you running it?

Tool surface

What counts against your monthly calls

What the scan could actually read

Capability — what it could do if the model were manipulated

Toxic-flow graph

Supply chain and provenance

Release history

See also