HAL
REMOTE · API.CHATWITHHAL.COM
Customer conversations, help center, CRM, deals and email campaigns on HAL (chatwithhal.com).
Available components
Last scanned (23 hours ago)
Scores higher than 64% of remote servers
Reachable. Last reached 4 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 Usability62
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 15170 tokens (~113/item across 134 items; 134 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 Management17
- Stability observed for 5 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 19 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 135 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.
- 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 4 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 →
cancel_broadcast ~64
Cancel a scheduled, in-progress, or paused broadcast. Recipients not yet sent to are marked cancelled.
| Name | Type | Req | Description |
|---|---|---|---|
| broadcast_id | string | yes | – |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
No output schema declared.
No examples provided.
check_sender_domain ~48
Re-check the project's custom sender domain verification status against Amazon SES.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
No output schema declared.
No examples provided.
configure_sender_domain ~204
Configure a custom sender domain for visitor-facing email on this project (Starter plan and above). Returns DNS records (DKIM CNAMEs, and MX/TXT if a mail-from subdomain is set) that the user must add themselves at their DNS provider before the domain can verify. Reply-To stays on the HAL inbound address so inbound routing keeps working, unless a Reply-To override is set afterwards with update_sender_identity.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain to send from, e.g. mail.yourcompany.com |
| local_part | string | yes | The local part of the From address, e.g. "support" |
| mail_from_subdomain | string | – | Optional custom MAIL FROM subdomain label, e.g. "bounce" |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
| sender_name | string | – | Display name to use in From. Defaults to the project name. |
No output schema declared.
No examples provided.
create_article ~124
Create an article with an initial translation
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | Article content (Markdown) |
| group_id | string|null | – | Group ID (null for ungrouped) |
| locale | string | – | Locale for the initial translation |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
| show_in_helpdesk | boolean | – | Whether to show this article in the helpdesk (defaults to true) |
| slug | string | yes | URL-friendly slug |
| title | string | yes | Article title |
No output schema declared.
No examples provided.
create_article_group ~92
Create a new article group
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Group description |
| name | string | yes | Group 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 (defaults to true) |
| slug | string | yes | URL-friendly slug |
No output schema declared.
No examples provided.
create_automation ~120
Create a new automation
| Name | Type | Req | Description |
|---|---|---|---|
| delay_seconds | number | – | Delay before showing |
| enabled | boolean | – | Whether enabled |
| frequency | string | – | How often to fire |
| messages | object | yes | Messages by locale (e.g. {"en": "Hello!"}) |
| name | string | yes | Automation name |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
| trigger_config | object | – | Trigger configuration |
| trigger_type | string | yes | Trigger type |
No output schema declared.
No examples provided.
create_broadcast ~338
New to HAL email? Call get_email_capabilities_overview first. Create a draft (or scheduled, if scheduled_at is set) one-off email broadcast. Does not send anything.
| 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 | – | Defaults to all contacts with an email |
| blocks | array | – | Shortcut for template_document.blocks |
| category | string | – | EmailCategory key (see list_email_categories); defaults to "marketing" |
| name | string | yes | – |
| preheader | string | – | Email preheader |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
| scheduled_at | string | – | ISO datetime to schedule the send |
| 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 | yes | Email subject |
| template_document | object | – | Structured email document |
| theme | object | – | – |
| track_engagement | boolean | – | Open pixel + click tracking (default true) |
No output schema declared.
No examples provided.
create_company ~131
Create a new company
| Name | Type | Req | Description |
|---|---|---|---|
| deal_value | number | – | Deal value |
| domain | string | – | Company domain |
| industry | string | – | Industry |
| metadata | object | – | Flat custom metadata (max 50 keys, 10KB). Values: string, number, boolean, or null. Replaces entire object on write. |
| name | string | yes | Company name |
| notes | string | – | Notes |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
| stage_id | string | – | CRM stage ID |
No output schema declared.
No examples provided.
create_contact ~119
Create a new contact
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Contact email | |
| metadata | object | – | Flat custom metadata (max 50 keys, 10KB). Values: string, number, boolean, or null. Replaces entire object on write. |
| name | string | – | Contact name |
| notes | string | – | Notes |
| phone | string | – | Contact phone |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
| tags | array | – | Tags |
No output schema declared.
No examples provided.
create_deal ~307
Create a deal for a company. The company's own stage and value follow its primary deal (its newest open new-business deal).
| Name | Type | Req | Description |
|---|---|---|---|
| amount | – | – | Deal amount in the project's sales currency and value unit |
| company_id | string | yes | – |
| contacts | array | – | People involved in the deal |
| 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.
create_email_campaign ~235
New to HAL email? Call get_email_capabilities_overview first. Create an email campaign using campaign language instead of workflow graph internals.
| Name | Type | Req | Description |
|---|---|---|---|
| conditions | array | – | – |
| custom_frequency_key | string | – | – |
| delay_seconds | number | – | – |
| email_category | string | – | Defaults to "marketing" if omitted |
| email_design | object | – | – |
| enabled | boolean | – | – |
| frequency | string | – | – |
| frequency_scope | string | – | – |
| name | string | yes | – |
| next_campaign_id | string | – | Optional campaign id to trigger after this campaign email is sent |
| 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 | yes | – |
No output schema declared.
No examples provided.
create_email_template ~113
New to HAL email? Call get_email_capabilities_overview first. Create a reusable workflow email template.
| Name | Type | Req | Description |
|---|---|---|---|
| blocks | array | – | Shortcut for template_document.blocks |
| name | string | yes | – |
| preheader | string | – | Email preheader |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
| subject | string | yes | Email subject |
| template_document | object | – | Structured email document |
| theme | object | – | – |
No output schema declared.
No examples provided.
create_guide ~345
Create a new guide
| Name | Type | Req | Description |
|---|---|---|---|
| conditions | object | – | Audience conditions, evaluated server-side: an ineligible visitor receives nothing at all. guide.completed:<id> and event.count:<name> enable completion-style targeting (e.g. not_exists on guide.comp… |
| delay_seconds | number | – | Delay before showing |
| description | object | – | One-line description by locale. Shown under the title. |
| enabled | boolean | – | Whether enabled |
| frequency | string | – | How often to show |
| name | string | yes | Guide name (internal label, not shown to visitors). A slug for host-page calls is generated from it and returned. |
| 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. Requires `title`. Independent of trigger_type: a route guide may fire on arrival and still be offered in chat. |
| start_url | string | – | Where this guide runs, as a same-origin path template against the visitor's stored properties, e.g. "{{app_base_path}}/documents/add/invoice". When a visitor starts the guide from elsewhere, the widg… |
| steps | array | yes | Guide steps |
| title | object | – | Guide title by locale, e.g. {"en":"Change your plan"}. Shown to visitors. |
| trigger_config | object | – | Trigger configuration |
| trigger_type | string | yes | Trigger type |
No output schema declared.
No examples provided.
create_webhook ~88
Create a new webhook
| Name | Type | Req | Description |
|---|---|---|---|
| events | array | yes | Event types to subscribe to (e.g. conversation.created, message.created) |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
| secret | string | – | Optional HMAC secret for signature verification |
| url | string | yes | The webhook URL to receive events |
No output schema declared.
No examples provided.
create_workflow ~153
New to HAL email? Call get_email_capabilities_overview first. Create a visitor workflow: a trigger plus a branching graph of condition/send_widget_message/send_email/trigger_campaign/end nodes. Call get_workflow_builder_reference first.
| 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.
delete_broadcast ~55
Delete a broadcast. Refused while it is actively sending.
| Name | Type | Req | Description |
|---|---|---|---|
| broadcast_id | string | yes | – |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
No output schema declared.
No examples provided.
delete_deal ~59
Delete a deal. A company with no deals left drops out of the pipeline.
| Name | Type | Req | Description |
|---|---|---|---|
| deal_id | string | yes | – |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
No output schema declared.
No examples provided.
delete_email_campaign ~68
Delete an email campaign. Refuses if another workflow in the project still chains into it via trigger_campaign or next_campaign_id.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | – |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
No output schema declared.
No examples provided.
delete_email_image ~73
Delete an image from a project’s email image library. Remove it from any email templates first, or the image block will break.
| Name | Type | Req | Description |
|---|---|---|---|
| image_id | string | yes | The email image ID |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
No output schema declared.
No examples provided.
delete_email_template ~57
Delete a reusable workflow email template. Existing campaigns keep their embedded copy.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
| template_id | string | yes | – |
No output schema declared.
No examples provided.
delete_guide ~56
Permanently delete a guide and its execution history
| 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.
delete_webhook ~50
Delete a webhook
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
| webhook_id | string | yes | The webhook ID |
No output schema declared.
No examples provided.
delete_workflow ~68
Delete a visitor workflow. Refuses if another workflow in the project still chains into it via trigger_campaign or next_campaign_id.
| Name | Type | Req | Description |
|---|---|---|---|
| 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.
disable_email_campaign ~48
Disable an email campaign.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | – |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
No output schema declared.
No examples provided.
enable_email_campaign ~48
Enable an email campaign.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | – |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
No output schema declared.
No examples provided.
find_relevant_articles ~334
Find published help articles that fit a conversation, in the visitor's language and limited to ones this visitor may see. Matches the visitor's latest message, or `query` when given. Returns up to 6, best match first; weaker results can be only loosely related, so check the title and excerpt before sharing one. Read-only; uses no AI quota. Each result has `insert`, the exact markup to put in the reply. To show a help article to the visitor, write `[label](hal-article:<article id or slug>)` into the `content` of reply_to_conversation. The widget renders it as a clickable card at that spot, on its own line (it is not an inline link inside a sentence), so put it between sentences or paragraphs, e.g. "Refunds take 5 days.\n[Refund policy](hal-article:refund-policy)\nAnything else?". The label is the card title, so use the article title. Several cards in one reply are fine. Only published articles the visitor may see are accepted; each reference is checked and rewritten to the slug for the visitor's language. Find the right article with find_relevant_articles (matched to the conversation, or to your own query), or list_articles with published_only.
| Name | Type | Req | Description |
|---|---|---|---|
| conversation_id | string | yes | The conversation to find articles for |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
| query | string | – | What to look for, e.g. 'refund policy'. Defaults to the visitor's latest message. |
No output schema declared.
No examples provided.
generate_ai_response_suggestion ~111
Generate an advisory-only HAL AI reply suggestion for the latest visitor message. Call this after get_conversation, then combine HAL's draft, evidence, and confidence with the conversation messages when composing your final answer. This tool never sends a message to the visitor, even when project auto-send or AI deflection is enabled.
| Name | Type | Req | Description |
|---|---|---|---|
| conversation_id | string | yes | The conversation ID |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
No output schema declared.
No examples provided.
get_article ~51
Get an article with translations
| Name | Type | Req | Description |
|---|---|---|---|
| article_id | string | yes | The article ID |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
No output schema declared.
No examples provided.
get_automation ~50
Get automation details
| Name | Type | Req | Description |
|---|---|---|---|
| automation_id | string | yes | The automation ID |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
No output schema declared.
No examples provided.
get_broadcast ~123
Get a single email broadcast, including delivery/open/click counts. With an A/B test, `ab_test` has its settings, `phase` (testing, waiting, winner_sending, done, skipped, cancelled), `ends_at` (automatic winner pick), the `winner`, and `results` (test-group sent/opens/clicks/rates per variant plus a confidence score).
| Name | Type | Req | Description |
|---|---|---|---|
| broadcast_id | string | yes | – |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
No output schema declared.
No examples provided.
get_broadcast_audience_fields ~62
List the fields available for building a broadcast audience (contact/company builtins, sampled metadata keys, valid operators per type).
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
No output schema declared.
No examples provided.
get_broadcast_readiness ~123
Deliverability checklist for a broadcast before sending: sender authentication (custom domain, DMARC, MAIL FROM/SPF), postal address, project bounce/complaint health, warm-up capacity (how many days the send will be spread over), and content lint (size, image-heavy, subject, spam phrases, link shorteners). `error` checks block sending; share warnings with the user.
| Name | Type | Req | Description |
|---|---|---|---|
| broadcast_id | string | yes | – |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
No output schema declared.
No examples provided.
get_company ~67
Get a company with contacts, details and its deals. The company stage and deal_value mirror its primary deal.
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | string | yes | The company ID |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
No output schema declared.
No examples provided.
get_contact ~61
Get a contact with full details, recent activity and the deals they are on
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | string | yes | The contact ID |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
No output schema declared.
No examples provided.
get_conversation ~139
Get a conversation with its messages and attachment metadata. agents_typing lists teammates drafting a reply right now; if someone is, let them answer instead of replying over them. replied_to_email is set when the conversation started as a reply to a campaign, workflow or broadcast email. Call get_conversation_image with an image attachment ID to inspect its visual content. To incorporate HAL's own evidence-backed AI draft into your final answer, call generate_ai_response_suggestion next.
| Name | Type | Req | Description |
|---|---|---|---|
| conversation_id | string | yes | The conversation ID |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
No output schema declared.
No examples provided.
get_conversation_image ~95
Get an image attached to a conversation message as MCP image content so the AI client can inspect it. Images over 2 MB are resized and compressed before delivery. Use an attachment ID returned by get_conversation.
| Name | Type | Req | Description |
|---|---|---|---|
| attachment_id | string | yes | The image attachment ID returned by get_conversation |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
No output schema declared.
No examples provided.
get_deal ~59
Get a deal with its company, stage, contacts and stage/amount history
| Name | Type | Req | Description |
|---|---|---|---|
| deal_id | string | yes | – |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
No output schema declared.
No examples provided.
get_deal_pipeline ~86
Summarize the sales pipeline: per stage the number of deals, total and probability-weighted amount, plus open/won/lost totals, win rate and open deals whose expected close date has passed. Use list_deals for the deals themselves.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
No output schema declared.
No examples provided.
get_email_campaign ~48
Get email campaign details.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | – |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
No output schema declared.
No examples provided.
get_email_campaign_run ~61
Get one email campaign run with clicked URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | – |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
| run_id | string | yes | – |
No output schema declared.
No examples provided.
get_email_capabilities_overview ~63
Orientation for HAL email features: campaigns vs workflows vs broadcasts, templates vs project defaults vs inline design, sender domains, images, test sending, track_event, and unsubscribe/suppression. Call this before creating any campaign, workflow, broadcast, or template.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_email_deliverability ~275
Project email reporting. Always returns: health (last 30 days across every campaign, workflow and broadcast: sent, sent_last_24h, delivered, hard bounces (bounced), soft bounces, complaints and their rates, plus the status that blocks broadcasts, and reset_at when a list-cleanup reset restarted the window), sources (the same window broken down per workflow/broadcast with delivered, hard/soft bounces, unique opens, clicks and replies), warm-up progress (only broadcasts count toward it), and the footer postal address. Pass workflow_id or broadcast_id (optionally with days; omitted = all time) to also get stats for that one campaign. Opens and clicks exclude automatic ones from security scanners and Apple Mail Privacy Protection, which are reported as automatic_opens/automatic_clicks. Replies count recipients who answered the email (auto-replies are ignored). Delivered counts only cover emails sent after delivery tracking was enabled.
| Name | Type | Req | Description |
|---|---|---|---|
| broadcast_id | string | – | Broadcast to report on |
| days | integer | – | Trailing window for the workflow_id/broadcast_id stats; omitted = all time |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
| workflow_id | string | – | Campaign/workflow to report on |
No output schema declared.
No examples provided.
get_email_template ~50
Get a reusable workflow email template.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
| template_id | string | yes | – |
No output schema declared.
No examples provided.
get_email_unsubscribe_status ~89
Check whether an email address is currently suppressed for lifecycle email campaigns, for a given category (default "all").
| 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.
get_guide ~50
Get guide details
| 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.
get_guide_health ~78
Which guides had steps fail to anchor recently — the signal that a selector rotted in the target app
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
| since_days | number | – | Look at misses from the last N days. Default: 7. |
No output schema declared.
No examples provided.
get_guide_stats ~89
Per-guide analytics: triggers, completions, completion rate, per-step drop-off, selector misses
| 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) |
| since_days | number | – | Count only executions from the last N days. Omit for all time. |
No output schema declared.
No examples provided.
get_macro ~53
Get a single shared macro by ID
| Name | Type | Req | Description |
|---|---|---|---|
| macro_id | string | yes | The macro ID |
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
No output schema declared.
No examples provided.
get_message_tags_stats ~45
Get all project tags with their usage counts
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
No output schema declared.
No examples provided.
get_sender_domain ~83
Get the custom sender domain (Starter plan and above) configured for this project, including DNS records, verification status, and any Reply-To override (`sender_domain.reply_to`, alongside the top-level `reply_to` this project's emails actually use).
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | – | Target project ID |
| project_slug | string | – | Target project slug (helpdesk slug) |
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 75 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 134 tools: list_projects, list_conversations, get_conversation, get_conversation_image, set_typing, and 129 more. Their descriptions and schemas cost roughly 14,910 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 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.