HAL
REMOTE · API.CHATWITHHAL.COM
Customer conversations, help center, CRM, deals and email campaigns on HAL (chatwithhal.com).
Available components
Last scanned (2 hours ago)
Scores higher than 66% of remote servers
Reachable. Last reached 5 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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 15389 tokens (~113/item across 136 items; 136 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 Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage92
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 77% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 21 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "reply_to_conversation" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 137 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
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.
- 5 Nov 26 +1
- New tool “delete_company” functional
- New tool “delete_contact” functional
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 30 Oct 26 73
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://api.chatwithhal.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=chatwithhal.com | CN=WE1,O=Google Trust Services,C=US | 28 Sept 2026 | 27 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 6eed566668d301370e6de7fc568a6574 |
| SANs: chatwithhal.com, *.chatwithhal.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.chatwithhal.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| chatwithhal.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'none'; frame-ancestors 'none'; base-uri 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.chatwithhal.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.chatwithhal.com/mcp | HTTPS enforced | 301 | https://api.chatwithhal.com/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 →
send_broadcast_now ~158
IMMEDIATELY sends this broadcast to its whole live audience - a real, irreversible email blast to real contacts, not a test. You MUST call preview_broadcast_audience first and pass its exact `count` as confirm_recipient_count; a mismatch is refused. Call get_broadcast_readiness first too: sends with blocking deliverability checks are refused. Only call this after the user has explicitly confirmed they want to send to that many recipients right now.
| Name | Type | Req | Description |
|---|---|---|---|
| broadcast_id | string | yes | – |
| confirm_recipient_count | integer | yes | Must exactly equal the current preview_broadcast_audience count |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
No output schema declared.
No examples provided.
send_test_broadcast_email ~120
Send a test of a broadcast email to an account user email address only (never to real contacts).
| Name | Type | Req | Description |
|---|---|---|---|
| broadcast_id | string | yes | – |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
| sample_contact_id | string | – | Contact to source sample merge fields from |
| to_email | string | yes | Recipient email. Must belong to a user on this account. |
| variant | string | – | A/B test variant to send (default a, the main email) |
No output schema declared.
No examples provided.
send_test_email_campaign ~88
Send a test email for an existing email campaign to an account user email address only.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | – |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
| sample_context | object | – | – |
| to_email | string | yes | Recipient email. Must belong to a user on this account. |
No output schema declared.
No examples provided.
send_test_email_template ~143
Send a workflow email template test to an account user email address only.
| Name | Type | Req | Description |
|---|---|---|---|
| blocks | array | – | Shortcut for template_document.blocks |
| preheader | string | – | Email preheader |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
| sample_context | object | – | – |
| subject | string | – | Email subject |
| template_document | object | – | Structured email document |
| template_id | string | – | – |
| theme | object | – | – |
| to_email | string | yes | Recipient email. Must belong to a user on this account. |
| workflow_name | string | – | – |
No output schema declared.
No examples provided.
send_test_workflow_email ~112
Send a real test email for one send_email node in a workflow to an account user email address only.
| Name | Type | Req | Description |
|---|---|---|---|
| node_id | string | – | Required if the workflow has more than one send_email node |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
| sample_context | object | – | – |
| to_email | string | yes | Recipient email. Must belong to a user on this account. |
| workflow_id | string | yes | – |
No output schema declared.
No examples provided.
set_deal_contact ~71
Add a contact to a deal, or change their role on it
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | string | yes | – |
| deal_id | string | yes | – |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
| role | – | – | – |
No output schema declared.
No examples provided.
set_typing ~172
Show the visitor and your teammates in the dashboard that a reply is being written. Call it right before you draft a reply the visitor will read, so a live agent sees the conversation is being handled. Do not call it for internal notes, for reading or summarizing, or when you are not going to reply. reply_to_conversation clears it; call again with is_typing false if you decide not to reply.
| Name | Type | Req | Description |
|---|---|---|---|
| conversation_id | string | yes | The conversation ID |
| duration_seconds | integer | – | Clear the indicator after this many seconds if no reply is sent |
| is_typing | boolean | – | true while you draft the reply, false to clear it without replying |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
No output schema declared.
No examples provided.
set_workflow_enabled ~58
Enable or disable a visitor workflow.
| Name | Type | Req | Description |
|---|---|---|---|
| enabled | boolean | yes | – |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
| workflow_id | string | yes | – |
No output schema declared.
No examples provided.
suppress_email_recipient ~119
Suppress an email address so lifecycle email campaigns skip it. Defaults to category "all" (blocks everything); pass a specific category key (see list_email_categories) to block only that category.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | EmailCategory key (see list_email_categories), or "all" for every category |
| string | yes | – | |
| note | string | – | – |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
| reason | string | – | – |
No output schema declared.
No examples provided.
tag_message ~99
Add tags to a message. Merges with existing tags (deduplicates). If Damper integration is enabled and a tag matches tags_to_sync, pushes the conversation to Damper as feedback.
| Name | Type | Req | Description |
|---|---|---|---|
| message_id | string | yes | The message ID to tag |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
| tags | array | yes | Tags to add to the message |
No output schema declared.
No examples provided.
toggle_automation ~64
Enable or disable an automation
| Name | Type | Req | Description |
|---|---|---|---|
| automation_id | string | yes | The automation ID |
| enabled | boolean | yes | Whether to enable or disable |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
No output schema declared.
No examples provided.
toggle_guide ~64
Enable or disable a guide
| Name | Type | Req | Description |
|---|---|---|---|
| enabled | boolean | yes | Whether to enable or disable |
| guide_id | string | yes | The guide ID |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
No output schema declared.
No examples provided.
track_event ~271
Track a lifecycle event exactly like the public track-event API. THIS CAN SEND REAL EMAILS: matching enabled api_trigger workflows fire immediately for real contacts. Use dry_run to preview matches without tracking or sending anything. Workflows only fire for events that resolve to a visitor (via user_id or email); company-only events never trigger workflows.
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | string | – | – |
| contact_name | string | – | – |
| dry_run | boolean | – | If true, does not track anything or send emails; only reports which enabled api_trigger workflows would match |
| string | – | – | |
| entity | string | – | – |
| event_key | string | – | Idempotency key; a repeat call with the same key returns the original event |
| metadata | object | – | Contact properties. Only fills properties the contact does not have yet (missing, null or empty), unless overwrite_metadata is true. |
| name | string | yes | – |
| occurred_at | string | – | ISO timestamp; defaults to now |
| overwrite_metadata | boolean | – | Replace existing contact properties with the metadata values |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
| user_id | string | – | – |
| value | string|number|boolean|null | – | – |
No output schema declared.
No examples provided.
unsuppress_email_recipient ~106
Remove an email address from the lifecycle email suppression list. Omit category to lift every suppression on the address (bounce/complaint rows are never removed); pass category to lift only that one.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | EmailCategory key (see list_email_categories), or "all" for every category |
| string | yes | – | |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
No output schema declared.
No examples provided.
untag_message ~63
Remove specific tags from a message
| Name | Type | Req | Description |
|---|---|---|---|
| message_id | string | yes | The message ID |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
| tags | array | yes | Tags to remove |
No output schema declared.
No examples provided.
update_article ~160
Update article properties or upsert a translation
| Name | Type | Req | Description |
|---|---|---|---|
| article_id | string | yes | The article ID |
| content | string | – | Translation content in Markdown (requires locale) |
| group_id | string|null | – | New group ID (null for ungrouped) |
| is_published | boolean | – | Publish/unpublish |
| locale | string | – | Locale to upsert translation for |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
| show_in_helpdesk | boolean | – | Whether to show in the helpdesk |
| slug | string | – | New slug |
| sort_order | integer | – | New display order |
| title | string | – | Translation title (requires locale) |
No output schema declared.
No examples provided.
update_article_group ~109
Update an article group
| Name | Type | Req | Description |
|---|---|---|---|
| description | string|null | – | New description |
| group_id | string | yes | The group ID |
| name | string | – | New name |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
| show_in_helpdesk | boolean | – | Whether to show this group in the helpdesk |
| slug | string | – | New slug |
| sort_order | integer | – | New display order |
No output schema declared.
No examples provided.
update_automation ~121
Update an automation
| Name | Type | Req | Description |
|---|---|---|---|
| automation_id | string | yes | The automation ID |
| delay_seconds | number | – | New delay |
| enabled | boolean | – | Enable/disable |
| frequency | string | – | New frequency |
| messages | object | – | New messages by locale |
| name | string | – | New name |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
| trigger_config | object | – | New trigger configuration |
| trigger_type | string | – | New trigger type |
No output schema declared.
No examples provided.
update_broadcast ~320
Update a draft or scheduled broadcast (name, email content, audience, schedule, list-hygiene or tracking options, A/B test).
| Name | Type | Req | Description |
|---|---|---|---|
| ab_test | object | – | Optional automatic A/B test: a random test group gets variant A (the main email) or B; after duration_hours the variant with the better winner_metric is sent to everyone else. Needs track_engagement… |
| audience | object | – | – |
| blocks | array | – | – |
| broadcast_id | string | yes | – |
| category | string | – | EmailCategory key (see list_email_categories); defaults to "marketing" |
| name | string | – | – |
| preheader | string | – | – |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
| scheduled_at | string|null | – | ISO datetime, or null to unschedule |
| skip_recently_emailed | boolean | – | Frequency cap: leave out contacts who got a broadcast in the last 24h (default true) |
| skip_role_addresses | boolean | – | Leave out shared role mailboxes like info@ or admin@ (default false) |
| skip_unengaged | boolean | – | Leave out contacts who got 5+ emails in the last 180 days without opening or clicking any (default true) |
| subject | string | – | – |
| template_document | object | – | – |
| theme | object | – | – |
| track_engagement | boolean | – | Open pixel + click tracking (default true) |
No output schema declared.
No examples provided.
update_company ~153
Update a company
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | string | yes | The company ID |
| deal_value | number|null | – | New deal value |
| domain | string|null | – | New domain |
| industry | string|null | – | New industry |
| metadata | – | – | Flat custom metadata (max 50 keys, 10KB). Values: string, number, boolean, or null. Replaces entire object when set. Pass null or {} to clear. |
| name | string | – | New name |
| notes | string | – | New notes |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
| stage_id | string|null | – | New stage ID |
No output schema declared.
No examples provided.
update_contact ~136
Update a contact
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | string | yes | The contact ID |
| string | – | New email | |
| metadata | – | – | Flat custom metadata (max 50 keys, 10KB). Values: string, number, boolean, or null. Replaces entire object when set. Pass null or {} to clear. |
| name | string | – | New name |
| notes | string | – | New notes |
| phone | string | – | New phone |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
| tags | array | – | New tags |
No output schema declared.
No examples provided.
update_conversation ~214
Update conversation status, assignment, snooze state, or spam. is_spam true does what "Mark as spam" does in the inbox: the conversation leaves the inbox, is marked read, and the same sender's next conversations in this project go straight to spam; is_spam false undoes it and lets the sender back in. The change is recorded in the conversation's activity as done via MCP. Use list_conversations with spam "only" to review spam.
| Name | Type | Req | Description |
|---|---|---|---|
| assigned_user_id | string|null | – | User ID to assign (null to unassign) |
| conversation_id | string | yes | The conversation ID |
| is_spam | boolean | – | true to mark the conversation as spam, false to unmark it |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
| snoozed_until | – | – | ISO 8601 time to snooze until (null to unsnooze) |
| status | string | – | New status |
No output schema declared.
No examples provided.
update_deal ~310
Update a deal. Moving it to a 100% stage marks it won and a 0% stage marks it lost (pass lost_reason); moving it back to an open stage reopens it.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | – | – | Deal amount in the project's sales currency and value unit |
| deal_id | string | yes | – |
| deal_type | string | – | new_business, expansion or renewal |
| expected_close_date | string|null | – | ISO 8601 date, e.g. 2026-12-31. Pass null to clear. |
| lost_reason | string|null | – | Why the deal was lost. Kept only while the deal is in a lost stage. |
| name | string | – | Deal name. Defaults to the company name. |
| next_step | string|null | – | The next action to move the deal |
| next_step_due_at | string|null | – | ISO 8601 date, e.g. 2026-12-31. Pass null to clear. |
| notes | string|null | – | – |
| owner_user_id | string|null | – | User who owns the deal |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
| source | string|null | – | Where the deal came from, e.g. inbound, outbound, referral |
| stage_id | string|null | – | CRM stage ID (see list_crm_stages). A 100% stage means won, 0% means lost. |
No output schema declared.
No examples provided.
update_email_campaign ~234
Update an email campaign.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | – |
| conditions | array | – | – |
| custom_frequency_key | string | – | – |
| delay_seconds | number | – | – |
| email_category | string | – | EmailCategory key (see list_email_categories), or "all" for every category |
| email_design | object | – | – |
| enabled | boolean | – | – |
| frequency | string | – | – |
| frequency_scope | string | – | – |
| name | string | – | – |
| next_campaign_id | string|null | – | Campaign id to trigger after this campaign email is sent, or null to clear |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
| reevaluate_conditions_at_send | boolean | – | – |
| skip_unengaged | boolean | – | Skip contacts who received 5+ emails in the last 180 days without opening, clicking or replying to any (the sunset rule broadcasts use). Ignored for categories people cannot unsubscribe from. Default… |
| template_id | string | – | – |
| trigger | object | – | – |
No output schema declared.
No examples provided.
update_email_categories ~86
Replace the full set of email categories for a project (upserts by key, removes any key not included). Refused with the referencing suppressions/broadcasts/workflows if a key still in use would be removed.
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | yes | – |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
No output schema declared.
No examples provided.
update_email_postal_address ~84
Set the physical mailing address shown in the footer of every marketing/lifecycle email (required by CAN-SPAM). Pass null or an empty string to remove it. Confirm the exact address with the user first.
| Name | Type | Req | Description |
|---|---|---|---|
| postal_address | – | yes | – |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
No output schema declared.
No examples provided.
update_email_template ~94
Update a reusable workflow email template.
| Name | Type | Req | Description |
|---|---|---|---|
| blocks | array | – | – |
| name | string | – | – |
| preheader | string | – | – |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
| subject | string | – | – |
| template_document | object | – | – |
| template_id | string | yes | – |
| theme | object | – | – |
No output schema declared.
No examples provided.
update_guide ~249
Update a guide
| Name | Type | Req | Description |
|---|---|---|---|
| conditions | object | – | Audience conditions, evaluated server-side before the guide is sent. Pass an empty rules array to clear. |
| delay_seconds | number | – | New delay |
| description | object | – | One-line description by locale. |
| enabled | boolean | – | Enable/disable |
| frequency | string | – | New frequency |
| guide_id | string | yes | The guide ID |
| name | string | – | New name. The slug does NOT change — host-page calls keep working across renames. |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
| show_in_suggestions | boolean | – | Offer this guide to a visitor typing a matching question. Independent of trigger_type. |
| start_url | string | – | Where this guide runs — same-origin path template, e.g. "{{app_base_path}}/documents/add/invoice". Empty string clears it. |
| steps | array | – | New steps |
| title | object | – | Guide title by locale. Shown to visitors. |
| trigger_config | object | – | New trigger config |
| trigger_type | string | – | New trigger type |
No output schema declared.
No examples provided.
update_sender_identity ~212
Update the local part, display sender name, and/or Reply-To override of the configured sender domain, without changing the domain itself. By default, Reply-To stays on the HAL inbound address so inbound routing/threading keep working. Setting `reply_to` overrides that with the given address - it must already forward into the project's HAL inbound address, or replies will be lost. Pass an empty string or omit `reply_to` as `null` to clear an existing override and revert to the HAL address.
| Name | Type | Req | Description |
|---|---|---|---|
| local_part | string | – | New local part of the From address |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
| reply_to | string|null | – | Reply-To override, a single bare email address (e.g. support@yourcompany.com) that already forwards into the HAL inbound address. Pass an empty string or null to clear the override. |
| sender_name | string | – | New display name to use in From |
No output schema declared.
No examples provided.
update_webhook ~97
Update an existing webhook
| Name | Type | Req | Description |
|---|---|---|---|
| enabled | boolean | – | Enable or disable the webhook |
| events | array | – | New event types |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
| secret | string|null | – | New secret (null to remove) |
| url | string | – | New webhook URL |
| webhook_id | string | yes | The webhook ID |
No output schema declared.
No examples provided.
update_workflow ~132
Update a visitor workflow. Partial: only provided fields change. If trigger fields change without a new definition, the existing trigger node is synced in place.
| Name | Type | Req | Description |
|---|---|---|---|
| definition | object | – | – |
| enabled | boolean | – | – |
| frequency | string | – | – |
| name | string | – | – |
| priority | integer | – | – |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
| trigger_config | object | – | – |
| trigger_mode | string | – | – |
| trigger_type | string | – | – |
| workflow_id | string | yes | – |
No output schema declared.
No examples provided.
update_workflow_email_defaults ~112
Update the project default email design (subject/preheader/theme/template_document) used to seed new send_email nodes. Merges into the project config without touching other settings.
| Name | Type | Req | Description |
|---|---|---|---|
| blocks | array | – | Shortcut for template_document.blocks |
| preheader | string | – | – |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
| subject | string | – | – |
| template_document | object | – | – |
| theme | object | – | – |
No output schema declared.
No examples provided.
upload_email_image ~206
Upload an image to a project's email image library so it can be used in lifecycle/workflow email `image` blocks (email_block_types.image.url must be an absolute URL — external hosting is no longer required). Provide exactly one of data_base64 (with mime_type) or source_url. Use email_url in email image blocks (image.url).
| Name | Type | Req | Description |
|---|---|---|---|
| alt | string | – | Alt text for the image |
| data_base64 | string | – | Base64-encoded image bytes, max 5MB decoded |
| filename | string | – | Original filename for the data_base64 path, used to derive alt text when alt is omitted |
| mime_type | string | – | Required with data_base64: image/jpeg, image/png, image/gif, or image/webp |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
| source_url | string | – | https/http URL to fetch the image from |
No output schema declared.
No examples provided.
validate_email_template ~104
Validate an email template and return AI-client-friendly errors.
| Name | Type | Req | Description |
|---|---|---|---|
| blocks | array | – | Shortcut for template_document.blocks |
| preheader | string | – | Email preheader |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
| subject | string | – | Email subject |
| template_document | object | – | Structured email document |
| template_id | string | – | – |
| theme | object | – | – |
No output schema declared.
No examples provided.
validate_guide ~110
Validate a guide's start location and step selectors against the live pages the developer is logged into. Results are recorded by the widget's authoring mode (?hal_guide_debug=1 on any page where the widget runs); this tool returns the newest snapshot per page, so a guide that spans pages reports each of them.
| Name | Type | Req | Description |
|---|---|---|---|
| guide_id | string | yes | The guide ID |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
No output schema declared.
No examples provided.
validate_workflow ~123
Validate a visitor workflow definition without saving it. Same input as create_workflow.
| Name | Type | Req | Description |
|---|---|---|---|
| definition | object | yes | – |
| enabled | boolean | – | – |
| frequency | string | – | – |
| name | string | yes | – |
| priority | integer | – | – |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
| trigger_config | object | – | Shape depends on trigger_type; call get_workflow_builder_reference first. |
| trigger_mode | string | – | – |
| trigger_type | string | yes | – |
No output schema declared.
No examples provided.
How do I install the HAL MCP server?
HAL is a hosted endpoint at https://api.chatwithhal.com/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 · api.chatwithhal.com
claude mcp add --transport http com-chatwithhal-mcp 'https://api.chatwithhal.com/mcp'
What is the HAL MCP server?
HAL is an MCP server listed in the public MCP registry as com.chatwithhal/mcp. Customer conversations, help center, CRM, deals and email campaigns on HAL (chatwithhal.com). This page covers its hosted endpoint (https://api.chatwithhal.com/mcp).
Is the HAL MCP server safe to use?
HAL scores 76 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 HAL MCP server expose?
HAL exposes 136 tools: list_projects, list_conversations, get_conversation, get_conversation_image, set_typing, and 131 more. Their descriptions and schemas cost roughly 15,129 tokens of context every time the server is loaded.
Does the HAL MCP server require authentication?
Yes. HAL 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 HAL MCP server still maintained?
HAL is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.