Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

gethal.ai

REMOTE · GETHAL.AI

Public MCP for gethal.ai — autonomous AI sales agent. Pricing, features, book a demo.

Available components

0 this week 75 Trust /100

Last scanned (22 hours ago)

Scores higher than 62% of remote servers

Reachable. Last reached 21 Nov 2026.

Category CRM and Sales

Trust breakdown (7 categories)

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 Security57
Transport & Reachability100
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 495 tokens (~55/item across 9 items; 9 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management84
  • Stability check failed: schema churn in the 30 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 3 additions. See how to fix → Fail
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

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 →

Changelog

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.

  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 3 Nov 26 0
    • Schema quality: 50 → 55 ▼ functional
    • New tool “get_posts” functional
  • 26 Oct 26 −3
    • Stability: pass → fail ▼ security
    • A breaking change shipped without a version bump: still 1.0.0 ▼ security
    • Tool “book_demo” was removed ▼ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 56 → 50 ▲ functional
  • 25 Oct 26 0
    • Tool “get_pricing” rewrote its description, which is the text the model reads security
    • Schema quality: 376 → 509 ▼ functional
    • New tool “get_playbook” functional
    • New tool “get_products” functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
Diagnostics

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://gethal.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=gethal.ai CN=WE1,O=Google Trust Services,C=US 20 Nov 2026 19 Feb 2027 ECDSA 256 ECDSA-SHA256 2dfb27cde22459de13241a1803600bd4
SANs: gethal.ai
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 gethal.ai. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ai. DS published 1814 8 Verified
gethal.ai. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://gethal.ai/mcp Verified 200
http (plaintext) http://gethal.ai/mcp HTTPS enforced 301 https://gethal.ai/mcp
MCP tools · 9 exposed · ~435 tokens

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 →

Tool Tokens
describe_hal ~40

Explains how the HAL autonomous sales agent works: the six-stage pipeline (find → research → qualify → quality control → draft → send) and key traits.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_company_info ~30

Returns the company name, operator, contact email, homepage, and a short description of gethal.ai.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_customer_profile ~37

Returns the target customer profile for gethal.ai (industries, team sizes, regions, representative use cases) and any public reference customers.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_features ~22

Returns the six core features of gethal.ai with one-line descriptions.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_playbook ~74

Returns the HAL playbook: guides and cheat sheets on working with each product (for Outreach: what HAL does in each pipeline stage, and the requests customers send HAL most), with page URLs and PDF downloads in English and Danish. Optionally filter by product.

NameTypeReqDescription
productstring–Only return guides for this product.

No output schema declared.

No examples provided.

get_posts ~89

Returns the latest posts from the gethal.ai blog (https://gethal.ai/blog): title, language, date, excerpt, categories and URL. Posts exist in English (default), Danish, Spanish and Polish; pass language to get another one.

NameTypeReqDescription
languagestring–Language of the posts. Default en.
limitinteger–How many posts, newest first. Default 10.

No output schema declared.

No examples provided.

get_pricing ~62

Returns pricing for all four HAL products (Outreach, inbox-agent, Saga, vitr) plus the Outreach plans (Team, Enterprise) with monthly and yearly rates and included features.

NameTypeReqDescription
billingstring–Which billing cadence to return. Defaults to "both".

No output schema declared.

No examples provided.

get_products ~47

Returns the four HAL products (Outreach, inbox-agent, Saga, vitr): what each does, how it works on its own and together with the others, its page URL and pricing model.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_use_cases ~34

Returns representative B2B sales use cases (outbound prospecting, market expansion, partner-channel sales) with example prompts.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the gethal.ai MCP server?

gethal.ai is a hosted endpoint at https://gethal.ai/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 · gethal.ai

# add to Claude Code
claude mcp add --transport http ai-gethal-mcp 'https://gethal.ai/mcp'
Common questions

What is the gethal.ai MCP server?

gethal.ai is an MCP server listed in the public MCP registry as ai.gethal/mcp. Public MCP for gethal.ai, autonomous AI sales agent. Pricing, features, book a demo. This page covers its hosted endpoint (https://gethal.ai/mcp).

Is the gethal.ai MCP server safe to use?

gethal.ai 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 gethal.ai MCP server expose?

gethal.ai exposes 9 tools: get_company_info, get_pricing, get_products, get_features, get_use_cases, and 4 more. Their descriptions and schemas cost roughly 435 tokens of context every time the server is loaded.

Does the gethal.ai MCP server require authentication?

No. We connected to gethal.ai without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the gethal.ai MCP server still maintained?

gethal.ai 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 gethal.ai MCP server?

VerifyMCP ran 12 checks on gethal.ai, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about gethal.ai: Authorization. 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.