Assistable MCP server

• Registry nameai.assistable/assistableverified in the MCP registry

The registry name sits under assistable.ai. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-29
• Tools20
• Server calls itselfassistable
• Server version0.4.0
• Protocol version2025-06-18

On 2026-10-29 the server answered initialize and tools/list without a sign-in. First answer in 171 ms.

• Whether its tools do the product's job has not been judged yet.
• Checked on 4 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 4 so far
• Answeredmeasuring4 of the 7 daily checks it takes to print a share
• Median first answer180 ms
• Space in an agent's context≈ 2,851 tokensthe definitions of all its tools (16), which an agent carries on every turn
• Tool definitionsB · 84 of 100
• Typed results0 of 16 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 15 of 16

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• search_tools

  Search Assistable's registered MCP tools by the task the user wants to do. Returns up to 5 exact tool definitions with JSON input schemas and annotations. Use this first when you need to choose a tool; the result is not authorization to…

• assistants_list

  List assistants in a subaccount (excludes archived by default). Note: voice_settings and platform_tools are returned only by assistants_get, not in the list.

• assistants_get

  Fetch an assistant's full configuration by ID. The response includes voice_settings (greeting mode, opening messages, voicemail) and platform_tools (attached platform-catalog tool names).

• assistants_create

  Create an assistant. Required: subAccountId, name. Optional config blocks (llmConfig, voiceConfig, chatConfig) mirror the dashboard create dialog. voice_settings configures call greeting mode, opening messages, and voicemail behavior…

• assistants_update

  Patch an assistant. Only supplied fields change; nested config blocks are upserted. voice_settings updates call greeting mode, opening messages, and voicemail behavior; platform_tools declaratively replaces the attached platform-catalog…

• assistants_archive

  Archive (soft-delete) an assistant.

• tools_list

  List tools visible to a subaccount. Pass includePrebuilt=false for only custom tools.

• tools_get

  Fetch a tool's full configuration.

• tools_create_custom

  Create a custom tool (toolType=CUSTOM). Name must match /^[a-zA-Z0-9_-]+$/ and be unique in the subaccount.

• tools_update

  Patch a custom tool. Supplying parameters/headers replaces those rows; omit to leave them.

• tools_delete

  Soft-delete a custom tool.

• contacts_list

  List contacts in a subaccount. meta.total is the number of matching contacts, so use it to answer how many contacts there are.

• contacts_get

  Fetch a contact by ID.

• conversations_list

  List conversations in a subaccount.

• appointments_list

  List appointments in a subaccount within an optional date range.

• calls_get

  Fetch a call (status, recording, transcript) by ID.

• assistable_connect

  Only when you have no Assistable API key: start signing in. Returns verification_uri_complete and user_code; send the person that link (or the code) so they can sign in to Assistable, pick the account and approve. Then call…

• assistable_connect_finish

  Check an assistable_connect sign-in. error.code authorization_pending means the person has not approved yet: wait interval seconds and call again. On approval it returns api_key once: use it as the Authorization: Bearer header for this…

• assistable_signup

  Only when the person has no Assistable account (assistable_connect is for people who have one): start one with their email and name, and area_code or city/state for their local number. Emails them a 6-digit code; ask them for it, then…

• assistable_signup_finish

  Finish assistable_signup with signup_id, the code the person read to you, and a strong password you generate and keep in your vault (it is their dashboard login). Returns api_key once: send it as the Authorization: Bearer header to this…