app.onehaus/haus
REMOTE · MCP.ONEHAUS.APP · SCANNED AUG 3
OneHaus household tools: tasks, calendar, contacts, pets, vehicles, documents and more.
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 →
Endpoint Security97
- 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
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability89
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 9261 tokens (~134/item across 69 items; 68 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Tools include usage examples.Pass
Stability & Change Management27
- Stability observed for 8 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
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities73
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
- Supports UI / widget rendering.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.onehaus.app
claude mcp add --transport http app-onehaus-haus https://mcp.onehaus.app/
[mcp_servers.app-onehaus-haus] url = "https://mcp.onehaus.app/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"app-onehaus-haus": {
"type": "remote",
"url": "https://mcp.onehaus.app/",
"enabled": true
}
}
} openclaw mcp add app-onehaus-haus --url https://mcp.onehaus.app/ --transport streamable-http
mcp_servers:
app-onehaus-haus:
url: "https://mcp.onehaus.app/" {
"mcpServers": {
"app-onehaus-haus": {
"type": "http",
"url": "https://mcp.onehaus.app/"
}
}
} 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.
- 2 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +6
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 77
First indexed and scored.
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 3 Aug 2026 · Probed https://mcp.onehaus.app
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.onehaus.app | CN=Amazon RSA 2048 M01,O=Amazon,C=US | 11 Jun 2026 | 25 Dec 2026 | RSA 2048 | SHA256-RSA | d8eef4f6d543a7f3570fcf1cf084dd8 |
| SANs: mcp.onehaus.app | ||||||
| CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 77312380b9d6688a33b1ed9bf9ccda68e0e0f |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
DNSSEC secure
Validation of mcp.onehaus.app. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| onehaus.app. | present | 10683 | 13 | Verified |
| mcp.onehaus.app. | 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.onehaus.app/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://mcp.onehaus.app/.well-known/oauth-protected-resource" | Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
Protected resource metadata
| Document | https://mcp.onehaus.app/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.onehaus.app |
| Authorisation server | https://mcp.onehaus.app |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.onehaus.app | Verified | 200 | |
| http (plaintext) | http://mcp.onehaus.app | HTTPS enforced |
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.
add_shopping_list_item ~206
Add an item to the household's shopping list. A brand-new item gets a category auto-assigned from its name. If an unbought item with a matching name already exists, its quantity is merged into that item instead of creating a duplicate, keeping the existing item's category unchanged.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The name of the item to add, e.g. 'Milk' or 'Paper towels'. Maximum 200 characters. For a brand-new item, a category is auto-assigned from the name. If an unbought item with a matching name is alread… |
| quantity | integer | — | How many of the item to add. Defaults to 1 if omitted. Minimum 1, maximum 9999. When merged into an existing unbought item, this is added to the existing quantity (capped at 9999). |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | — |
| message | string | — | — |
| title | string | — | — |
| variant | string | — | — |
{"name":"Milk","quantity":2} assign_task ~72
Assign or unassign a task to a household member.
| Name | Type | Req | Description |
|---|---|---|---|
| assignedToMemberId | string | — | The member ID of the household member. Get this from list_house_members. Pass null or empty string to unassign. |
| id | string | yes | The task's ID, as returned by create_task or list_tasks. |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | — |
| message | string | — | — |
| title | string | — | — |
| variant | string | — | — |
{"id":"018f2c9a1b2c7d3e9a4f5b6c7d8e9f0a","assignedToMemberId":"7f3a9c2e1b4d8f6a0c5e3b7d9a1f4c6e"} batch_add_shopping_list_items ~50
Add multiple items to the shopping list at once
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | List of items to add to the shopping list in a single call. Up to 25 items per call. |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | — |
| message | string | — | — |
| title | string | — | — |
| variant | string | — | — |
{"items":[{"name":"Milk","quantity":2},{"name":"Eggs","quantity":1}]} buy_shopping_list_item ~123
Buy item (decrements quantity; removes at zero)
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The ID of the shopping list item to buy, as returned by add_shopping_list_item, batch_add_shopping_list_items, or list_shopping_list_items. |
| quantityToBuy | integer | — | How many units to mark as bought. Defaults to 1. Minimum: 1, maximum 9999. If this meets or exceeds the item's remaining quantity, the item is fully bought and removed from the active list; otherwise… |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | — |
| message | string | — | — |
| title | string | — | — |
| variant | string | — | — |
{"id":"0189c8d4f2b1712a9e4d6c9a1b2e3f4a","quantityToBuy":1} complete_task ~56
Marks a task as completed and records the completion for the household's momentum stats. Fails with a conflict if the task is already completed.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The task's ID, as returned by create_task or list_tasks. |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | — |
| message | string | — | — |
| title | string | — | — |
| variant | string | — | — |
{"id":"018f2c9a1b2c7d3e9a4f5b6c7d8e9f0a"} create_appliance ~206
Create an appliance record for the household, tracking purchase date, warranty expiry, and optional references to previously created warranty/insurance documents.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | — | Manufacturer or brand name. |
| insuranceDocumentId | string | — | ID of a previously created document containing the insurance policy. |
| model | string | — | Model name or number, as printed on the appliance or its manual. |
| name | string | yes | Name of the appliance, e.g. what it is or where it's located. |
| notes | string | — | Freeform notes about the appliance. |
| purchaseDate | string | — | Date the appliance was purchased, in YYYY-MM-DD format. |
| serialNumber | string | — | Manufacturer serial number, used when contacting support or filing a warranty claim. |
| warrantyDocumentId | string | — | ID of a previously created document containing the warranty paperwork. |
| warrantyExpiryDate | string | — | Date the manufacturer warranty expires, in YYYY-MM-DD format. Must not be before purchaseDate. |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | — |
| message | string | — | — |
| title | string | — | — |
| variant | string | — | — |
{"name":"Kitchen Refrigerator","brand":"Samsung","model":"RF28R7351SG","serialNumber":"S/N-4471829","purchaseDate":"2023-11-04","warrantyExpiryDate":"2025-11-04"} create_calendar_event ~268
Creates a single, one-off calendar event on the household calendar. For a repeating schedule use create_recurring_calendar_event instead.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | — | Longer free-text description of the event. Up to 2000 characters. |
| endDateTime | string | — | ISO 8601 date-time in UTC (Z-suffix). Must not be before startDateTime. |
| isAllDay | boolean | yes | True for an all-day event with no specific start/end time; false for a timed event. |
| location | object | — | Location. Set $type to 'Address' for physical (with line1-3, postalCode, countryCode) or 'OnlineLocation' for virtual (with url, notes). |
| notes | string | — | Freeform notes attached to the event. Up to 5000 characters. |
| startDateTime | string | yes | ISO 8601 date-time in UTC (Z-suffix). The wall clock is interpreted against the supplied timezone if any. |
| timezone | string|null | — | IANA timezone id (e.g. 'Europe/London') describing the wall-clock zone of startDateTime/endDateTime; null = UTC. |
| title | string | yes | Event title/summary shown in calendar views. Required, up to 200 characters. |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | — |
| message | string | — | — |
| title | string | — | — |
| variant | string | — | — |
{"title":"Dentist appointment","description":"Annual checkup with Dr. Smith","location":{"$type":"Address","line1":"221B Baker Street","postalCode":"NW1 6XE","countryCode":"GB"},"startDateTime":"2026-08-03T14:30:00Z","endDateTime":"2026-08-03T15:30:00Z","isAllDay":false,"notes":"Bring insurance card","timezone":"Europe/London"} create_contact ~207
Create a contact in the household's address book. Only firstName is required; all other details (address, date of birth, notes, a flag to prepare a birthday present) are optional and can be filled in later with update_contact.
| Name | Type | Req | Description |
|---|---|---|---|
| address | object | — | The contact's postal address. |
| dateOfBirth | string | — | YYYY-MM-DD format |
| displayName | string | — | An alternate name to show for the contact instead of first/last, e.g. a nickname, company name, or role. |
| string | — | The contact's email address. | |
| firstName | string | yes | The contact's first name. The only required field. |
| lastName | string | — | The contact's last (family) name. |
| notes | string | — | Free-text notes about the contact. |
| phone | string | — | The contact's phone number, in any format. |
| prepareBirthdayPresent | boolean | — | Whether to prepare a birthday present for this contact |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | — |
| message | string | — | — |
| title | string | — | — |
| variant | string | — | — |
{"firstName":"Sarah","lastName":"Jones","email":"[email protected]","phone":"\u002B44 7911 123456","address":{"line1":"12 Baker Street","postalCode":"NW1 6XE","countryCode":"GB"},"dateOfBirth":"1990-05-15","notes":"Met at the neighbourhood BBQ.","prepareBirthdayPresent":true} create_document ~186
Create a document (passport, insurance, certificate, warranty, license, other)
| Name | Type | Req | Description |
|---|---|---|---|
| documentNumber | string | — | The document's reference or serial number, e.g. a passport number or insurance policy number. |
| documentType | string | yes | The kind of document being stored. |
| fee | object | — | The cost associated with the document, e.g. a renewal or issuance fee. |
| issuingAuthority | string | — | The organization or authority that issued the document. |
| notes | string | — | Free-text notes about the document. |
| renewalCronExpression | string | — | Reserved for a future renewal-reminder schedule. Currently accepted but not persisted or acted on by document creation — has no effect yet. |
| title | string | — | A custom title for the document. If omitted, one is derived from the document type and number, e.g. 'Passport - 512345678'. |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | — |
| message | string | — | — |
| title | string | — | — |
| variant | string | — | — |
{"documentType":"Passport","title":"UK Passport","documentNumber":"512345678","issuingAuthority":"HM Passport Office","fee":{"value":8250,"currencyCode":"GBP"},"notes":"Renew before the next family trip."} create_meal_plan ~208
Plan 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.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Date of the planned meal (format: YYYY-MM-DD). Must be from today up to four weeks ahead. |
| mealType | string | yes | Which meal slot of the day this entry occupies |
| name | string | — | Custom meal name when no recipe is linked |
| notes | string | — | Optional free-text notes about the planned meal |
| recipeId | string | — | ID of an existing recipe (from list_recipes or list_global_recipes) |
| recipeSource | string | — | Set 'global' when recipeId refers to a Discover/global recipe (from list_global_recipes); defaults to 'household' |
| servings | integer | — | Number of servings for the planned meal. Between 1 and 100 |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | — |
| message | string | — | — |
| title | string | — | — |
| variant | string | — | — |
{"date":"2026-07-16","mealType":"dinner","recipeId":"8f14e45f-ceea-467e-8a2f-1a2b3c4d5e6f","servings":4} create_pet ~142
Create a pet. Supports microchip, vet contact, and insurance refs.
| Name | Type | Req | Description |
|---|---|---|---|
| dateOfBirth | string | — | The pet's date of birth, in YYYY-MM-DD format. |
| insuranceDocumentId | string | — | ID of a previously created document containing the pet's insurance policy. |
| microchipNumber | string | — | Microchip identification number, used to reunite a lost pet with its household. |
| name | string | yes | The pet's name. |
| notes | string | — | Freeform notes about the pet, e.g. dietary needs or medical history. |
| vetContactId | string | — | ID of a previously created contact for the pet's vet. |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | — |
| message | string | — | — |
| title | string | — | — |
| variant | string | — | — |
{"name":"Bella","microchipNumber":"985141000123456","dateOfBirth":"2021-06-15","notes":"Allergic to chicken; on prescription food."} create_recipe ~135
Create a new recipe in the household's recipe collection, with optional ingredients, source URL, instructions and serving size. Link it to a date with create_meal_plan, or browse it later with list_recipes.
| Name | Type | Req | Description |
|---|---|---|---|
| ingredients | array | — | Optional list of ingredients required for the recipe |
| instructions | string | — | Optional free-text cooking instructions/method |
| name | string | yes | Recipe name/title |
| servings | integer | — | Number of servings the recipe yields. Minimum: 1 |
| url | string | — | Optional source URL the recipe was found at (e.g. a link to a blog or recipe site) |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | — |
| message | string | — | — |
| title | string | — | — |
| variant | string | — | — |
{"name":"Chicken Tikka Masala","url":"https://example.com/recipes/chicken-tikka-masala","instructions":"Marinate the chicken, then simmer in the spiced tomato sauce for 20 minutes.","servings":4,"ingredients":[{"name":"chicken breast","quantity":2},{"name":"tomato","quantity":4}]} create_recurring_calendar_event ~456
Create a recurring calendar event that automatically generates event instances on a schedule.
| Name | Type | Req | Description |
|---|---|---|---|
| cronExpression | string | yes | Recurrence interval, NOT a cron expression despite the field name. Format is 'N Unit' where N is a positive integer and Unit is one of Day, Week, Month, Year (case-sensitive), e.g. '1 Day', '2 Week',… |
| description | string | — | Longer free-text description applied to every generated instance. Up to 2000 characters. |
| duration | string | — | Length of each instance, in ISO 8601 duration format. |
| endDate | string | — | Last date on which instances may occur, YYYY-MM-DD format. Omit for no end date (bounded only by maxOccurrences, if set). |
| isAllDay | boolean | — | True if generated instances are all-day events with no specific start/end time; false for timed instances. |
| location | object | — | Location applied to every generated instance. Set $type to 'Address' for physical (with line1-3, postalCode, countryCode) or 'OnlineLocation' for virtual (with url, notes). |
| maxOccurrences | integer | — | Maximum number of instances to generate before recurrence stops. Omit for unlimited (bounded only by endDate, if set). |
| notes | string | — | Freeform notes applied to every generated instance. Up to 5000 characters. |
| startDate | string | — | Anchor date the recurrence is calculated from, YYYY-MM-DD format. The first instance falls on this date (subject to startTime/timezone); later instances are startDate plus multiples of the cronExpres… |
| startTime | string | — | Time of day each instance starts, in HH:mm:ss format (local to timezone). Omit for an event with no fixed time. |
| timezone | string|null | — | IANA timezone id (e.g. 'Europe/London') that startTime is in. Each generated occurrence's UTC instant respects this zone's DST. |
| title | string | yes | Event title/summary applied to every generated instance. Required, up to 200 characters. |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | — |
| message | string | — | — |
| title | string | — | — |
| variant | string | — | — |
{"title":"Weekly team standup","description":"Sync on sprint progress","startTime":"09:00:00","duration":"PT30M","isAllDay":false,"notes":"Bring your laptop","cronExpression":"1 Week","startDate":"2026-08-03","endDate":"2026-12-31","maxOccurrences":20,"timezone":"Europe/London"} create_recurring_task ~294
Create a recurring task that automatically generates task instances on a schedule.
| Name | Type | Req | Description |
|---|---|---|---|
| assigneeRotation | array | — | Ordered list of household member IDs to round-robin through, one per generated instance. Entries that are no longer valid house members are skipped and that instance is left unassigned. |
| cronExpression | string | yes | Recurrence frequency expression in the format 'N Unit', e.g. '2 Week' for every two weeks. Unit must be exactly Day, Week, Month, or Year (case-sensitive). Despite the parameter name, this is not cro… |
| endDate | string | — | The last date instances are generated through (inclusive), in YYYY-MM-DD format. Omit for an open-ended schedule. |
| maxOccurrences | integer | — | Maximum number of task instances to generate in total. Generation stops once this many instances have been created, even if endDate has not been reached. |
| notes | string | — | Freeform notes copied to every generated task instance. |
| preparationDays | integer | — | Number of days before each occurrence's due date to set that instance's preparation date. Clamped to today if the computed date would be in the past. |
| startDate | string | — | The date the schedule starts generating instances from, in YYYY-MM-DD format. Defaults to today if omitted. |
| title | string | yes | The recurring task's title. Used as the title for every generated task instance. |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | — |
| message | string | — | — |
| title | string | — | — |
| variant | string | — | — |
{"title":"Take out the recycling","notes":"Blue bin only","preparationDays":1,"cronExpression":"2 Week","startDate":"2026-08-01","endDate":"2026-12-31","maxOccurrences":26,"assigneeRotation":["7f3a9c2e1b4d8f6a0c5e3b7d9a1f4c6e","a1b2c3d4e5f60718293a4b5c6d7e8f90"]} create_subscription ~160
Create a subscription for the household to track a recurring cost, such as a streaming service or membership. Accepts an optional cron-based renewal schedule (must not repeat more frequently than once a day) and a fee amount.
| Name | Type | Req | Description |
|---|---|---|---|
| fee | object | — | The recurring charge for this subscription. |
| name | string | yes | Display name of the subscription, e.g. 'Netflix' or 'Gym membership'. |
| notes | string | — | Free-text notes about the subscription. |
| remindMe | boolean | — | Whether to send renewal reminders for this subscription |
| renewalCronExpression | string | — | Cron expression describing how often the subscription renews. Must not repeat more frequently than once a day. |
| status | string | yes | Lifecycle status of the subscription at creation time. |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | — |
| message | string | — | — |
| title | string | — | — |
| variant | string | — | — |
{"name":"Netflix","status":"Active","renewalCronExpression":"0 0 1 * *","fee":{"value":1599,"currencyCode":"USD"},"notes":"Family plan, shared with parents","remindMe":true} create_task ~167
Creates a new household task. Only title is required; the task starts unassigned and uncompleted. Use assign_task, update_task, or complete_task to change it afterward.
| Name | Type | Req | Description |
|---|---|---|---|
| assignedToMemberId | string | — | The member ID of the household member. Get this from list_house_members. |
| dueDate | string | — | The date the task is due, in YYYY-MM-DD format. |
| notes | string | — | Freeform notes about the task. Not for assignment info. |
| preparationDate | string | — | The date to start preparing for the task, in YYYY-MM-DD format. Must be on or before the due date if both are set. |
| title | string | yes | The task's title, e.g. 'Take out the recycling'. Required; max 200 characters. |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | — |
| message | string | — | — |
| title | string | — | — |
| variant | string | — | — |
{"title":"Take out the recycling","assignedToMemberId":"7f3a9c2e1b4d8f6a0c5e3b7d9a1f4c6e","dueDate":"2026-08-01","preparationDate":"2026-07-30","notes":"Blue bin only"} create_vehicle ~261
Create 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.
| Name | Type | Req | Description |
|---|---|---|---|
| colour | string | — | Colour of the vehicle. |
| insuranceDocumentId | string | — | Document ID of insurance policy |
| make | string | — | Manufacturer of the vehicle, e.g. 'Toyota'. |
| model | string | — | Model name of the vehicle, e.g. 'Corolla'. |
| motDueDate | string | — | Date the next MOT (roadworthiness test) is due, in YYYY-MM-DD format. |
| notes | string | — | Free-text notes about the vehicle. |
| registration | string | — | The vehicle's registration/licence plate as shown on the plate. Free-text; format varies by country. |
| serviceDueDate | string | — | Date the vehicle's next scheduled service is due, in YYYY-MM-DD format. |
| taxDueDate | string | — | Date the vehicle's road tax is next due, in YYYY-MM-DD format. |
| vin | string | — | Vehicle Identification Number: a 17-character alphanumeric code unique to the vehicle. |
| year | integer | — | Model year of the vehicle. Must be between 1900 and 2100. |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | — |
| message | string | — | — |
| title | string | — | — |
| variant | string | — | — |
{"make":"Toyota","model":"Corolla","year":2021,"registration":"AB21 CDE","vin":"1HGCM82633A004352","colour":"Blue","motDueDate":"2026-11-15","taxDueDate":"2026-09-01","serviceDueDate":"2027-01-20","notes":"Winter tyres fitted"} defer_recommendation ~53
Add Later: defer a House Review recommendation and create a 7-day task
| Name | Type | Req | Description |
|---|---|---|---|
| recommendationId | string | yes | Id of a pending recommendation, taken from the id field of an item returned by get_house_review. |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | — |
| message | string | — | — |
| title | string | — | — |
| variant | string | — | — |
{"recommendationId":"0195e3c1a2b34c5d6e7f8091a2b3c4d5"} delete_appliance ~39
Soft-delete an appliance; it is hidden from list_appliances but not permanently erased.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | ID of the appliance to delete. |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | — |
| message | string | — | — |
| title | string | — | — |
| variant | string | — | — |
{"id":"01933f9c-7a2b-7c3d-8e4f-1a2b3c4d5e6f"} delete_calendar_event ~51
Soft-deletes a single calendar event by id. Events imported from a calendar subscription cannot be deleted here; unsubscribe from the source calendar instead.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Id of the calendar event to delete. |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | — |
| message | string | — | — |
| title | string | — | — |
| variant | string | — | — |
{"id":"0198f3a1b2c34d5e6f7089ab1c2d3e4f"} delete_contact ~61
Soft-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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The id of the contact to delete, as returned by create_contact or list_contacts. |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | — |
| message | string | — | — |
| title | string | — | — |
| variant | string | — | — |
{"id":"01928e4a7d3f7b9ac1e3f6d8b2a4c710"} delete_document ~62
Soft-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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The id of the document to delete, as returned by create_document or list_documents. |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | — |
| message | string | — | — |
| title | string | — | — |
| variant | string | — | — |
{"id":"01928e4a7d3f7b9ac1e3f6d8b2a4c710"} delete_meal_plan ~70
Remove a planned meal from the household's meal plan. This is a soft delete: the entry stops appearing in list_meal_plans and its date/meal-type slot becomes free again.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | ID of the meal plan entry to delete (from list_meal_plans) |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | — |
| message | string | — | — |
| title | string | — | — |
| variant | string | — | — |
{"id":"8f14e45f-ceea-467e-8a2f-1a2b3c4d5e6f"} delete_pet ~38
Soft-delete a pet; it is hidden from list_pets but not permanently erased.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | ID of the pet to delete. |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | — |
| message | string | — | — |
| title | string | — | — |
| variant | string | — | — |
{"id":"01933f9c-7a2b-7c3d-8e4f-1a2b3c4d5e6f"} delete_recipe ~78
Delete a recipe from the household's collection. This is a soft delete; any meal plan entries still linked to this recipe are automatically converted into custom entries that keep a snapshot of its name, ingredients and instructions, so they aren't left with a dangling recipe link.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | ID of the recipe to delete (from list_recipes) |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | — |
| message | string | — | — |
| title | string | — | — |
| variant | string | — | — |
{"id":"8f14e45f-ceea-467e-8a2f-1a2b3c4d5e6f"} delete_recurring_calendar_event ~40
Delete a recurring calendar event and all its future instances.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Id of the recurring calendar event (template) to delete. |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | — |
| message | string | — | — |
| title | string | — | — |
| variant | string | — | — |
{"id":"0198f3a1b2c34d5e6f7089ab1c2d3e4f"} delete_recurring_task ~47
Delete a recurring task and all its uncompleted future instances.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The recurring task's ID, as returned by create_recurring_task or list_recurring_tasks. |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | — |
| message | string | — | — |
| title | string | — | — |
| variant | string | — | — |
{"id":"5c3d2e1f0a9b8c7d6e5f4a3b2c1d0e9f"} delete_subscription ~27
Soft-delete a subscription
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | ID of the subscription to soft-delete. |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | — |
| message | string | — | — |
| title | string | — | — |
| variant | string | — | — |
{"id":"0198c1f4b2c07a1b9e4d5f6a7b8c9d0e"} delete_task ~59
Soft-deletes a task: it stops appearing in list_tasks but the record is retained rather than permanently removed. Fails if the task was already deleted.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The task's ID, as returned by create_task or list_tasks. |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | — |
| message | string | — | — |
| title | string | — | — |
| variant | string | — | — |
{"id":"018f2c9a1b2c7d3e9a4f5b6c7d8e9f0a"} delete_vehicle ~27
Soft-delete a vehicle
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | ID of the vehicle to soft-delete. |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | — |
| message | string | — | — |
| title | string | — | — |
| variant | string | — | — |
{"id":"0198c1f4b2c07a1b9e4d5f6a7b8c9d0e"} forget_memory ~44
Forget (soft-delete) a memory by id. Use when a memory is superseded or no longer relevant.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Id from a prior recall_memory result. |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | — |
| message | string | — | — |
| title | string | — | — |
| variant | string | — | — |
{"id":"0195e3c1a2b34c5d6e7f8091a2b3c4d5"} get_house ~59
Return full details for the household the current session is scoped to: name, address, invite code, notes, join settings, members, subscription status, and resolved feature-flag states. No parameters — the household is resolved server-side from the authenticated session.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | — |
| message | string | — | — |
| title | string | — | — |
| variant | string | — | — |
{} get_house_review ~70
Return this week's pending House Review recommendations (data gaps like a missing appliance warranty date or vehicle MOT date), re-validated live so items already filled in, actioned, or superseded by an open task are dropped before they're returned. Pro-gated: fails if the household isn't on a Pro plan.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | — |
| message | string | — | — |
| title | string | — | — |
| variant | string | — | — |
{} get_profile ~59
Return the authenticated user's profile: name, email, AI-consent status, and timezone. Also records this call as user activity (bumps last-seen) as a side effect. No parameters — the user is resolved server-side from the authenticated session.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | — |
| message | string | — | — |
| title | string | — | — |
| variant | string | — | — |
{} get_weather_forecast ~47
Get weather forecast for the household's location
| Name | Type | Req | Description |
|---|---|---|---|
| forecastDays | integer | — | Number of forecast days to return, from 1 to 5. Defaults to 3 if omitted. |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | — |
| message | string | — | — |
| title | string | — | — |
| variant | string | — | — |
{"forecastDays":3} list_appliances ~16
List all appliances in the household
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | — |
| message | string | — | — |
| title | string | — | — |
| variant | string | — | — |
{} list_calendar_events ~117
List calendar events with optional date-range filters
| Name | Type | Req | Description |
|---|---|---|---|
| startDateFrom | string | — | Inclusive lower bound of the date range, ISO 8601 date-time in UTC. An event matches if it ends (or, when it has no end, starts) on or after this instant. Omit for no lower bound. |
| startDateTo | string | — | Inclusive upper bound of the date range, ISO 8601 date-time in UTC. An event matches if it starts on or before this instant. Omit for no upper bound. |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | — |
| message | string | — | — |
| title | string | — | — |
| variant | string | — | — |
{"startDateFrom":"2026-07-01T00:00:00Z","startDateTo":"2026-07-31T23:59:59Z"} list_contacts ~26
List all contacts in the household. Takes no parameters; soft-deleted contacts are excluded.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | — |
| message | string | — | — |
| title | string | — | — |
| variant | string | — | — |
{} list_documents ~55
List documents in the household, optionally filtered to a single document type. Soft-deleted documents are excluded.
| Name | Type | Req | Description |
|---|---|---|---|
| documentType | string | — | Optional filter to only return documents of this type. Omit to return documents of all types. |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | — |
| message | string | — | — |
| title | string | — | — |
| variant | string | — | — |
{}{"documentType":"Passport"} list_global_recipes ~26
List the global/Discover recipe catalogue (curated recipes available to all households)
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | — |
| message | string | — | — |
| title | string | — | — |
| variant | string | — | — |
{} list_house_members ~24
List household members with their userId, name, nickname, and role.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | — |
| message | string | — | — |
| title | string | — | — |
| variant | string | — | — |
{} list_houses ~44
List 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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | — |
| message | string | — | — |
| title | string | — | — |
| variant | string | — | — |
{} list_meal_plans ~73
List meal plans in the household with an optional date range
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | — | Inclusive date range start (format: YYYY-MM-DD). Omit for an open-ended start. |
| to | string | — | Inclusive date range end (format: YYYY-MM-DD). Omit for an open-ended end. |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | — |
| message | string | — | — |
| title | string | — | — |
| variant | string | — | — |
{"from":"2026-07-14","to":"2026-07-21"} list_pets ~16
List all pets in the household
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | — |
| message | string | — | — |
| title | string | — | — |
| variant | string | — | — |
{} list_recipes ~16
List all recipes in the household
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | — |
| message | string | — | — |
| title | string | — | — |
| variant | string | — | — |
{} list_shopping_list_items ~20
List all shopping list items in the household
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | — |
| message | string | — | — |
| title | string | — | — |
| variant | string | — | — |
{} list_subscriptions ~38
List subscriptions with optional status filter
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | — | Only return subscriptions with this status. Omit to return subscriptions of all statuses. |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | — |
| message | string | — | — |
| title | string | — | — |
| variant | string | — | — |
{"status":"Active"} list_tasks ~229
Lists tasks in the household with optional filters (assignee, due-date range, completion status) and cursor-based pagination. Excludes completed tasks by default; results are sorted by due date ascending, with tasks that have no due date listed first.
| Name | Type | Req | Description |
|---|---|---|---|
| assignedToMemberId | string | — | Filter to tasks assigned to this household member ID. Omit to include tasks for all assignees. |
| cursor | string | — | Opaque pagination cursor from a previous list_tasks response's nextCursor. Omit to fetch the first page. |
| dueDateOnOrAfter | string | — | Only include tasks with a due date on or after this date (YYYY-MM-DD). Tasks with no due date never match. |
| dueDateOnOrBefore | string | — | Only include tasks with a due date on or before this date (YYYY-MM-DD). Tasks with no due date never match. |
| includeCompleted | boolean | — | Whether to include completed tasks in the results. Default: false |
| limit | integer | — | Maximum number of tasks to return per page. 1-100, default 50. |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | — |
| message | string | — | — |
| title | string | — | — |
| variant | string | — | — |
{"assignedToMemberId":"7f3a9c2e1b4d8f6a0c5e3b7d9a1f4c6e","includeCompleted":false,"dueDateOnOrAfter":"2026-07-01","dueDateOnOrBefore":"2026-07-31","limit":20}