Interact with Microsoft 365 and Office services through the Microsoft Graph API.
Familyorg is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Cozi family members, lists and shared calendar, as MCP tools.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user familyorg-mcp '--' npx -y @reneturcios/familyorg mcp
# 2 — ask your agent for something these tools do
# family_members, get_lists, get_list_items and 12 more
Familyorg costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Familyorg as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user familyorg-mcp '--' npx -y @reneturcios/familyorg mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
15 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
List the members of the Cozi family account.
No parameter schema on file.
List the family's lists, optionally filtered by list type.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| list_type | string | no | Optional list type to filter by: "shopping" or "todo". All lists are returned when omitted. |
Get the items on one list, optionally including completed items.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| list_id | string | yes | ID of the list to get items from, as returned by get_lists. |
| include_completed | boolean | no | When true, include completed items in the result. |
Create a new shopping or to-do list.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Name of the new list. |
| list_type | string | yes | Type of the new list: "shopping" or "todo". |
Rename an existing list.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| list_id | string | yes | ID of the list to rename, as returned by get_lists. |
| title | string | yes | New title for the list. |
Delete a list from the family account, removing the list identified by list_id.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| list_id | string | yes | ID of the list to delete, as returned by get_lists. |
Add an item to a list, optionally at a position.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| list_id | string | yes | ID of the list to add the item to, as returned by get_lists. |
| text | string | yes | Text of the item to add. |
| position | integer | no | Optional position in the list at which to insert the item. |
Update an item's text or completed state on a list.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| list_id | string | yes | ID of the list containing the item, as returned by get_lists. |
| item_id | string | yes | ID of the item to update, as returned by get_list_items. |
| text | string | no | Optional new text for the item. |
| completed | boolean | no | Optional new completed state for the item. |
Remove one or more items from a list.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| list_id | string | yes | ID of the list to remove items from, as returned by get_lists. |
| item_ids | array | yes | IDs of the items to remove, as returned by get_list_items. |
Return today's date from the local clock. Needs no Cozi credentials.
No parameter schema on file.
Get the family calendar appointments for one month.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| year | integer | yes | Four-digit year of the month to retrieve. |
| month | integer | yes | Month to retrieve, as a number from 1 to 12. |
Search the family calendar for appointments matching a query.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Search text to match against calendar appointments. |
Create an appointment on the family calendar.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| subject | string | yes | Subject (title) of the appointment. |
| start | string | yes | Start time of the appointment, as a date/time string. |
| end | string | yes | End time of the appointment, as a date/time string. |
| attendees | array | no | Optional attendees for the appointment, as a list of names or identifiers. |
| all_day | boolean | no | When true, the appointment is an all-day appointment. |
| notes | string | no | Optional notes for the appointment. |
| location | string | no | Optional location of the appointment. |
| repeat | object | no | Optional recurrence rule for the appointment, as an object. |
| reminders | array | no | Optional reminders for the appointment, as a list. |
| notify | boolean | no | When true, notify attendees about the appointment. |
Update fields of an existing appointment in a given month.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| appointment_id | string | yes | ID of the appointment to update. |
| year | integer | yes | Year of the month containing the appointment. |
| month | integer | yes | Month containing the appointment, as a number from 1 to 12. |
| subject | string | no | Optional new subject (title) for the appointment. |
| start | string | no | Optional new start time, as a date/time string. |
| end | string | no | Optional new end time, as a date/time string. |
| attendees | array | no | Optional new attendees, as a list of names or identifiers. |
| all_day | boolean | no | Optional new all-day state for the appointment. |
| notes | string | no | Optional new notes for the appointment. |
| location | string | no | Optional new location for the appointment. |
| repeat | object | no | Optional new recurrence rule, as an object. |
| reminders | array | no | Optional new reminders, as a list. |
| notify | boolean | no | When true, notify attendees about the update. |
| scope | string | no | Optional scope of the update for a repeating appointment, such as a single occurrence or the series. |
| occurrence_day | string | no | Optional day of the occurrence to update, for a repeating appointment. |
Delete an appointment from a given month.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| appointment_id | string | yes | ID of the appointment to delete. |
| year | integer | yes | Year of the month containing the appointment. |
| month | integer | yes | Month containing the appointment, as a number from 1 to 12. |
| scope | string | no | Optional scope of the deletion for a repeating appointment, such as a single occurrence or the series. |
| occurrence_day | string | no | Optional day of the occurrence to delete, for a repeating appointment. |
| notify | boolean | no | When true, notify attendees about the deletion. |
- 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
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Familyorg or to call it, at any volume.
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.
| 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 |
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.
Tools were statically extracted from the published source (15 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, 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 |
|---|---|---|
| family_members | no tags | |
| get_lists | no tags | |
| get_list_items | no tags | |
| create_list | no tags | |
| rename_list | no tags | |
| delete_list | no tags | |
| add_item | no tags | |
| update_item | no tags | |
| remove_items | no tags | |
| today | no tags | |
| get_calendar | no tags | |
| search_calendar | no tags | |
| create_appointment | no tags | |
| update_appointment | no tags | |
| delete_appointment | no tags |
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
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.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.1.0. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Familyorg can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.