com.hibot/hibot
REMOTE · HIBOT.COM · SCANNED SEP 28
HiBot public knowledge: the ANSWER framework for AI visibility, audit plans, case studies, research
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 Security63
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability79
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 605 tokens (~121/item across 5 items; 5 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 Management42
- Stability check failed: schema churn in the 26 days we've observed: 3 tool removals, 0 breaking changes, 0 auth/transport breaks, 1 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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 com.hibot/hibot MCP server?
com.hibot/hibot is a hosted endpoint at https://hibot.com/mcp/public, 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 · hibot.com
claude mcp add --transport http com-hibot-hibot 'https://hibot.com/mcp/public'
{
"mcpServers": {
"com-hibot-hibot": {
"url": "https://hibot.com/mcp/public"
}
}
} {
"servers": {
"com-hibot-hibot": {
"type": "http",
"url": "https://hibot.com/mcp/public"
}
}
} [mcp_servers.com-hibot-hibot] url = "https://hibot.com/mcp/public"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-hibot-hibot": {
"type": "remote",
"url": "https://hibot.com/mcp/public",
"enabled": true
}
}
} openclaw mcp add com-hibot-hibot --url 'https://hibot.com/mcp/public' --transport streamable-http
mcp_servers:
com-hibot-hibot:
url: "https://hibot.com/mcp/public" {
"McpServers": {
"com-hibot-hibot": {
"Transport": "http",
"Url": "https://hibot.com/mcp/public"
}
}
} assistant mcp add com-hibot-hibot -t streamable-http -u 'https://hibot.com/mcp/public'
{
"mcpServers": {
"com-hibot-hibot": {
"type": "http",
"url": "https://hibot.com/mcp/public"
}
}
} 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.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 32 to 35.
- 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
- 24 Sept 26 −5
- Stability: 0.70 → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Tool “get_case_study” was removed ▼ security
- Tool “get_plans” was removed ▼ security
- Tool “list_case_studies” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “generate_ai_visibility_questions” rewrote its description, which is the text the model reads security
- Tool “get_answer_methodology” rewrote its description, which is the text the model reads security
- Tool “get_blog_article” rewrote its description, which is the text the model reads security
- Tool “list_blog_articles” rewrote its description, which is the text the model reads security
- Tool “search_blog” rewrote its description, which is the text the model reads security
- Schema quality: 996 → 605 ▲ functional
- “generate_ai_visibility_questions” dropped the optional parameter “email” cosmetic
- “generate_ai_visibility_questions” dropped the optional parameter “includeWhitepaper” cosmetic
- Tool “generate_ai_visibility_questions” changed its title: Free AI Visibility Question Set → AI Visibility Questions cosmetic
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: pass → fail ▼ functional
- New tool “generate_ai_visibility_questions” functional
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 28 Sept 2026 · Probed https://hibot.com/mcp/public
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=hibot.com | CN=YE1,O=Let's Encrypt,C=US | 26 Sept 2026 | 25 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6cd5c749a6adbcad5947158d2f7f002f4cb |
| SANs: *.hibot.com, hibot.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of hibot.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| hibot.com. | 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 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://hibot.com/mcp/public | Verified | 200 | |
| http (plaintext) | http://hibot.com/mcp/public | Inconclusive | 405 |
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 →
generate_ai_visibility_questions AI Visibility Questions ~175
Generate the AI-visibility questions for any brand from its website: the kinds of questions real customers ask ChatGPT, Perplexity, and Google when choosing in that market, mapped to the six ANSWER categories (Appearance, Nomination, Showdown, Worth, Expertise, Reputation). Useful for AEO and GEO research and content planning. It reads the site to infer the brand; pass brandName and description if the site cannot be read automatically.
| Name | Type | Req | Description |
|---|---|---|---|
| brandName | string | – | Optional. Only needed if the site cannot be read automatically (a JavaScript-heavy or very small site). |
| description | string | – | Optional. One line on what the business sells. Only needed if the site cannot be read automatically. |
| website | string | yes | The brand's website or domain, e.g. example.com. Required. |
No output schema declared.
No examples provided.
get_answer_methodology The ANSWER Methodology ~61
The ANSWER framework for measuring AI visibility: the six categories, the 0 to 4 response rubric, category weights, score bands, and the letter-grade scale. Use it to explain what an AI visibility score means and how each category is defined.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_blog_article One HiBot Blog Article ~53
One published HiBot article by slug, rendered as readable Markdown with its canonical URL. Reference reading on AI visibility and the ANSWER framework.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Article slug from list_blog_articles or search_blog. |
No output schema declared.
No examples provided.
list_blog_articles HiBot Blog Articles ~93
Published HiBot articles on AI visibility and the ANSWER framework, newest first, optionally filtered to one ANSWER category. Reference reading.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional ANSWER category slug: general, appearance, nomination, showdown, worth, expertise, or reputation. |
| limit | integer | – | Articles to return. Default 20. |
| offset | integer | – | Articles to skip for paging. Default 0. |
No output schema declared.
No examples provided.
search_blog Search HiBot Articles ~62
Keyword search over published HiBot articles, ranked by relevance, each with its page URL. Reference reading on AI visibility and the ANSWER framework.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results to return. Default 10. |
| query | string | yes | Keywords to search for. |
No output schema declared.
No examples provided.
What is the com.hibot/hibot MCP server?
com.hibot/hibot is an MCP server listed in the public MCP registry as com.hibot/hibot. HiBot public knowledge: the ANSWER framework for AI visibility, audit plans, case studies, research. This page covers its hosted endpoint (https://hibot.com/mcp/public).
Is the com.hibot/hibot MCP server safe to use?
com.hibot/hibot scores 72 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 com.hibot/hibot MCP server expose?
com.hibot/hibot exposes 5 tools: get_answer_methodology, list_blog_articles, get_blog_article, search_blog, generate_ai_visibility_questions. Their descriptions and schemas cost roughly 444 tokens of context every time the server is loaded.
Does the com.hibot/hibot MCP server require authentication?
No. We connected to com.hibot/hibot without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.hibot/hibot MCP server still maintained?
com.hibot/hibot is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.