Sergio by Serviche
REMOTE · SERGIO.SERVICHE.COM
Make sure nothing falls through the cracks in your cleaning business, even when you're not watching.
Available components
Last scanned (15 hours ago)
Scores higher than 74% of remote servers
Reachable. Last reached 21 Nov 2026.
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability53
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 24472 tokens (~235/item across 104 items; 104 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management32
- Stability check failed: schema churn in the 12 days we've observed: 8 tool removals, 1 breaking changes, 0 auth/transport breaks, 4 additions. See how to fix → Fail
Tool Coverage76
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 27% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 10 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 105 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “create_client” rewrote its description, which is the text the model reads security
- Tool “edit_client” rewrote its description, which is the text the model reads security
- Tool “report_feedback” rewrote its description, which is the text the model reads security
- New tool “move_address_to_contact” functional
- “edit_client” added an optional parameter “access_method” cosmetic
- “edit_client” added an optional parameter “same_person_as” cosmetic
- “edit_client” added an optional parameter “separate_person” cosmetic
- “report_feedback” added an optional parameter “hypothesis” cosmetic
- 18 Nov 26 +1
- Tool “catalog” rewrote its description, which is the text the model reads security
- Tool “create_client” rewrote its description, which is the text the model reads security
- “catalog” added an optional parameter “schemas” cosmetic
- “create_client” added an optional parameter “address” cosmetic
- 16 Nov 26 0
- A breaking change shipped without a version bump: still 1.0.2 ▼ security
- Tool “add_training_question” was removed ▼ security
- Tool “archive_training_module” was removed ▼ security
- Tool “create_training_module” was removed ▼ security
- Tool “delete_training_question” was removed ▼ security
- Tool “edit_training_module” was removed ▼ security
- Tool “edit_training_question” was removed ▼ security
- Tool “generate_training_questions” was removed ▼ security
- Tool “remove_training_assignment” was removed ▼ security
- Tool “create_client” rewrote its description, which is the text the model reads security
- Tool “create_handbook_article” rewrote its description, which is the text the model reads security
- Tool “draft_handbook_edit” rewrote its description, which is the text the model reads security
- Tool “edit_client” rewrote its description, which is the text the model reads security
- Tool “edit_handbook_article” rewrote its description, which is the text the model reads security
- Tool “query” rewrote its description, which is the text the model reads security
- Tool “read” rewrote its description, which is the text the model reads security
- Tool “update_settings” rewrote its description, which is the text the model reads security
- “create_client” added an optional parameter “platform_customer” cosmetic
- “edit_client” added an optional parameter “platform_customer” cosmetic
- 14 Nov 26 +1
- Stability: 0.13 → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.2 ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “read” rewrote its description, which is the text the model reads security
- Tool “reopen_task” rewrote its description, which is the text the model reads security
- Tool “update_settings” rewrote its description, which is the text the model reads security
- “reopen_task” added a required parameter “reopen_reason”, so existing callers break ▼ functional
- 13 Nov 26 0
- New tool “record_staff_event” functional
- 12 Nov 26 0
- Tool “update_settings” rewrote its description, which is the text the model reads security
- New tool “edit_staff_member” functional
- 11 Nov 26 +1
- Tool “query” rewrote its description, which is the text the model reads security
- Tool “update_settings” rewrote its description, which is the text the model reads security
- New tool “log_call” functional
- 10 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://sergio.serviche.com/api/agent/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=serviche.com | CN=YE1,O=Let's Encrypt,C=US | 9 Oct 2026 | 7 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 53905d714ec75cf625c8ee2fc4453319a0f |
| SANs: *.serviche.com, serviche.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of sergio.serviche.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| serviche.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 realm="sergio-agent", resource_metadata="https://sergio.serviche.com/.well-known/oauth-protected-resource"
Bearer realm="sergio-agent", resource_metadata="https://sergio.serviche.com/.well-known/oauth-protected-resource" | Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| content-security-policy | default-src 'none'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=(), serial=(), bluetooth=(), display-capture=(self) |
Protected resource metadata
| Document | https://sergio.serviche.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://sergio.serviche.com/api/agent/mcp |
| Authorisation server | https://sergio.serviche.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://sergio.serviche.com/api/agent/mcp | Verified | 200 | |
| http (plaintext) | http://sergio.serviche.com/api/agent/mcp | HTTPS enforced | 301 | https://sergio.serviche.com/api/agent/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
accept_smaller_sync Accept a smaller sync ~170
Applies a booking sync Sergio held back for returning far fewer bookings than it holds, once, and makes that size the new normal, as Accept this smaller sync on Data sources does. job_id is the held sync's import job. Pass the same idempotency_key when retrying. An owner-level change: Sergio tells the owner after it is made.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | yes | Your id for this operation (8-128 of A-Z a-z 0-9 . _ : -). Reuse it on every retry of the same operation; use a new one for a new operation. |
| jobId | string | yes | – |
| reason | string | – | Why you are doing this, in one sentence. The owner sees it in the notice Sergio sends after the change. |
No output schema declared.
No examples provided.
accept_suggestion Accept a Sergio suggestion ~218
Accepts a Sergio suggestion card, as the card's accept does. action "accept" commits it as a task (optionally with your edited title, details or due, ISO 8601 or null); "accept_no_task" resolves it without a task when the work already happened. A card whose move would send a message, move money, open to the public or grant access is refused with where the owner does it; draft instead (create_draft, or run_suggestion_now on a draft card). Pass the same idempotency_key when retrying; a repeat returns the first answer.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | – |
| due | – | – | – |
| idempotency_key | string | yes | Your id for this operation (8-128 of A-Z a-z 0-9 . _ : -). Reuse it on every retry of the same operation; use a new one for a new operation. |
| suggestion_id | string | yes | – |
| taskDescription | string | – | – |
| taskTitle | string | – | – |
No output schema declared.
No examples provided.
add_client_note Add a note to a client ~143
Adds an office note to a client's record (category general, access, preference, alert or scheduling; pinned keeps it surfaced). Only the team sees it; nothing is sent. Pass the same idempotency_key when retrying; a repeat returns the original note.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| client_id | string | yes | – |
| content | string | yes | – |
| idempotency_key | string | yes | Your id for this operation (8-128 of A-Z a-z 0-9 . _ : -). Reuse it on every retry of the same operation; use a new one for a new operation. |
| pinned | boolean | – | – |
No output schema declared.
No examples provided.
add_staff_member Add a staff member ~228
To rename someone already on the roster, pass rename_staff_id with the new name; the old spelling keeps pointing at them. Otherwise adds a field worker to the roster, as the staff page's Add staff does: name (a profile with that name is reused, never duplicated), optional employment_type (employee or contractor), or client_id to make an existing contact staff (a name clash comes back as name_conflict; call again with link_to_staff_id to link instead). This gives them no sign-in; inviting someone to Sergio is the owner's. Nothing is sent. Pass the same idempotency_key when retrying.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | string | – | – |
| employment_type | string | – | – |
| idempotency_key | string | yes | Your id for this operation (8-128 of A-Z a-z 0-9 . _ : -). Reuse it on every retry of the same operation; use a new one for a new operation. |
| link_to_staff_id | string | – | – |
| name | string | yes | – |
| rename_staff_id | string | – | – |
No output schema declared.
No examples provided.
add_staff_scheduling_rule Add a scheduling rule for a field worker ~234
Adds a plain-English scheduling rule for one field worker (staff_id), as Add rule on their Rules tab does, e.g. "Won't work Tuesdays" or "Only mornings in Brooklyn". hardness hard (default: never scheduled against it) or soft (avoided when possible). The same wording again updates the same rule. Answers the worker's rules with their ids. Remove one with remove_staff_scheduling_rule; read every rule with read staff_scheduling_rules. Pass the same idempotency_key when retrying. An owner-level change: Sergio tells the owner after it is made.
| Name | Type | Req | Description |
|---|---|---|---|
| hardness | string | – | – |
| idempotency_key | string | yes | Your id for this operation (8-128 of A-Z a-z 0-9 . _ : -). Reuse it on every retry of the same operation; use a new one for a new operation. |
| plainEnglish | string | yes | – |
| reason | string | – | Why you are doing this, in one sentence. The owner sees it in the notice Sergio sends after the change. |
| staff_id | string | yes | – |
No output schema declared.
No examples provided.
answer_google_review_match Link or unlink a Google review and a client ~158
Says which client wrote a Google review, as Contacts > Needs review does: client_id links it (also moving a review linked to the wrong client), client_id null says no client wrote it (unlinking a linked review). A link closes that client's review requests. Find reviews and their ids with read google_reviews. Nothing is sent or posted to Google. Pass the same idempotency_key when retrying.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | – | yes | – |
| idempotency_key | string | yes | Your id for this operation (8-128 of A-Z a-z 0-9 . _ : -). Reuse it on every retry of the same operation; use a new one for a new operation. |
| review_id | string | yes | – |
No output schema declared.
No examples provided.
answer_handbook_question Answer a handbook question ~202
Answers or files a logged question (question_id from read entity sop_questions), as Handbook > Admin > Questions does: answer, status (open, answered, needs_new_sop, sop_updated, dismissed), sop_id it belongs to, notes. save_as_sop: true has Sergio write the answer into the handbook (the matching article, or a new one). Pass the same idempotency_key when retrying; a repeat does not save it to the handbook twice.
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | – | – |
| idempotency_key | string | yes | Your id for this operation (8-128 of A-Z a-z 0-9 . _ : -). Reuse it on every retry of the same operation; use a new one for a new operation. |
| notes | string | – | – |
| question_id | string | yes | – |
| save_as_sop | boolean | – | – |
| sop_id | – | – | – |
| status | string | – | – |
No output schema declared.
No examples provided.
approve_follow_up_style Approve the lead journeys drafted from follow-up answers ~256
Records the owner's approval of the lead journeys drafted from how the business follows up today, as Get started's follow-up step does. The journeys must already be saved as the answers draw them (answers: firstChannel, speed, followUpChannel, tries, overDays, giveUpDays; sources: the journeys approved, as lead sources such as site_thumbtack or web_form; Get started's lead sources map to them). Save the journeys first through the lead follow-up journeys setting (settings.lead_pursuit_program), drawn from these answers; otherwise the route answers journeys_not_saved. Writes no journey and sends nothing. Pass the same idempotency_key when retrying. An owner-level change: Sergio tells the owner after it is made.
| Name | Type | Req | Description |
|---|---|---|---|
| answers | object | yes | – |
| idempotency_key | string | yes | Your id for this operation (8-128 of A-Z a-z 0-9 . _ : -). Reuse it on every retry of the same operation; use a new one for a new operation. |
| reason | string | – | Why you are doing this, in one sentence. The owner sees it in the notice Sergio sends after the change. |
| sources | array | yes | – |
No output schema declared.
No examples provided.
archive_handbook_article Remove a handbook article ~113
Takes an article out of the handbook as its Delete does: it is marked inactive and kept (edit_handbook_article cannot bring it back; a person can). Pass the same idempotency_key when retrying.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | yes | Your id for this operation (8-128 of A-Z a-z 0-9 . _ : -). Reuse it on every retry of the same operation; use a new one for a new operation. |
| sop_id | string | yes | – |
No output schema declared.
No examples provided.
assign_conversation Assign a conversation ~155
Assigns a conversation to a teammate, as the thread header's Assign menu does: assigned_member_id is the teammate's id (read entity org_members), or null to unassign; assigned_to (the teammate's exact name) is accepted instead. A name that is not exactly one current teammate is refused. Pass the same idempotency_key when retrying.
| Name | Type | Req | Description |
|---|---|---|---|
| assigned_member_id | – | – | – |
| assigned_to | – | – | – |
| conversation_id | string | yes | – |
| idempotency_key | string | yes | Your id for this operation (8-128 of A-Z a-z 0-9 . _ : -). Reuse it on every retry of the same operation; use a new one for a new operation. |
No output schema declared.
No examples provided.
assign_task Assign a task ~137
Assigns a task to a team member (their member id from read('team_members') or whoami), or unassigns it with null. Pass the same idempotency_key when retrying; a repeat returns the task, reports what the original call applied, and changes nothing if the task changed since.
| Name | Type | Req | Description |
|---|---|---|---|
| assigned_to | – | yes | – |
| idempotency_key | string | yes | Your id for this operation (8-128 of A-Z a-z 0-9 . _ : -). Reuse it on every retry of the same operation; use a new one for a new operation. |
| task_id | string | yes | – |
No output schema declared.
No examples provided.
bulk_clear_conversations Clear old conversations in bulk ~206
Clears every thread older than a cutoff at once, as the inbox's bulk Clear does (owner or admin seats only): mode date clears threads quiet for olderThanDays (default 14) or since cutoff (ISO date); mode leads clears threads a lead follow-up owns. includeTasks also closes their open tasks; includeReplyOwed also clears threads the customer wrote last in (date mode). The Quo inbox follows when the business's write setting allows. Pass the same idempotency_key when retrying.
| Name | Type | Req | Description |
|---|---|---|---|
| cutoff | string | – | – |
| idempotency_key | string | yes | Your id for this operation (8-128 of A-Z a-z 0-9 . _ : -). Reuse it on every retry of the same operation; use a new one for a new operation. |
| includeReplyOwed | boolean | – | – |
| includeTasks | boolean | – | – |
| mode | string | – | – |
| olderThanDays | integer | – | – |
No output schema declared.
No examples provided.
cancel_import Cancel a running import ~118
Cancels a running import (message history or a spreadsheet), as Cancel in the import drawer does; what it already brought in stays. job_id comes from start_history_import or the import list. Pass the same idempotency_key when retrying.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | yes | Your id for this operation (8-128 of A-Z a-z 0-9 . _ : -). Reuse it on every retry of the same operation; use a new one for a new operation. |
| job_id | string | yes | – |
No output schema declared.
No examples provided.
catalog What can I do ~142
Returns `asks`, a short list of things a person can ask (give your user these when they ask what you can do), then lists every tool this seat can call right now, grouped by family, with whether each one changes anything, and under `held` the actions only a person can do (sending, money, access), each with the reason and where in the app the owner does it, and under `not_lent` every other app action agents cannot do yet, with where a person does it. Pass schemas: [tool names] to get each named tool its exact input schema (inputSchema) before calling it.
| Name | Type | Req | Description |
|---|---|---|---|
| schemas | array | – | – |
No output schema declared.
No examples provided.
clear_staff_availability_override Clear a worker's schedule change for a date ~135
Clears one field worker's schedule change on a date (YYYY-MM-DD), so their normal weekly hours apply again, as Clear on the staff calendar does. To set a change, use set_staff_availability. Nothing is sent. Pass the same idempotency_key when retrying.
| Name | Type | Req | Description |
|---|---|---|---|
| cleaner_name | string | yes | – |
| date | string | yes | – |
| idempotency_key | string | yes | Your id for this operation (8-128 of A-Z a-z 0-9 . _ : -). Reuse it on every retry of the same operation; use a new one for a new operation. |
No output schema declared.
No examples provided.
close_conversation_flow Mark a conversation's flow done ~155
Marks a conversation's flow done, as the flow chip's Mark done does. conversationFlowId names the flow when the thread has more than one. outcome (for example declined) closes it early without marking its steps done; close_note is optional. Pass the same idempotency_key when retrying.
| Name | Type | Req | Description |
|---|---|---|---|
| close_note | string | – | – |
| conversationFlowId | string | – | – |
| conversation_id | string | yes | – |
| idempotency_key | string | yes | Your id for this operation (8-128 of A-Z a-z 0-9 . _ : -). Reuse it on every retry of the same operation; use a new one for a new operation. |
| outcome | string | – | – |
No output schema declared.
No examples provided.
complete_task Complete a task ~135
Marks a task done, recorded as completed by this seat. A flow-step task also completes its step, as the check box does. Pass the same idempotency_key when retrying; a repeat returns the task, reports what the original call applied, and changes nothing if the task changed since.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | yes | Your id for this operation (8-128 of A-Z a-z 0-9 . _ : -). Reuse it on every retry of the same operation; use a new one for a new operation. |
| note | string | – | – |
| task_id | string | yes | – |
No output schema declared.
No examples provided.
complete_tasks_bulk Mark several tasks done ~169
Marks up to 200 tasks done at once, as the Tasks page's selection bar does; each closes exactly as its own check box would. Kinds that close only from their own screen (lead follow-ups, flow steps, questions, staff check-ins, rules) are refused per task and reported in results. action "reopen" is the Undo. Pass the same idempotency_key when retrying; a repeat returns the first answer and moves nothing again.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | – |
| idempotency_key | string | yes | Your id for this operation (8-128 of A-Z a-z 0-9 . _ : -). Reuse it on every retry of the same operation; use a new one for a new operation. |
| ids | array | yes | – |
No output schema declared.
No examples provided.
create_campaign Build a campaign (saved as a draft) ~1,017
Builds a campaign as the Campaigns page's New campaign does, always saved as a draft: name, the messages (steps: the opener first, each { template, delayDays?, channel? text | email | call }), offer, audience (audience_filter, or audience_source { kind: list | view | people | filter }), caps and send window. Templates use Sergio's merge tags ({{Client First Name}}, {{User Company}}, {{Offer}}, {{Offer Expiry Date}} and the rest listed on steps.template), never a hard-coded business or client name. audience_filter takes the builder's own keys (visits, days since last booking, last booking total, days since last contact, frequency, services); audience_mode rolling (default) keeps adding people as they qualify (evergreen), fixed freezes the audience at start. read campaigns returns this vocabulary and existing campaigns to copy from. Sergio's audience rules apply unless your person asks otherwise, so leave those fields out: it leaves out anyone with an upcoming booking (audience_filter.noUpcomingBooking) and anyone another campaign reached lately (contact_floor_days, the business's window, 30 days unless changed), and new matches join on their own (audience_mode rolling). The people a rule leaves out show in the campaign as Excluded by Sergio, where a person can include one anyway, so another campaign running over the same people is not something to warn about. The answer's audience_rules says all this in one sentence: tell your person that sentence when you report the draft. A credit your person names is the offer the message describes (see offer_text); never ask them to apply credits. Nobody is enrolled and nothing is sent until it starts: start_campaign (your person sees every message first and says yes), or Start campaign in the app; turning on automatic sending stays the owner's. Pass the same idempotency_key when retrying; a repeat returns the same draft.
| Name | Type | Req | Description |
|---|---|---|---|
| audience_filter | object | – | Who the campaign is for, as the builder's Audience section sets it. Use these keys only; every key given must hold. |
| audience_mode | string | – | – |
| audience_source | – | – | Instead of audience_filter, follow Contacts: { kind: "list", listId } | { kind: "view", viewId } | { kind: "people", clientIds: [...] } | { kind: "filter", query } (a Contacts filter). |
| auto_send | boolean | – | – |
| color | – | – | – |
| contact_floor_days | – | – | – |
| cooldown_days | integer | – | – |
| daily_cap | integer | – | – |
| enrollment_source | string | – | – |
| hold_negative_feedback | boolean | – | – |
| idempotency_key | string | yes | Your id for this operation (8-128 of A-Z a-z 0-9 . _ : -). Reuse it on every retry of the same operation; use a new one for a new operation. |
| min_days_since_visit | integer | – | – |
| name | string | yes | – |
| offer_expiry_days | – | – | Days the offer stays good after each person's first message; {{Offer Expiry Date}} quotes the date. |
| offer_text | – | – | offer_text is the offer, written the way the builder writes it ("$25 off your next booking", "10% off your next booking", "a free fridge clean"); {{Offer}} sends those exact words to every recipient.… |
| queue_expiry_days | integer | – | – |
| send_time_local | – | – | – |
| send_window_hours | – | – | – |
| short_code | – | – | – |
| steps | array | – | – |
| text_by_email_subject | – | – | The one email subject every text step takes when it goes by email to someone Sergio may not text. An email step keeps its own. |
No output schema declared.
No examples provided.
create_client Add a contact ~349
Adds a contact as the Add contact form does: a name, a phone (with area code) or an email is enough. contact_type picks client (default), lead, applicant, staff or other. A phone or email that already belongs to a contact, or else the exact name of one, is answered with that contact (duplicate_contact, matchedOn, its id in the message); use it, or pass createAnyway: true for a different person who shares it (two people can share a name; a shared phone stays with its owner). Look a person up first with findClientByIdentifier or read. Pass the same idempotency_key when retrying; a repeat returns the contact the first call made. platform_customer links the contact to its booking platform customer id (platform defaults to the company's one booking platform); an id another contact holds is refused with that contact. address {line, apt, zip} saves the client's service address with the contact (its default), through the same address book as add_client_address; a line without a 5-digit ZIP refuses the whole call (zip_required) and creates nothing. A booking for this client then books at that address.
| Name | Type | Req | Description |
|---|---|---|---|
| address | object | – | – |
| contact_type | string | – | – |
| createAnyway | boolean | – | – |
| string | – | – | |
| idempotency_key | string | yes | Your id for this operation (8-128 of A-Z a-z 0-9 . _ : -). Reuse it on every retry of the same operation; use a new one for a new operation. |
| name | string | – | – |
| phone | string | – | – |
| platform_customer | object | – | – |
No output schema declared.
No examples provided.
create_contact_list Make a contact list ~110
Makes a contact list on the Contacts page, or answers the live one with that name. Add people to it with edit_contacts (op add_to_list). Pass the same idempotency_key when retrying.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | yes | Your id for this operation (8-128 of A-Z a-z 0-9 . _ : -). Reuse it on every retry of the same operation; use a new one for a new operation. |
| name | string | yes | – |
No output schema declared.
No examples provided.
create_contact_tag Make a contact tag ~106
Makes a tag on the Contacts page, or answers the live one with that name. Tag people with edit_contacts (op add_tags). Pass the same idempotency_key when retrying.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | yes | Your id for this operation (8-128 of A-Z a-z 0-9 . _ : -). Reuse it on every retry of the same operation; use a new one for a new operation. |
| name | string | yes | – |
No output schema declared.
No examples provided.
create_draft Draft a message ~159
Writes a message into a client conversation's draft box. It never sends: a person on the team reviews the exact text and presses Send in Sergio, where the organization's sending policy applies. Give conversationId, or clientId to use that client's conversation. Pass the same idempotency_key when retrying; a repeat returns the original draft.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | – |
| channel | string | – | – |
| clientId | string | – | – |
| conversationId | string | – | – |
| idempotency_key | string | yes | Your id for this operation (8-128 of A-Z a-z 0-9 . _ : -). Reuse it on every retry of the same operation; use a new one for a new operation. |
No output schema declared.
No examples provided.
create_handbook_article Add a handbook article ~383
Adds an article (SOP) to the handbook, as Handbook > Admin > New SOP does: title, content_md (markdown), optional category, tags, audience (cleaner = staff, va = office), bucket (A, B or C), licensed (from a franchise or licensed manual: never shared outside the business). Nothing is sent. Before adding anything to the handbook, search the sops read entity by the topic (search finds by meaning): when an article already covers it, put the new text into that article (edit_handbook_article with its full content_md, the new lines placed where they belong, or draft_handbook_edit) instead of a new one; create a new article only when none fits, and say which closest article you found and why it did not fit. Audience comes from the person's words: cleaner SOPs, cleaning standards or staff = cleaner; policies, office or VA = va; when the words do not say, ask in one line. Ask which place, in one line naming both, when two places fit the person's words equally well: two articles that both match; a place the person named outright is never a tie. The proposed change is the confirmation, so never ask "should I add this?" first. Pass the same idempotency_key when retrying; a repeat returns the same article.
| Name | Type | Req | Description |
|---|---|---|---|
| audience | string | – | – |
| bucket | string | – | – |
| category | string | – | – |
| content_md | string | yes | – |
| idempotency_key | string | yes | Your id for this operation (8-128 of A-Z a-z 0-9 . _ : -). Reuse it on every retry of the same operation; use a new one for a new operation. |
| licensed | boolean | – | – |
| tags | array | – | – |
| title | string | yes | – |
No output schema declared.
No examples provided.
create_scanner Create a Scanner ~279
Saves a new Scanner, as Save on New Scanner does: question (required), and optionally name, inputs, look-again timing, who gets the task, due rule, destination, contact types, and enabled (on or off; there is no trial mode). Pass the same idempotency_key when retrying. An owner-level change: Sergio tells the owner after it is made.
| Name | Type | Req | Description |
|---|---|---|---|
| assignee_kind | string | – | – |
| assignee_member_id | – | – | – |
| contact_types | – | – | – |
| destination | string | – | – |
| draft | boolean | – | – |
| due_hours | – | – | – |
| due_rule | string | – | – |
| enabled | boolean | – | – |
| idempotency_key | string | yes | Your id for this operation (8-128 of A-Z a-z 0-9 . _ : -). Reuse it on every retry of the same operation; use a new one for a new operation. |
| inputs | array | – | – |
| look_again_kind | string | – | – |
| look_again_minutes | – | – | – |
| name | string | – | – |
| question | string | yes | – |
| reason | string | – | Why you are doing this, in one sentence. The owner sees it in the notice Sergio sends after the change. |
| refinements | array | – | – |
| rollup | boolean | – | – |
No output schema declared.
No examples provided.
create_task Create a task ~150
Adds a task to the team's work queue, optionally tied to a client or conversation and due at a time (ISO 8601). Pass the same idempotency_key when retrying; a repeat returns the original task.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | string | – | – |
| conversation_id | string | – | – |
| description | string | – | – |
| due_date | string | – | – |
| idempotency_key | string | yes | Your id for this operation (8-128 of A-Z a-z 0-9 . _ : -). Reuse it on every retry of the same operation; use a new one for a new operation. |
| priority | string | – | – |
| title | string | yes | – |
No output schema declared.
No examples provided.
decide_company_document_suggestion Approve, edit or skip a document suggestion ~178
Decides one suggestion Sergio read from an uploaded document (itemId from read_company_document or read entity company_documents), as the setup guide's taps do: approve creates the flow as a draft that is OFF or the recurring task PAUSED (nothing runs or sends until a person turns it on); edit rewrites its sentence; skip drops it. approve with sentence applies that edit first. A repeat returns the same created row.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| document_id | string | yes | – |
| idempotency_key | string | yes | Your id for this operation (8-128 of A-Z a-z 0-9 . _ : -). Reuse it on every retry of the same operation; use a new one for a new operation. |
| itemId | string | yes | – |
| sentence | string | – | – |
No output schema declared.
No examples provided.
declare_lead_sources Say where leads come from ~186
Records where the business gets its leads (keys from the setup guide list, for example thumbtack, google_lsa, yelp, website, other; other needs its words), as Get started's lead sources step does. An answer only: it opens and sends nothing. Pass the same idempotency_key when retrying. An owner-level change: Sergio tells the owner after it is made.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | yes | Your id for this operation (8-128 of A-Z a-z 0-9 . _ : -). Reuse it on every retry of the same operation; use a new one for a new operation. |
| keys | array | yes | – |
| other | string | – | – |
| reason | string | – | Why you are doing this, in one sentence. The owner sees it in the notice Sergio sends after the change. |
No output schema declared.
No examples provided.
delete_campaign Delete a campaign ~122
Deletes a campaign as Delete on its card does: its queued messages are pulled back first; messages already sent stay in their threads. It cannot be undone; to stop it for now, edit_campaign with status paused. Pass the same idempotency_key when retrying.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | – |
| idempotency_key | string | yes | Your id for this operation (8-128 of A-Z a-z 0-9 . _ : -). Reuse it on every retry of the same operation; use a new one for a new operation. |
No output schema declared.
No examples provided.
delete_client_note Delete a client note ~128
Deletes a note from a contact's card outright, as the note's Delete does. It cannot be undone (the activity log keeps what it said). Pass the same idempotency_key when retrying; a repeat after the note is gone answers success.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | string | yes | – |
| idempotency_key | string | yes | Your id for this operation (8-128 of A-Z a-z 0-9 . _ : -). Reuse it on every retry of the same operation; use a new one for a new operation. |
| noteId | string | yes | – |
No output schema declared.
No examples provided.
delete_scanner Delete a Scanner ~155
Deletes a Scanner, as Delete in its editor does; the tasks it already made stay. To pause it instead, use set_scanner_on with enabled false. Pass the same idempotency_key when retrying. An owner-level change: Sergio tells the owner after it is made.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | yes | Your id for this operation (8-128 of A-Z a-z 0-9 . _ : -). Reuse it on every retry of the same operation; use a new one for a new operation. |
| reason | string | – | Why you are doing this, in one sentence. The owner sees it in the notice Sergio sends after the change. |
| scanner_id | string | yes | – |
No output schema declared.
No examples provided.
delete_task Delete a task ~132
Deletes a task outright, as the task menu's Delete does. It cannot be undone; to say a task is not needed, use skip_task instead. Deleting a Scanner's task tells that Scanner it was wrong. Pass the same idempotency_key when retrying; a repeat returns the first delete's answer.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | yes | Your id for this operation (8-128 of A-Z a-z 0-9 . _ : -). Reuse it on every retry of the same operation; use a new one for a new operation. |
| task_id | string | yes | – |
No output schema declared.
No examples provided.
dismiss_conversation_reminders Dismiss a conversation's reminders ~100
Dismisses every open reminder on a conversation, as the bell's Dismiss does. Pass the same idempotency_key when retrying.
| Name | Type | Req | Description |
|---|---|---|---|
| conversation_id | string | yes | – |
| idempotency_key | string | yes | Your id for this operation (8-128 of A-Z a-z 0-9 . _ : -). Reuse it on every retry of the same operation; use a new one for a new operation. |
No output schema declared.
No examples provided.
dismiss_notification Dismiss a notification ~126
Dismisses a notification card (action "dismiss"), snoozes it for its own snooze time ("snooze"), or marks it read ("read"), as the card's controls do. Pass the same idempotency_key when retrying.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | – |
| idempotency_key | string | yes | Your id for this operation (8-128 of A-Z a-z 0-9 . _ : -). Reuse it on every retry of the same operation; use a new one for a new operation. |
| notification_id | string | yes | – |
No output schema declared.
No examples provided.
dismiss_suggestion Dismiss a Sergio suggestion ~127
Dismisses a Sergio suggestion card, as the card's dismiss does. reason is optional ("Not needed" tells the Scanner that raised it that it was wrong). Pass the same idempotency_key when retrying; a repeat returns the first answer.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | yes | Your id for this operation (8-128 of A-Z a-z 0-9 . _ : -). Reuse it on every retry of the same operation; use a new one for a new operation. |
| reason | string | – | – |
| suggestion_id | string | yes | – |
No output schema declared.
No examples provided.
disposition_conversation Record a quiet thread's disposition ~162
Records why a quiet thread needs no reply, as the clear gate's picker does: spam (the contact becomes spam; its lead work stops and its Quo card is tagged when the business's write setting allows), lead (the contact becomes a lead), reengage (tags the contact for a later marketing touch) or no_action. It does not clear the thread. Pass the same idempotency_key when retrying.
| Name | Type | Req | Description |
|---|---|---|---|
| conversation_id | string | yes | – |
| disposition | string | yes | – |
| idempotency_key | string | yes | Your id for this operation (8-128 of A-Z a-z 0-9 . _ : -). Reuse it on every retry of the same operation; use a new one for a new operation. |
No output schema declared.
No examples provided.
draft_handbook_edit Have Sergio draft an article edit ~369
Asks Sergio to draft an edit to an article, as the article's Ask Sergio does: with context, the smallest change that does what it says; without, a general cleanup. The draft waits as a pending version (review_handbook_edit approves or rejects it). When the person gave the exact words to add, edit_handbook_article with them is the direct change; use this when they asked for a rewrite or cleanup. Before adding anything to the handbook, search the sops read entity by the topic (search finds by meaning): when an article already covers it, put the new text into that article (edit_handbook_article with its full content_md, the new lines placed where they belong, or draft_handbook_edit) instead of a new one; create a new article only when none fits, and say which closest article you found and why it did not fit. Audience comes from the person's words: cleaner SOPs, cleaning standards or staff = cleaner; policies, office or VA = va; when the words do not say, ask in one line. Ask which place, in one line naming both, when two places fit the person's words equally well: two articles that both match; a place the person named outright is never a tie. The proposed change is the confirmation, so never ask "should I add this?" first. Pass the same idempotency_key when retrying; a repeat returns the same draft without asking the model again.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | – |
| idempotency_key | string | yes | Your id for this operation (8-128 of A-Z a-z 0-9 . _ : -). Reuse it on every retry of the same operation; use a new one for a new operation. |
| sop_id | string | yes | – |
No output schema declared.
No examples provided.
edit_campaign Edit, pause or archive a campaign ~794
Edits a campaign as its builder does (the fields you pass change; the rest stay), or pauses (status paused, pulls back its queued sends) or archives it. Turning automatic sending off (auto_send false) is open. To start or resume one, use start_campaign (your person confirms first). Held for the owner, refused with where: starting it here, turning automatic sending on, and changing the messages, audience, caps or send window of a started campaign that sends automatically (turn auto_send off first, in the same call or before). Templates, offer and audience_filter follow the same rules as create_campaign (listed on each field). Pass the same idempotency_key when retrying.
| Name | Type | Req | Description |
|---|---|---|---|
| audience_filter | object | – | Who the campaign is for, as the builder's Audience section sets it. Use these keys only; every key given must hold. |
| audience_mode | string | – | – |
| audience_source | – | – | Instead of audience_filter, follow Contacts: { kind: "list", listId } | { kind: "view", viewId } | { kind: "people", clientIds: [...] } | { kind: "filter", query } (a Contacts filter). |
| auto_send | boolean | – | – |
| campaign_id | string | yes | – |
| color | – | – | – |
| contact_floor_days | – | – | – |
| cooldown_days | integer | – | – |
| daily_cap | integer | – | – |
| dismissed_tips | array | – | – |
| enrollment_source | string | – | – |
| hold_negative_feedback | boolean | – | – |
| idempotency_key | string | yes | Your id for this operation (8-128 of A-Z a-z 0-9 . _ : -). Reuse it on every retry of the same operation; use a new one for a new operation. |
| min_days_since_visit | integer | – | – |
| name | string | – | – |
| offer_expiry_days | – | – | Days the offer stays good after each person's first message; {{Offer Expiry Date}} quotes the date. |
| offer_text | – | – | offer_text is the offer, written the way the builder writes it ("$25 off your next booking", "10% off your next booking", "a free fridge clean"); {{Offer}} sends those exact words to every recipient.… |
| queue_expiry_days | integer | – | – |
| send_time_local | – | – | – |
| send_window_hours | – | – | – |
| short_code | – | – | – |
| status | string | – | – |
| steps | array | – | – |
| text_by_email_subject | – | – | The one email subject every text step takes when it goes by email to someone Sergio may not text. An email step keeps its own. |
No output schema declared.
No examples provided.
edit_client Edit a contact ~439
Edits a contact as the contact card's pencil does: name, phone (with area code), email, company_name, address (keep its zip if it had one), access_method (how the crew usually gets in, e.g. someone is home, key is hidden, lockbox; for one visit or this and later visits of a plan use add_booking_note kind access_method instead), access_notes, special_instructions, has_pets, pet_details, preferred_cleaner, preferences, availability_notes, contact_type. Send only the fields to change; a contact always keeps a name, phone or email. expected (field -> the value you read) refuses the save if someone changed it since (stale_write). A rename reaches the Quo card when the business's write setting allows. Renaming a staff contact to a name another staff member holds answers name_conflict with that person: ask your user, then send the name again with same_person_as (that staff id: this contact is them) or separate_person: true (a different person; the name stays on this contact only). platform_customer links the contact to its booking platform customer id; an id another contact holds is refused with that contact. Pass the same idempotency_key when retrying.
| Name | Type | Req | Description |
|---|---|---|---|
| access_method | – | – | – |
| access_notes | – | – | – |
| address | – | – | – |
| availability_notes | – | – | – |
| client_id | string | yes | – |
| company_name | – | – | – |
| contact_type | string | – | – |
| – | – | – | |
| expected | object | – | – |
| has_pets | – | – | – |
| idempotency_key | string | yes | Your id for this operation (8-128 of A-Z a-z 0-9 . _ : -). Reuse it on every retry of the same operation; use a new one for a new operation. |
| name | – | – | – |
| pet_details | – | – | – |
| phone | – | – | – |
| platform_customer | object | – | – |
| preferences | – | – | – |
| preferred_cleaner | – | – | – |
| same_person_as | string | – | – |
| separate_person | boolean | – | – |
| special_instructions | – | – | – |
No output schema declared.
No examples provided.
edit_contact_list Rename or archive a contact list ~124
Renames a contact list or archives it (archived: true; its people keep their other lists), as the Contacts page's list menu does. Pass the same idempotency_key when retrying.
| Name | Type | Req | Description |
|---|---|---|---|
| archived | boolean | – | – |
| idempotency_key | string | yes | Your id for this operation (8-128 of A-Z a-z 0-9 . _ : -). Reuse it on every retry of the same operation; use a new one for a new operation. |
| list_id | string | yes | – |
| name | string | – | – |
No output schema declared.
No examples provided.
edit_contact_tag Rename or archive a contact tag ~117
Renames a Contacts tag or archives it (archived: true), as the Contacts page's tag menu does. Pass the same idempotency_key when retrying.
| Name | Type | Req | Description |
|---|---|---|---|
| archived | boolean | – | – |
| idempotency_key | string | yes | Your id for this operation (8-128 of A-Z a-z 0-9 . _ : -). Reuse it on every retry of the same operation; use a new one for a new operation. |
| name | string | – | – |
| tag_id | string | yes | – |
No output schema declared.
No examples provided.
edit_contacts Edit contacts in bulk ~276
Applies one edit to up to 5000 contacts, as the Contacts page's selection bar does: op add_to_list / remove_from_list (listId), add_tags / remove_tags (tagIds), set_service_category (value residential, commercial, both or null), set_lead_source (value thumbtack, google_lsa, yelp, bark, website_form, google_business_profile, referral, booking_software, direct, web_chat, other or null), set_type (type client, lead, applicant, other), archive, mark_spam (at most 500 for the last three; a type change or spam tags or untags the Quo card when the business's write setting allows). Each contact answers succeeded, skipped (already so) or failed. Pass the same idempotency_key when retrying; every op is safe to repeat.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | yes | Your id for this operation (8-128 of A-Z a-z 0-9 . _ : -). Reuse it on every retry of the same operation; use a new one for a new operation. |
| ids | array | yes | – |
| listId | string | – | – |
| op | string | yes | – |
| tagIds | array | – | – |
| type | string | – | – |
| value | – | – | – |
No output schema declared.
No examples provided.
edit_draft Edit or discard a draft ~175
Edits a draft in a conversation's draft box, as a person typing in it does: body, subject (email), whyNote, isReady, or status 'discarded' to throw it away. Nothing is sent; a person still presses Send. draft_id comes from create_draft or read. Pass the same idempotency_key when retrying.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | – |
| draft_id | string | yes | – |
| idempotency_key | string | yes | Your id for this operation (8-128 of A-Z a-z 0-9 . _ : -). Reuse it on every retry of the same operation; use a new one for a new operation. |
| isReady | boolean | – | – |
| status | string | – | – |
| subject | – | – | – |
| whyNote | – | – | – |
No output schema declared.
No examples provided.
edit_flow Rename a flow or change its description ~144
Changes a flow's name or description, as its editor on the Automations page does. Send only what changes. Its steps and how it starts are set in the editor (how it starts: set_flow_start). flow_id comes from read('flows'). Pass the same idempotency_key when retrying.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| flow_id | string | yes | – |
| idempotency_key | string | yes | Your id for this operation (8-128 of A-Z a-z 0-9 . _ : -). Reuse it on every retry of the same operation; use a new one for a new operation. |
| name | string | – | – |
No output schema declared.
No examples provided.
edit_handbook_article Edit a handbook article ~410
Edits a handbook article as its Edit page does: title, content_md, category, tags, audience, bucket, is_published, exclude_from_suggestions. Send only the fields to change (sop_id from read entity sops); content_md replaces the whole body, so read the article in full (read sops with id) and send all of it with the change in place. Saving supersedes pending suggestions on it. Before adding anything to the handbook, search the sops read entity by the topic (search finds by meaning): when an article already covers it, put the new text into that article (edit_handbook_article with its full content_md, the new lines placed where they belong, or draft_handbook_edit) instead of a new one; create a new article only when none fits, and say which closest article you found and why it did not fit. Audience comes from the person's words: cleaner SOPs, cleaning standards or staff = cleaner; policies, office or VA = va; when the words do not say, ask in one line. Ask which place, in one line naming both, when two places fit the person's words equally well: two articles that both match; a place the person named outright is never a tie. The proposed change is the confirmation, so never ask "should I add this?" first. Pass the same idempotency_key when retrying.
| Name | Type | Req | Description |
|---|---|---|---|
| audience | string | – | – |
| bucket | – | – | – |
| category | – | – | – |
| content_md | string | – | – |
| exclude_from_suggestions | boolean | – | – |
| idempotency_key | string | yes | Your id for this operation (8-128 of A-Z a-z 0-9 . _ : -). Reuse it on every retry of the same operation; use a new one for a new operation. |
| is_published | boolean | – | – |
| sop_id | string | yes | – |
| tags | array | – | – |
| title | string | – | – |
No output schema declared.
No examples provided.
edit_lead_step Change a step in a lead's follow-ups ~266
Changes one step of one lead's follow-ups, as the journey list does. Send one or more of: dueAt (ISO time, or null for the plan's timing; must stay after the step before it), channel ('message', 'email', 'call', 'reply', or null for the plan), removed (true takes it out, false puts it back), keep: true (its custom text is still right after the latest conversation). Or addAfter ('message', 'email', 'call' or 'reply') alone to add a step after it (the new step's id comes back). The step's words are your person's to change in the app. step_id comes from the lead's journey. Pass the same idempotency_key when retrying.
| Name | Type | Req | Description |
|---|---|---|---|
| addAfter | string | – | – |
| channel | – | – | – |
| dueAt | – | – | – |
| idempotency_key | string | yes | Your id for this operation (8-128 of A-Z a-z 0-9 . _ : -). Reuse it on every retry of the same operation; use a new one for a new operation. |
| keep | boolean | – | – |
| removed | boolean | – | – |
| step_id | string | yes | – |
| task_id | string | yes | – |
No output schema declared.
No examples provided.
edit_scanner Edit a Scanner ~285
Changes a Scanner, as its editor on the Scanners page does: any of name, question, inputs, look-again timing, who gets the task, due rule, destination, contact types, enabled. scanner_id comes from read('scanners'). Pass the same idempotency_key when retrying. An owner-level change: Sergio tells the owner after it is made.
| Name | Type | Req | Description |
|---|---|---|---|
| assignee_kind | string | – | – |
| assignee_member_id | – | – | – |
| contact_types | – | – | – |
| destination | string | – | – |
| draft | boolean | – | – |
| due_hours | – | – | – |
| due_rule | string | – | – |
| enabled | boolean | – | – |
| idempotency_key | string | yes | Your id for this operation (8-128 of A-Z a-z 0-9 . _ : -). Reuse it on every retry of the same operation; use a new one for a new operation. |
| inputs | array | – | – |
| look_again_kind | string | – | – |
| look_again_minutes | – | – | – |
| name | string | – | – |
| question | string | – | – |
| reason | string | – | Why you are doing this, in one sentence. The owner sees it in the notice Sergio sends after the change. |
| refinements | array | – | – |
| rollup | boolean | – | – |
| scanner_id | string | yes | – |
No output schema declared.
No examples provided.
edit_staff_member Change a staff member's details ~328
Changes one staff member (staff_id, from read staff_roster or staff_detail) as Save in their staff drawer does. Pass only what changes: employmentType (employee reads Staff, contractor reads Contractor), payRateCents with payRateUnit (hour, visit or percent; null clears), publicBookable (customers can pick them on the booking page), portalBookable (clients can pick them in the portal), payHidden (hide their pay from payroll views), venmo / zelle (tip handles; empty clears). To rename, use add_staff_member with rename_staff_id. Ending someone's employment is done by a person on the staff page. Nothing is sent. For several people, call once per person. Pass the same idempotency_key when retrying. An owner-level change: Sergio tells the owner after it is made.
| Name | Type | Req | Description |
|---|---|---|---|
| employmentType | string | – | – |
| idempotency_key | string | yes | Your id for this operation (8-128 of A-Z a-z 0-9 . _ : -). Reuse it on every retry of the same operation; use a new one for a new operation. |
| payHidden | boolean | – | – |
| payRateCents | – | – | – |
| payRateUnit | – | – | – |
| portalBookable | boolean | – | – |
| publicBookable | boolean | – | – |
| reason | string | – | Why you are doing this, in one sentence. The owner sees it in the notice Sergio sends after the change. |
| staff_id | string | yes | – |
| venmo | – | – | – |
| zelle | – | – | – |
No output schema declared.
No examples provided.
events_ack Acknowledge events ~55
Stores `cursor` (a next_cursor you received) as this seat's high-water mark, so events_list with no cursor resumes after it. It only moves forward; an older cursor changes nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | yes | – |
No output schema declared.
No examples provided.
events_list Pull events ~144
Returns the next events for this seat, oldest first, after `cursor` (omit it to continue from your last ack). Each event names an arrival by id (a text, email, call, or booking change); fetch its detail with read(). Delivery is at-least-once: dedupe on event_id. Pass next_cursor to the next call, and ack it with events_ack once you have processed the page. An error cursor_expired (410) means events behind your cursor were trimmed (7-day retention or backlog cap): resync through read(), then events_subscribe with restart: true.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
How do I install the Sergio by Serviche MCP server?
Sergio by Serviche is a hosted endpoint at https://sergio.serviche.com/api/agent/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · sergio.serviche.com
claude mcp add --transport http com-serviche-sergio 'https://sergio.serviche.com/api/agent/mcp'
What is the Sergio by Serviche MCP server?
Sergio by Serviche is an MCP server listed in the public MCP registry as com.serviche/sergio. Make sure nothing falls through the cracks in your cleaning business, even when you're not watching. This page covers its hosted endpoint (https://sergio.serviche.com/api/agent/mcp).
Is the Sergio by Serviche MCP server safe to use?
Sergio by Serviche scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Sergio by Serviche MCP server expose?
Sergio by Serviche exposes 104 tools: whoami, catalog, report_feedback, events_subscribe, events_list, and 99 more. Their descriptions and schemas cost roughly 23,695 tokens of context every time the server is loaded.
Does the Sergio by Serviche MCP server require authentication?
Yes. Sergio by Serviche asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Sergio by Serviche MCP server still maintained?
Sergio by Serviche is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Sergio by Serviche MCP server?
VerifyMCP ran 13 checks on Sergio by Serviche, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.