All servers / Productivity / haus
haus
OneHaus household tools: tasks, calendar, contacts, pets, vehicles, documents and more.
Tested by ConnectATD Hosted serverTested 2026-11-22. Address: https://mcp.onehaus.app · Registry name: app.onehaus/haus
Score 85 out of 100. Tested 2026-11-22.
Score breakdown
| Connects and stays up | 20 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Inputs explained | 15 / 15 | |
| Speed | 0 / 15 | |
| Safety basics | 15 / 15 | |
| Upkeep | 15 / 15 |
What we saw
- Connects and answers the MCP handshake: yes (1.0 seconds)
- Uses an encrypted (https) connection: yes
- Server reports itself as: OneHaus 1.8.0
- Tools offered: 77 · Parameters with a plain description: 292 of 292
- One safe, read-only test call to
list_contacts: failed (first call 0.2 seconds) - Official registry entry last updated: 2026-11-19
From the publisher
- No notes.
How hosted servers are graded
Hosted servers run on the publisher's own machines, so we cannot score downloads or install safety. We use six checks instead (connects and stays up 20, tool descriptions 20, inputs explained 15, speed 15, safety basics 15, upkeep 15). Speed is the first call to a safe, read-only tool (when a server marks none, the time to connect and list its tools), using a fresh request where we can so a saved answer cannot hide a slow one. We never call tools that write data or cost money. A server that needs a login or key is not graded. Full method.
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions.
create_contact9 of 9 parameters describedAdd a contact to the address book. Only firstName is required; address, date of birth, notes and the birthday-present flag can follow via update_contact.
update_contact10 of 10 parameters describedUpdate a contact by id. Only the fields supplied are changed; omitted fields keep their current value (dateOfBirth is the exception: an empty string explicitly clears it).
delete_contact1 of 1 parameter describedSoft-delete a contact by id; it is marked deleted and no longer appears in list_contacts, but the underlying record is retained rather than permanently erased.
list_contactsno parametersList all contacts in the household. Takes no parameters; soft-deleted contacts are excluded.
create_appliance9 of 9 parameters describedCreate an appliance record for the household, tracking purchase date, warranty expiry, and optional references to previously created warranty/insurance documents.
update_appliance10 of 10 parameters describedUpdate an appliance's details; omitted fields keep their current value. Rejects the update if the resulting warranty expiry date would fall before the purchase date.
delete_appliance1 of 1 parameter describedSoft-delete an appliance; it is hidden from list_appliances but not permanently erased.
list_appliancesno parametersList the household's appliances with brand, model, serial number, purchase date and warranty expiry. Answers whether something is still under warranty.
create_calendar_event11 of 11 parameters describedCreates a single, one-off calendar event on the household calendar. Timed events need startDateTime; all-day events need startDate (plus endDate for several days). Set reminders with reminderOffsetMinutes. For a repeating schedule use create_recurring_calendar_event instead.
update_calendar_event12 of 12 parameters describedUpdates fields on an existing single calendar event; only the fields supplied are changed, all others keep their current value. Imported (subscription-sourced) events cannot be edited.
delete_calendar_event1 of 1 parameter describedSoft-deletes a single calendar event by id. Events imported from a calendar subscription cannot be deleted here; unsubscribe from the source calendar instead. Events shared from a member's device calendar can only be removed by that member or the house owner.
list_calendar_events2 of 2 parameters describedList one-off calendar events with their title, times, location and notes. Bound them with startDateFrom and startDateTo, or omit both for everything. An all-day event's end depends on its sourceEntityType. With no source, endDateTime is its LAST day (inclusive), or null for a single day. For 'deviceCalendar' and 'calendarSubscription' it is the day AFTER the last day (exclusive). For 'RecurringCalendarEvent' the event covers endDateTime minus startDateTime in whole days, rounded up (a single day when null). Read a 00:00Z value as its UTC date; read any other all-day value in the event's timezone when it has one.
create_document9 of 9 parameters describedStore a document (passport, insurance, certificate, warranty, license, other) with its reference number, issuing authority, fee and notes. Optionally file it against a pet, vehicle or appliance with linkedEntityType and linkedEntityId. Returns the new id, which an appliance, vehicle or pet can link to.
update_document10 of 10 parameters describedUpdate a stored document's type, title, reference number, issuing authority, fee, notes or linked pet, vehicle or appliance, returning the updated document. Only the fields you send change. renewalCronExpression is the one exception: it is accepted but not yet stored or acted on, so sending it changes nothing.
delete_document1 of 1 parameter describedSoft-delete a document by id and cascade soft-delete its attachments; none of them appear in listings afterward, but the records are retained rather than permanently erased.
list_documents1 of 1 parameter describedList documents in the household, optionally filtered to a single document type. Soft-deleted documents are excluded.
create_pet6 of 6 parameters describedAdd a pet, optionally with its microchip number and date of birth, and links to an existing contact as vet and document as insurance. Returns the new pet's id.
update_pet7 of 7 parameters describedUpdate a pet's name, microchip number, date of birth, notes, or its linked vet contact and insurance document. Only the fields you send change.
delete_pet1 of 1 parameter describedSoft-delete a pet; it is hidden from list_pets but not permanently erased.
list_petsno parametersList the household's pets with microchip number, date of birth, notes and their linked vet contact and insurance document.
create_subscription8 of 8 parameters describedTrack a bill such as a streaming service or membership, with an optional fee and cron renewal schedule (no more often than daily). A bill with no renewal schedule is a one-off. Set paymentDate only when the money leaves the account on a different day from the renewal.
update_subscription9 of 9 parameters describedUpdate a subscription. Only the fields you send change; for renewalCronExpression, startDate, paymentDate and notes an empty string clears the stored value.
delete_subscription1 of 1 parameter describedSoft-delete a subscription so it leaves list_subscriptions; the record is retained. Use it when the user cancels a service.
list_subscriptions1 of 1 parameter describedList tracked subscriptions with their fee, renewal schedule, payment date and status. A subscription with no renewal schedule is a one-off. startDate is the renewal date: the first renewal of a recurring bill, or when a one-off is due; paymentDate, when set, is the first day money leaves the account and repeats on the renewal cadence. Pass status to filter to one.
create_vehicle11 of 11 parameters describedCreate a vehicle record for the household to track its details, registration and VIN, insurance document, and upcoming MOT/tax/service due dates. All fields are optional.
update_vehicle12 of 12 parameters describedUpdate a vehicle. Only the fields you send change; for text and due-date fields an empty string clears the stored value.
delete_vehicle1 of 1 parameter describedSoft-delete a vehicle so it leaves list_vehicles; the record is retained. Use it when the household sells a car.
list_vehiclesno parametersList the household's vehicles with make, model, year, registration, VIN and MOT, tax and service due dates. Answers questions like when the MOT is due.
create_task7 of 7 parameters describedCreates a new household task. Only title is required; the task starts unassigned and uncompleted. Set reminders with reminderOffsetMinutes. Use assign_task, update_task, or complete_task to change it afterward.
update_task8 of 8 parameters describedUpdate a task's title, assignee, due date, reminders, notes or urgency. Only the fields you send change.
delete_task1 of 1 parameter describedSoft-delete a task. It leaves list_tasks but the record is retained. Fails if it was already deleted.
complete_task1 of 1 parameter describedMarks a task as completed. Fails with a conflict if the task is already completed.
uncomplete_task1 of 1 parameter describedReopens a completed task, clearing its completion timestamp and completed-by user. Fails with a conflict if the task is not currently completed.
assign_task2 of 2 parameters describedAssign or unassign a task to a household member.
list_tasks6 of 6 parameters describedList tasks, filterable by assignee, due-date range and completion, with cursor pagination. Excludes completed tasks by default and sorts open urgent tasks first (within the returned page), then due date ascending (undated first).
get_weather_forecast1 of 1 parameter describedReturn a one-to-five day forecast for the household's location, for planning outdoor tasks or events.
get_houseno parametersReturn the current household in full: name, address, invite code, notes, join settings, members, subscription status and resolved feature flags.
list_house_membersno parametersList the household's members with id, userId, first and last name, nickname and role. Use a member's id as assignedToMemberId in create_task and assign_task.
list_housesno parametersList the households the current user belongs to (e.g. to tell the user which home you are acting on). The active house is determined server-side from the authenticated session.
get_profileno parametersReturn the signed-in user's profile: name, email, AI-consent status and timezone. Also bumps their last-seen activity as a side effect.
list_shopping_listsno parametersList the household's named shopping lists with their id, name, whether they are the default list, and how many live items each holds. Use this to resolve a shoppingListId for the shopping list item tools.
list_shopping_list_items1 of 1 parameter describedList outstanding (unbought) shopping list items with their name, quantity, category and shoppingListId. Pass shoppingListId to limit it to one named list.
add_shopping_list_item4 of 4 parameters describedAdd one item to the shopping list. A new item gets a category from its name; if an unbought item of the same name exists, its quantity is increased instead of duplicating it.
buy_shopping_list_item2 of 2 parameters describedMark units of a shopping list item as bought, reducing its quantity by quantityToBuy and clearing it off the list once nothing is left.
get_house_reviewno parametersReturn this week's pending House Review recommendations: data gaps like a missing appliance warranty or vehicle MOT date. Re-validated live, so items already filled in, actioned or covered by an open task are dropped. Pro-gated.
defer_recommendation1 of 1 parameter describedDefer a House Review recommendation and raise a task due in seven days, for when the user wants to handle the gap later.
skip_recommendation1 of 1 parameter describedPermanently suppress a House Review recommendation so get_house_review stops returning it. Use it when the suggestion does not apply.
store_memory4 of 4 parameters describedStore a long-term memory about the household. Use sparingly for durable preferences, routines, constraints, or insights worth recalling in a future conversation. Recall first to avoid duplicates.
update_memory4 of 4 parameters describedUpdate an existing memory's name, description, or content. Type is immutable; to reclassify, forget and store again.
forget_memory1 of 1 parameter describedForget (soft-delete) a memory by id. Use when a memory is superseded or no longer relevant.
recall_memory3 of 3 parameters describedRecall long-term memories stored about the current household. Call this at the start of advisory or open-ended turns. Filter by type when only one author's notes are relevant.
create_calendar_subscription2 of 2 parameters describedSubscribe the household to an external calendar feed (an .ics link, e.g. a school, club or bin collection calendar) so its events appear in the household calendar and stay in sync. Only subscribe to a feed link the user typed themselves in this conversation. Only the house owner can do this; a house can have up to 5 feeds. The feed is checked before it is saved; its events appear after the feed's next refresh, which can take a few hours.
create_meal_plan7 of 7 parameters describedPlan a meal for a specific date and meal type. Provide recipeId to link an existing recipe (from list_recipes) OR name for a custom meal; when recipeId is given any name is ignored and stored as null.
update_meal_plan8 of 8 parameters describedUpdate a planned meal. Only the fields you send change. recipeId links a recipe and clears any custom name; name makes it custom and clears the link; recipeId wins if both are sent.
delete_meal_plan1 of 1 parameter describedSoft-delete a planned meal. The entry leaves list_meal_plans and frees its date and meal slot again.
list_meal_plans2 of 2 parameters describedList planned meals with their date, meal slot, linked recipe or custom name, servings and notes. Narrow with from and to.
create_recipe5 of 5 parameters describedSave a recipe with optional ingredients, source URL, instructions and servings. Link it to a date with create_meal_plan.
update_recipe6 of 6 parameters describedUpdate a recipe. Only the fields you send change, except ingredients, which replaces the whole existing list rather than merging.
delete_recipe1 of 1 parameter describedSoft-delete a recipe. Meal plan entries linked to it become custom entries holding a snapshot of its name, ingredients and instructions, so none are left with a dangling link.
list_recipesno parametersList the household's own saved recipes with ingredients, instructions, source URL and servings. For the shared catalogue use list_global_recipes.
list_global_recipesno parametersList the curated Discover recipe catalogue shared by all households. Pass an id from here to create_meal_plan with recipeSource='global'.
batch_add_shopping_list_items2 of 2 parameters describedAdd up to 25 shopping list items at once, for a whole shop. Names are deduplicated within the batch and merged into any matching unbought item already listed.
update_shopping_list_item5 of 5 parameters describedUpdate a shopping list item's name, quantity, and/or category. Only the fields provided are changed; any field left out keeps its current value.
remove_shopping_list_item1 of 1 parameter describedRemove an item from the household's shopping list without marking it as bought. This soft-deletes the item so it no longer appears in list_shopping_list_items.
create_shopping_list1 of 1 parameter describedCreate a new named shopping list for the household (e.g. 'DIY' or 'Party') alongside the default list. A house can have up to 20 lists. Returns the list id to pass as shoppingListId when adding items.
update_shopping_list2 of 2 parameters describedRename one of the household's shopping lists, including the default list. The items on it are unchanged.
delete_shopping_list1 of 1 parameter describedDelete one of the household's named shopping lists. Its items move to the default list rather than being deleted. The default list itself cannot be deleted.
create_recurring_calendar_event13 of 13 parameters describedCreate a recurring calendar event. It generates event instances on a schedule, each with the reminders set in reminderOffsetMinutes.
update_recurring_calendar_event14 of 14 parameters describedUpdate a recurring calendar event. Changes to title/description/notes/reminders patch existing instances. Changes to frequency/dates/time regenerate future instances.
delete_recurring_calendar_event1 of 1 parameter describedDelete a recurring calendar event and all its future instances.
list_recurring_calendar_eventsno parametersList the household's repeating calendar events (the series, not their generated instances) with their id, title, interval ('N Unit'), local start time, duration, dates, timezone and reminders. Use it to find the id for update_recurring_calendar_event or delete_recurring_calendar_event.
create_recurring_task10 of 10 parameters describedCreate a recurring task. It generates task instances on a schedule, each with the reminders set in reminderOffsetMinutes.
update_recurring_task11 of 11 parameters describedUpdate a recurring task. Title, notes, urgency or reminder changes patch existing instances; frequency/date changes regenerate future instances.
delete_recurring_task1 of 1 parameter describedDelete a recurring task and all its uncompleted future instances.
list_recurring_tasksno parametersList the household's repeating tasks (the series, not their generated instances) with their id, title, interval ('N Unit'), dates, rotation and reminders. Use it to find the id for update_recurring_task or delete_recurring_task, e.g. to stop or change a weekly chore.
list_task_packsno parametersList the ready-made task packs the household can add (e.g. moving house, a new baby, car maintenance): each pack's id, title, description and items (id, kind, title, whether it is selected by default, days before the anchor date, repeat interval). Packs for a vehicle, appliance or pet list the owned items they can be linked to (entities) with a suggested anchor date. Use it before apply_task_pack.
apply_task_pack6 of 6 parameters describedAdd a task pack from list_task_packs to the household: creates its tasks, repeating tasks and events, dated from the anchor date. The pack's titles are English: when the user is not writing in English, pass their titles (and notes) translated in overrides. Returns how many of each were created.
Tested by ConnectATD. Spotted a mistake? Tell us.