Hello, AI
REMOTE · HELLOAI.COM
Ask your assistant which frontier model to use and get a live, Elo-backed answer.
Available components
Last scanned (14 hours ago)
Scores higher than 69% of remote servers
Reachable. Last reached 5 Nov 2026.
Category AI and Machine Learning
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- 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 Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 568 tokens (~94/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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 →
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 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 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.
- 28 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 27 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://helloai.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.helloai.com | CN=YR1,O=Let's Encrypt,C=US | 22 Sept 2026 | 21 Dec 2026 | RSA 2048 | SHA256-RSA | 662ca9a5bdd4e123727dc25d09f40de133a |
| SANs: helloai.com, www.helloai.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of helloai.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| helloai.com. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline'; img-src 'self' data: https:; font-src 'self'; connect-src 'self'; frame-ancestors 'none'; base-uri 'self'; form-action 'self'; object-src 'none'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://helloai.com/mcp | Verified | 200 | |
| http (plaintext) | http://helloai.com/mcp | HTTPS enforced | 301 | https://helloai.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 →
get_model Get one model ~50
One tracked model's full record by id (claude, fable, muse, gemini, qwen, grok) or exact name.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Model id or exact name |
No output schema declared.
No examples provided.
get_status Data freshness and version ~31
Data freshness, app version, model and article counts, the scoring version and snapshot fingerprint, and the rate limit.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_articles List recent articles ~47
Recent Hello, AI articles, newest first: title, date, category, excerpt and URL.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Articles to return, 1 to 50. Default 10. |
No output schema declared.
No examples provided.
list_categories List use-case categories ~39
The curated use-case categories with their curator-chosen leader and a one-paragraph insight. The leader is a hand-set label, not derived from Elo.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_models List tracked models ~66
All tracked models with full records: Elo and its provenance (elo_source), prices per million tokens, context window, strengths, description. rated is false when the stored Elo is a predecessor's, missing or stale.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | – | Provider name, case-insensitive substring match. |
No output schema declared.
No examples provided.
recommend_models Recommend models for a task ~220
Rank Hello, AI's tracked frontier models for a task. Same scoring as GET /api/recommend: task match 40%, Elo 35%, input cost 15%, context 10% (Elo 55%, cost 25%, context 20% when no task matches). Only rated models rank; unrated ones are listed separately. score is an ordering aid, not a quality measure.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many ranked rows to return, 1 to 10. Default 3. |
| max_cost | number | – | Maximum USD per 1 million input tokens; models above it are excluded. |
| min_context | integer | – | Minimum context window in tokens; models below it are excluded. |
| provider | string | – | Provider name, case-insensitive exact match (for example Anthropic, Google, xAI). |
| task | string | – | Use case, matched against the category names: Overall Preference, Coding & Engineering, Hard Reasoning & Science, Honest Daily Use. Examples: coding, reasoning, overall, daily. |
No output schema declared.
No examples provided.
How do I install the Hello, AI MCP server?
Hello, AI is a hosted endpoint at https://helloai.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 · helloai.com
claude mcp add --transport http com-helloai-directory 'https://helloai.com/mcp'
What is the Hello, AI MCP server?
Hello, AI is an MCP server listed in the public MCP registry as com.helloai/directory. Ask your assistant which frontier model to use and get a live, Elo-backed answer. This page covers its hosted endpoint (https://helloai.com/mcp).
Is the Hello, AI MCP server safe to use?
Hello, AI scores 77 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 Hello, AI MCP server expose?
Hello, AI exposes 6 tools: recommend_models, list_models, get_model, list_categories, list_articles, get_status. Their descriptions and schemas cost roughly 453 tokens of context every time the server is loaded.
Does the Hello, AI MCP server require authentication?
No. We connected to Hello, AI without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Hello, AI MCP server still maintained?
Hello, AI 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.
What did VerifyMCP test on the Hello, AI MCP server?
VerifyMCP ran 13 checks on Hello, AI, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.