gethal.ai
REMOTE · GETHAL.AI · SCANNED SEP 24
Public MCP for gethal.ai — autonomous AI sales agent. Pricing, features, book a demo.
Available components
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability84
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 376 tokens (~53/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
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
claude mcp add --transport http ai-gethal-mcp 'https://gethal.ai/mcp'
{
"mcpServers": {
"ai-gethal-mcp": {
"url": "https://gethal.ai/mcp"
}
}
} {
"servers": {
"ai-gethal-mcp": {
"type": "http",
"url": "https://gethal.ai/mcp"
}
}
} [mcp_servers.ai-gethal-mcp] url = "https://gethal.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-gethal-mcp": {
"type": "remote",
"url": "https://gethal.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-gethal-mcp --url 'https://gethal.ai/mcp' --transport streamable-http
mcp_servers:
ai-gethal-mcp:
url: "https://gethal.ai/mcp" {
"McpServers": {
"ai-gethal-mcp": {
"Transport": "http",
"Url": "https://gethal.ai/mcp"
}
}
} assistant mcp add ai-gethal-mcp -t streamable-http -u 'https://gethal.ai/mcp'
{
"mcpServers": {
"ai-gethal-mcp": {
"type": "http",
"url": "https://gethal.ai/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 26 Aug 26 78
- 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
- 11 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
- 31 Jul 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
- 27 Jul 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 Jul 26 0
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 24 Sept 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 | 22 Sept 2026 | 21 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | e0d0ebf8bb62fe080e838ea337bac259 |
| 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. | present | 3799 | 8 | Verified |
| gethal.ai. | absent | 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 |
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 →
book_demo ~113
Submits a demo request. The prospect receives a confirmation email and must click the link in it before the request reaches a human at A Cloud Frontier. Use only when a real person has explicitly asked for a demo and provided their own working email address. Do NOT call this for testing, evaluation, or crawling purposes — automated and unconfirmable requests are rejected.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | Company name (optional). |
| string | yes | Work email address. | |
| name | string | yes | Full name of the prospect. |
No output schema declared.
No examples provided.
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_pricing ~50
Returns the gethal.ai pricing plans (Solo, Team, Enterprise) with both monthly and yearly rates plus included features.
| Name | Type | Req | Description |
|---|---|---|---|
| billing | string | – | Which billing cadence to return. Defaults to "both". |
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.
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 78 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 7 tools: get_company_info, get_pricing, get_features, get_use_cases, describe_hal, and 2 more. Their descriptions and schemas cost roughly 326 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 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.