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 →
events_subscribe Subscribe to events ~207
Create or update this seat's one event subscription. inputs: which arrivals (omit for all: text_in, text_out, email_in, email_out, call_answered, call_missed, voicemail, booking_created, booking_changed, booking_cancelled, staff_clocked_in, staff_not_clocked_in, job_finished, visit_unconfirmed). contact_types: only arrivals for these contact types. A field you omit keeps its current value, so {paused:true} pauses without touching the filter; pass inputs:null or contact_types:null to go back to all. paused: true stops delivery without losing the cursor, paused: false resumes. restart: true moves your position to now and clears your ack (the resync after cursor_expired, once you have re-read current state). Delivery starts at the moment you first subscribe. Repeating the same call changes nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_types | – | – | – |
| inputs | – | – | – |
| paused | boolean | – | – |
| restart | boolean | – | – |
No output schema declared.
No examples provided.
findClientByIdentifier ~91
Look up a client ID by a single identifier (phone or email). Returns the client ID or null. Simpler than resolveClient. No creation, no merge. Use for a quick check: "is this phone number already a client?".
| Name | Type | Req | Description |
|---|---|---|---|
| type | string | yes | Identifier type: "phone" or "email". |
| value | string | yes | The identifier value (phone number or email address). |
No output schema declared.
No examples provided.
hold_follow_ups Hold automatic follow-ups ~145
Puts a lap's automatic follow-ups on hold, as its Hold follow-ups switch does: lead follow-ups, a feedback check-in and a review request all obey the one hold. No step goes out on its own; each is drafted for a person. Turning them back on is your person's, in the app. 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. |
| task_id | string | yes | – |
No output schema declared.
No examples provided.
hold_lead_follow_ups Hold automatic follow-ups ~147
Puts a lap's automatic follow-ups on hold, as its Hold follow-ups switch does: lead follow-ups, a feedback check-in and a review request all obey the one hold. No step goes out on its own; each is drafted for a person. Turning them back on is your person's, in the app. 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. |
| task_id | string | yes | – |
No output schema declared.
No examples provided.
link_conversation_to_client Link a conversation to a contact ~145
Links a conversation to a contact, as the inbox's Link to a contact does: if the contact already has a one-to-one thread, it is folded into this one, and an email thread's address is saved to the contact. Sergio learns the correction for later emails. Pass the same idempotency_key when retrying.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | string | yes | – |
| 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.
log_call Log a call to a contact ~266
Logs a phone call the team made outside the phone system (a cell phone, a desk phone) on a contact, as the contact pane's Log a call does. outcome: answered (someone picked up), no_answer, or voicemail (you left one). Optional note (what was said) and at (ISO time the call happened; now when left out, never in the future). The call joins the contact's history and moves their Lead status: an answered call reads In discussion; no answer or a voicemail, with nothing back from them, reads Contacted (a quote, a booking or a status a person set still wins). The answer carries leadStatus, where they stand now. Calls made through the connected phone system are recorded already; do not log those. Nothing is sent. Pass the same idempotency_key when retrying; a repeat returns the original call.
| Name | Type | Req | Description |
|---|---|---|---|
| at | string | – | – |
| 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. |
| note | string | – | – |
| outcome | string | yes | – |
No output schema declared.
No examples provided.
log_handbook_question Log a handbook question ~152
Logs a question the handbook does not answer, as Handbook's Ask a question does (optional sop_id of the article it is about, asked_by_name, channel app, sms, call or in-person). Pass the same idempotency_key when retrying; a repeat returns the same question.
| Name | Type | Req | Description |
|---|---|---|---|
| asked_by_name | string | – | – |
| channel | 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. |
| question | string | yes | – |
| sop_id | string | – | – |
No output schema declared.
No examples provided.
merge_conversations Merge two conversations ~135
Moves everything in conversation_id (messages, calls, emails, tasks) into target_conversation_id and removes the empty one, as the thread menu's Merge does. It cannot be split back. Pass the same idempotency_key when retrying; the same pair merges once.
| 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. |
| target_conversation_id | string | yes | – |
No output schema declared.
No examples provided.
move_address_to_contact Move an email address or number to the right contact ~162
Says who an email address or phone number on a contact really is, as an email's This is someone else does: pass exactly one of to_client_id, new_contact_name, or none=true. Its emails, texts and calls on that contact move with it and its next message lands on the new owner. Pass the same idempotency_key when retrying.
| 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. |
| kind | string | yes | – |
| to | – | yes | – |
| value | string | yes | – |
No output schema declared.
No examples provided.
move_lead_journey Move a lead to another journey ~132
Moves a lead to another follow-up journey (segmentId, as Settings > Lead follow-ups names them: read the lead program), at the same place in the sequence, as the lead's journey tag does. 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. |
| segmentId | string | yes | – |
| task_id | string | yes | – |
No output schema declared.
No examples provided.
open_conversation_by_phone Open a conversation for a phone number ~113
Opens (or finds) the one conversation for a phone number nobody is saved under, as the inbox search's Text <number> does. Nothing is sent. 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. |
| phone | string | yes | – |
No output schema declared.
No examples provided.
pin_client_note Pin or unpin a client note ~140
Pins a note to the top of a contact's card (pinned: true) or unpins it (false), as the note's pin on the contact card does. noteId comes from read (entity client notes). Pass the same idempotency_key when retrying.
| 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 | – |
| pinned | boolean | yes | – |
No output schema declared.
No examples provided.
query ~719
Run a read-only SQL SELECT over the business database and get rows back. It is the FALLBACK, not the first move: when a read(entity) answers the question (leads, clients, conversations, bookings and the rest of read's catalog), use read, which carries the business's own definitions (e.g. open leads = read lead_pursuits active:true) that raw tables do not. Use query only when read cannot express the question (a count, a GROUP BY, a JOIN across tables, filtering on a column read() does not expose, a discount a customer used, an arbitrary aggregate). SCHEMA: query the org-scoped view schema `soul_read` (NOT public). Every table you can read is a view there, already filtered to THIS business. You never write a WHERE organization_id clause and never pass an org id. START with `client_timeline` for any question about one person or booking: every SMS, call (with AI summary), email, booking and human action in one feed (columns: channel, direction, actor, at, text, ai_summary, sentiment, category, client_id, conversation_id, booking_id). Filter client_id, ORDER BY at DESC, LIMIT. Read `SELECT * FROM schema_notes` once for column semantics (event-time columns, value meanings, columns that lie: e.g. use sent_at not created_at; contact_type = client means a real client). Never guess a column name: before you name a column of any other table you have not listed in this conversation, list THAT table's columns first (one table, never the whole schema): `SELECT column_name FROM information_schema.columns WHERE table_schema='soul_read' AND table_name='<table>'`. Reference tables unqualified (e.g. `FROM bookings`). Search_path is already soul_read. RULES: exactly ONE SELECT statement (a second statement, SET, INSERT/UPDATE/DELETE or DDL is refused). Results cap at 100 rows; the response is {rows, returned, truncated}. When truncated is true, add your OWN aggregation (COUNT/GROUP BY) or a tighter WHERE rather than paging blindly. Dates are stored as the business's local calendar; co…
| Name | Type | Req | Description |
|---|---|---|---|
| sql | string | yes | A single read-only SQL SELECT over the soul_read schema, e.g. "SELECT status, count(*) FROM bookings WHERE scheduled_date BETWEEN '2026-07-01' AND '2026-07-31' GROUP BY status". |
No output schema declared.
No examples provided.
read ~1,485
Read ANYTHING about the business: read(entity, filters). ENTITIES (key: purpose [main filters]): conversations: The inbox list of conversations [status, from, to, needs_reply, conversation_id, ...] | conversation_transcript: A client's whole history in one timeline [conversation_id, client_ref, from, to, search] | communications: Every text, email and call across the business in ONE read [from, to, direction, channel, contact_type, ...] | calls: Call log [conversation_id, client_ref, from, to, direction, ...] | bookings: Bookings by status/date/client/cleaner [status, frequency, from, to, date_axis, ...] | booking_time_logs: Cleaner clock-in/out records as a SET read [from, to, staff, client_ref, booking_id, ...] | booking_notes: Tiered booking notes + the flat booking note [booking_id] | clients: Look up contacts by id [id, name, name_words, phone, email, ...] | contact_groups: The business's live Contacts tags and lists, as the Contacts page's side nav shows them [kind] | client_standing: Visit count + last visit per client, with the client name [client_ref, client_ids] | client_case_file: Full context for a client's thread [conversation_id, client_ref, question, as_of] | owner_directives: Standing asks the owner gave the team in the team channel [status, from, to] | tasks: Tasks [status, task_id, client_ref, conversation_id, flow, ...] | cockpit_queue: The Sergio cockpit / Needs-Attention queue | activity_log: Audit trail of changes [days, from, to, search, actor, ...] | scheduling_decisions: The scheduling decision log [booking_id, days] | chat_turns: Each Sergio chat turn's AI cost and time, newest first, read from the AI usage log [turn_id, days] | staff_roster: The cleaner/staff roster, counted in code | staff_detail: Detail for one staff member [staff, kind, from, to] | staff_events: Every logged staff event org-wide [from, to, kind, staff, sentiment, ...] | client_checkins: Every client check-in / feedback record org-wide [from, to, client_ref, staff, outc…
| Name | Type | Req | Description |
|---|---|---|---|
| entity | string | yes | The entity to read, or 'catalog' to list what you can read. |
| filters | object | – | Entity-specific filters (see read('catalog')). An organization id is never a filter. |
| options | object | – | Paging + projection. |
No output schema declared.
No examples provided.
read_company_document Have Sergio read an uploaded document ~134
Has Sergio read one uploaded company document (document_id from read entity company_documents) for Flows and recurring tasks it describes, as the setup guide's Your SOPs step does. Creates nothing; returns the suggestions (decide each with decide_company_document_suggestion). A document already read returns its list without a second read.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
record_staff_event Record a warning, kudos or note for a field worker ~236
Adds one entry to a field worker's (staff_id) staff log and their attendance and feedback counts: kind warning (a conduct warning), kudos, note, client_feedback (with sentiment), or sick, late, no_show. A sick day, late arrival or no-show that cancelled or moved a visit is recorded by cancelling or reassigning that booking with the cleaner's reason instead, so do not record those twice. occurredOn is YYYY-MM-DD (default today); body is the detail in plain words. Nothing is sent to the worker. Pass the same idempotency_key when retrying.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | – |
| bookingId | string | – | – |
| clientId | 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. |
| kind | string | yes | – |
| occurredOn | string | – | – |
| sentiment | string | – | – |
| staff_id | string | yes | – |
No output schema declared.
No examples provided.
record_tools_access Record the business's other tools ~209
Records the tools the business uses today and whether Serviche was given access to each, as Get started's Your tools step does: action pick (tools: [{ id } or { name }]), none, mark (tool, provided, note) or unmark (tool). Nothing leaves Sergio. Pass the same idempotency_key when retrying. An owner-level change: Sergio tells the owner after it is made.
| Name | Type | Req | Description |
|---|---|---|---|
| action | 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. |
| note | string | – | – |
| provided | boolean | – | – |
| reason | string | – | Why you are doing this, in one sentence. The owner sees it in the notice Sergio sends after the change. |
| tool | string | – | – |
| tools | array | – | – |
No output schema declared.
No examples provided.
redraft_lead_step Redraft a lead's upcoming text step ~178
Rewrites the text of a lead's upcoming step that a person sends, from the conversation so far, as the journey's Update draft does (one AI draft, billed like the composer's Draft). Refused for a call step, a step Sergio sends on its own, or a step already past. Nothing is sent. task_id is the lead (read entity tasks); step_id is the step's id from the lead's journey. 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. |
| step_id | string | yes | – |
| task_id | string | yes | – |
No output schema declared.
No examples provided.
remove_conversation_flow Remove a flow from a conversation ~130
Takes one flow off a conversation, as the flow chip's Remove does; its open step tasks are removed. conversationFlowId names the flow. reason is optional. Pass the same idempotency_key when retrying.
| Name | Type | Req | Description |
|---|---|---|---|
| conversationFlowId | string | yes | – |
| 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. |
| reason | string | – | – |
No output schema declared.
No examples provided.
remove_staff_scheduling_rule Remove a field worker's scheduling rule ~177
Removes one plain-English scheduling rule (ruleId, from add_staff_scheduling_rule or read staff_scheduling_rules) from a field worker (staff_id), as remove on their Rules tab does. Answers the rules left. 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. |
| ruleId | string | yes | – |
| staff_id | string | yes | – |
No output schema declared.
No examples provided.
reopen_task Reopen a task ~161
Reopens a done or dismissed task, clearing its completion. reopen_reason says briefly why (required, it rides the audit row). A lead follow-up (pursuit) task is refused: reopening it can queue a message, so a person does it. 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. |
| reopen_reason | string | yes | – |
| task_id | string | yes | – |
No output schema declared.
No examples provided.
report_feedback Report a bug or idea to the Sergio team ~195
Files a bug report or feature request with the Sergio team. It lands in the team's one Feedback inbox, the same place the in-app help bubble's reports go, tagged with this agent seat, and the team is notified the moment it is filed. There is no other feedback channel to try. Check with your user first unless they have already told you that you may report without asking; afterwards, tell your user in one line what you sent. Never include passwords, API keys, or card numbers. Optional hypothesis: in plain words, which tool call or page failed (with the arguments you sent) and what you think is wrong and how you would fix it. Prose only, no code or commands; the team treats it as a lead to verify, not a patch to apply.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | – |
| hypothesis | string | – | – |
| kind | string | yes | – |
| pageUrl | string | – | – |
No output schema declared.
No examples provided.
review_cleaner_roster Sort a cleaner name from bookings ~163
Sorts one cleaner name found on bookings, as the Get started card's Review your cleaner roster does: action add (adds them to the roster and links their past jobs), not_staff (this name is not one of our cleaners), or link (it is staffId under another spelling; links their past jobs). Nothing is sent. Pass the same idempotency_key when retrying.
| Name | Type | Req | Description |
|---|---|---|---|
| action | 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 | yes | – |
| staffId | string | – | – |
No output schema declared.
No examples provided.
review_handbook_edit Approve or reject a drafted article edit ~157
Approves (the draft becomes the article's text) or rejects a pending drafted version of an article (version_id from draft_handbook_edit or read entity sop_versions), as the article's Approve and Reject do. The same decision again answers success; the other decision on a reviewed version is refused. Pass the same idempotency_key when retrying.
| Name | Type | Req | Description |
|---|---|---|---|
| action | 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. |
| sop_id | string | yes | – |
| versionId | string | yes | – |
No output schema declared.
No examples provided.
review_import_mapping Approve or discard a spreadsheet's columns ~200
Settles an import waiting at the column review, as its review card does: decision approve (the import runs with the confident columns plus keepFields; keepValues and assignValues teach status words) or discard (nothing is written). Pass the same idempotency_key when retrying. An owner-level change: Sergio tells the owner after it is made.
| Name | Type | Req | Description |
|---|---|---|---|
| assignValues | array | – | – |
| decision | 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. |
| jobId | string | yes | – |
| keepFields | array | – | – |
| keepValues | array | – | – |
| 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.
run_suggestion_now Run a Sergio card now ~179
Runs a Sergio card's move now, as the card's "Run this now" does. action_type is the card's action type (for example create_draft). A move that sends, moves money, opens to the public or grants access is refused with where the owner does it; a move that writes to an outside system (booking changes) is not lent to agents yet. Pass the same idempotency_key when retrying; the move keys on the card, so it never runs twice.
| Name | Type | Req | Description |
|---|---|---|---|
| action_type | 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. |
| suggestion_id | string | yes | – |
No output schema declared.
No examples provided.
send_campaign_messages Send a campaign's ready messages (after your person confirms) ~246
Sends a started campaign's drafted messages that are ready, on your person's order, as Send in its Ready to send does, as Manual sends under the business's Sending setting, spread over the campaign's send window. First call without confirm_token: nothing is sent; you get a preview (each person and the exact finished text they get, up to 50 at a time) and a confirm_token. Show your person the preview word for word, and only after they say yes, call again with the same arguments and the SAME idempotency_key, plus confirm_token: exactly the messages shown are sent. If Sending is switched off the answer says so with the link; only the owner turns it on, in Sergio. Never send something nobody asked for.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | – |
| confirm_token | string | – | From the preview, after your person said yes. Leave it out to get the preview. |
| 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.
send_email Send an email (after your person confirms) ~223
Emails a client from the business mailbox on your person's order, as a Manual send under the business's Sending setting. First call without confirm_token: nothing is sent; you get a preview (to, subject and the exact text) and a confirm_token. Show your person the preview word for word, and only after they say yes, call again with the same arguments and the SAME idempotency_key, plus confirm_token. replyToEmailId threads it as a reply to that inbound email.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | – |
| confirm_token | string | – | From the preview, after your person said yes. Leave it out to get the preview. |
| 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. |
| replyToEmailId | string | – | – |
| subject | string | yes | – |
| to | string | yes | – |
No output schema declared.
No examples provided.
send_text Send a text (after your person confirms) ~324
Texts a client or teammate on your person's order, from the business number, as a Manual send under the business's Sending setting. Use it whenever your person asks you to text someone now, with their words or words you wrote for them ("text today's cleaners about the weather"); create_draft leaves it for someone else to send later. First call without confirm_token: nothing is sent; you get a preview (who it goes to and the exact text) and a confirm_token. Show your person the preview word for word, and only after they say yes, call again with the same arguments and the SAME idempotency_key, plus confirm_token. Several people: one preview each, shown together, one yes covers the ones they approve. Never send something nobody asked for, or while nobody is watching; that is a draft (create_draft). Give conversationId (one-to-one: to defaults to the conversation's number); for a cleaner or contact without one, read clients (contact_type 'staff' for cleaners) for the phone, then open_conversation_by_phone.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | – |
| confirm_token | string | – | From the preview, after your person said yes. Leave it out to get the preview. |
| conversationId | 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. |
| to | string | – | – |
No output schema declared.
No examples provided.
set_conversation_reminder Set a reminder on a conversation ~171
Adds a reminder on a conversation, as the thread's bell does: remind_at (ISO 8601) and an optional note become a task due then. hide_until_due: true also tucks the thread away until the reminder is due (a reply from the person brings it back). Pass the same idempotency_key when retrying; a repeat returns the first reminder.
| Name | Type | Req | Description |
|---|---|---|---|
| conversation_id | string | yes | – |
| hide_until_due | 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. |
| note | string | – | – |
| remind_at | string | yes | – |
No output schema declared.
No examples provided.
set_conversation_status Mark a conversation done, or reopen it ~163
Marks a thread done (status resolved) or reopens it (status new), as the inbox's Done and Reopen do; the Quo inbox follows when the business's write setting allows. A thread that still owes the customer a reply is refused unless replyOwedOverride is true (say why to your person first). 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. |
| replyOwedOverride | boolean | – | – |
| status | string | yes | – |
No output schema declared.
No examples provided.
set_flow_archived Archive or un-archive a flow ~148
Archives a flow as its Archive on the Automations page does (archived true): it leaves the flow pickers and the router but is kept, and runs in progress are unaffected. archived false un-archives it. flow_id comes from read('flows'); archive several by calling once per flow. Pass the same idempotency_key when retrying.
| Name | Type | Req | Description |
|---|---|---|---|
| archived | boolean | yes | – |
| 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. |
No output schema declared.
No examples provided.
set_flow_on Turn a flow on or off ~139
Turns a flow on or off, as its On switch on the Automations page does. Turning it on runs the same publish check (a refusal says what is missing); turning it off ends its runs in progress. flow_id comes from read('flows'). Pass the same idempotency_key when retrying.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| is_active | boolean | yes | – |
No output schema declared.
No examples provided.
set_flow_start Change how a flow starts ~578
Changes how one of this business's flows starts ("Starts when" in Automations) and whether it is on, exactly as the Automations editor's save does. starts_when "contact" means "You add it to a contact": nothing starts the flow by itself. Any other value starts it automatically on that booking event. Switching a start off ("contact") or turning a flow off (active false; its runs in progress end) is open to this seat. Starting a flow on an event or turning a flow on is owner-level: available only when the owner turned on "Let this agent change owner settings" for this seat; the owner is told about each such change. A flow that starts on every upcoming job (starts_when_words says so) turns on only after a person confirms how many jobs it covers, which this tool cannot do: it comes back refused with that count, and the owner turns it on in Automations. Picking a booking event here makes a flow start only on jobs from then on. read("flows") shows each flow and its current start. Events: booking_created (New job booked); booking_changed (Job changed); booking_cancelled (Job cancelled); staff_clocked_in (Cleaner clocked in); staff_not_clocked_in (Cleaner hasn't clocked in); job_finished (Job finished); visit_unconfirmed (Past job not marked done in the booking platform); card_declined (Card declined); review_received (Review received); review_low_rating (Low-star Google review); staff_on_the_way (Cleaner tapped On the way); staff_clocked_out (Cleaner clocked out); staff_running_late (Cleaner says they are running late); staff_not_on_the_way (Cleaner hasn't tapped On the way); staff_not_clocked_out (Cleaner hasn't clocked out); staff_clocked_in_twice (Cleaner clocked in on two jobs at once); staff_schedule_request (Cleaner asked to change their schedule). Pass the same idempotency_key when retrying; a repeat returns the original result.
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean | – | true turns the flow on, false turns it off. |
| first_booking_only | boolean | – | With an event: true starts it only on a client's first booking. Omitted keeps the current choice. |
| flow_id | string | yes | The flow id (from read("flows")). |
| 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. |
| justification | string | – | Optional: why the business wants this. Shown to the owner with an owner-level change. |
| starts_when | string | – | "contact" for by hand only, or the booking event that starts it. |
No output schema declared.
No examples provided.
set_handbook_toolshed_sharing Keep an article out of the Toolshed, or share it again ~180
Excludes one handbook article from Toolshed sharing (its shared rules are withdrawn) or includes it again, as the article's Toolshed sharing line does. Shared rules are generalized so no one can tell which business they came from. Pass the same idempotency_key when retrying. An owner-level change: Sergio tells the owner after it is made.
| Name | Type | Req | Description |
|---|---|---|---|
| excluded | boolean | 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. |
| sopId | string | yes | – |
No output schema declared.
No examples provided.
set_lead_outcome Record a lead's outcome ~374
Records what happened with a lead, as the lead card's Close menu and taps do. tap: quoted (they have a price); booked (closes it won, on the booking when one for them exists, else on your word); confirmed_booked (the same as booked); call_back_on (date YYYY-MM-DD, or at as an ISO time: pauses the lead until then; the pause ends by itself on that date, when a message goes either way, or when a step's date is changed); not_interested (lost; lostReason is one of "Timing / availability", "Price", "Went elsewhere / not needed", "Out of scope / area", or their own words for Other; a lead that just went quiet is not lost, it goes cold on its own); keep_pursuing; acknowledge_reply (their last message needs no answer: follow-ups resume); tracked_by_mistake; dismiss_plan; replied_on_site (stepKey: the Reply step answered on a lead site); undo_close (reopens a lead Sergio closed on its own, so the same evidence never closes it again; a contact made not-a-lead becomes a lead again, and Quo follows when the business's write setting allows). Nothing is sent. Pass the same idempotency_key when retrying.
| Name | Type | Req | Description |
|---|---|---|---|
| at | string | – | – |
| 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. |
| lostReason | string | – | – |
| stepKey | string | – | – |
| tap | string | yes | – |
| task_id | string | yes | – |
No output schema declared.
No examples provided.
set_scanner_on Turn a Scanner on or off ~178
Turns one of the business's Scanners on or off, as the On switch in Automations > Scanners does. A Scanner is only ever on or off (never a trial mode). 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 |
|---|---|---|---|
| enabled | boolean | 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. |
| scanner_id | string | yes | – |
No output schema declared.
No examples provided.
set_staff_availability Set a field worker's availability for a date ~233
Sets one field worker's availability for a date, or a date range (end_date, up to 92 days): a day off (day_off: true), one shift (available_from + available_until, HH:MM), or split shifts (windows). It replaces that day's override; hours equal to the weekly default clear it. Nothing is sent to anyone. Returns the override ids and any booking conflicts the change creates, for a person to resolve. Pass the same idempotency_key when retrying; a repeat returns the original override ids.
| Name | Type | Req | Description |
|---|---|---|---|
| available_from | string | – | – |
| available_until | string | – | – |
| cleaner_name | string | yes | – |
| date | string | yes | – |
| day_off | boolean | – | – |
| end_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. |
| reason | string | – | – |
| windows | array | – | – |
No output schema declared.
No examples provided.
set_staff_weekly_hours Save a field worker's weekly hours or details ~243
Replaces the regular weekly hours of the workers named in staffNames with exactly the windows in entries (day_of_week 0 = Sunday to 6 = Saturday, HH:MM times; several windows a day allowed; a named worker with no entries has no regular hours). Workers not in staffNames are untouched. Omit entries to leave hours alone and only save profiles (the worker's details: email, phone, allergies, and venmo / zelle, which change only for a seat allowed to change payment handles). For one date only, use set_staff_availability. If the new hours no longer cover a worker's upcoming Sergio visits, those visits are released and a task is filed for a person. Nothing is sent. Pass the same idempotency_key when retrying.
| Name | Type | Req | Description |
|---|---|---|---|
| entries | array | – | – |
| 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. |
| profiles | array | – | – |
| staffNames | array | yes | – |
No output schema declared.
No examples provided.
skip_task Dismiss a task as not needed ~140
Dismisses a task as not needed (terminal, distinct from done). A client check-in needs a skip_reason. 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 | – | – |
| skip_reason | string | yes | – |
| task_id | string | yes | – |
No output schema declared.
No examples provided.
snooze_conversation Mute a conversation for a few minutes ~166
Mutes a conversation until snoozed_until (ISO 8601, in the future), at most 10 minutes from now (a later time is cut to 10 minutes), as the inbox's Mute does while someone is on a call. note is optional. For a later follow-up, use set_conversation_reminder. 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. |
| note | string | – | – |
| snoozed_until | string | yes | – |
No output schema declared.
No examples provided.
snooze_task Move a task's due time ~142
Moves a task's due time (ISO 8601 with offset). A flow-step task shifts its later steps by the same gap, as in the app. 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 |
|---|---|---|---|
| due_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. |
| task_id | string | yes | – |
No output schema declared.
No examples provided.
start_campaign Start a campaign (after your person confirms) ~279
Starts a draft or paused campaign on your person's order, as Start campaign does: it enrolls the people waiting and drafts their first message; starting sends nothing by itself. First call without confirm_token: nothing changes; you get a preview (every message's exact words, how many people it reaches now, the audience rules, and whether the business's Sending lets a person's messages go out) and a confirm_token. Show your person the preview word for word, and only after they say yes, call again with the same arguments and the SAME idempotency_key, plus confirm_token. If the preview says Sending is switched off, tell your person that plainly with the link; only the owner turns it on, in Sergio, and you never change it. A campaign with a message Sergio sends on its own is the owner's to start, in the app. To send the drafted messages once it has started, use send_campaign_messages.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | – |
| confirm_token | string | – | From the preview, after your person said yes. Leave it out to get the preview. |
| 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.
start_conversation_flow Start a flow on a conversation ~131
Starts a flow on a conversation, as the thread's flow picker does: flowId names an active flow (read entity flows); its steps become tasks with deadlines. label is optional. Pass the same idempotency_key when retrying.
| Name | Type | Req | Description |
|---|---|---|---|
| conversation_id | string | yes | – |
| flowId | 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. |
| label | – | – | – |
No output schema declared.
No examples provided.
start_group_text Open a group text thread ~142
Opens the one group text thread for 2 to 9 contacts who each have a phone, as the inbox's New conversation with several people checked does (an existing group for the same people is reused). Nothing is sent; texting it is send_conversational_message, which shows your person the words first. Pass the same idempotency_key when retrying.
| Name | Type | Req | Description |
|---|---|---|---|
| clientIds | array | 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.
start_history_import Import message history from a connected inbox ~163
Starts importing the past messages of a connected inbox into Sergio, as Import history on Data sources does: source openphone (Quo) or gmail, or transcripts; days back (default 90). The account must already be connected (connecting is the owner's, in Settings). A second start while one is running returns that job; it carries on in the background. Nothing is sent. Pass the same idempotency_key when retrying.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
| 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. |
| source | string | yes | – |
No output schema declared.
No examples provided.
start_spreadsheet_import Start an uploaded spreadsheet's import ~127
Starts the import of a spreadsheet uploaded with upload_spreadsheet, as Start in the import drawer does: Sergio checks its columns; a confident mapping imports, an uncertain one answers status needs_review and waits for review_import_mapping. 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. |
| jobId | string | yes | – |
No output schema declared.
No examples provided.
track_conversation_as_lead Track a conversation as a new lead ~164
Opens a lead for this thread's contact, as the thread header's Track this as a new lead does, for a customer asking about new work. request is what they asked for, in a line. Refused when lead follow-up is off, the thread has no contact, or the contact is staff, an applicant or spam. Pass the same idempotency_key when retrying.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | 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. |
| request | string | – | – |
No output schema declared.
No examples provided.
unsnooze_conversation Unmute a conversation ~97
Ends a conversation's mute now, as the inbox's Unmute 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.
update_payroll_settings Change payroll settings ~203
Changes one payroll setting per call, as Payroll settings on the staff page does: providerPayFallbackPct (0 to 1), providerPayDefault ({ unit: visit or hour, cents }), or payHoursFrom (booked or approved_time_logs). Staff pay settings only; no money moves. 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. |
| payHoursFrom | string | – | – |
| providerPayDefault | object | – | – |
| providerPayFallbackPct | number | – | – |
| 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.
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.