com.hibot/hibot
com.hibot/hibot · 1.0.0
HiBot public knowledge: the ANSWER framework for AI visibility, audit plans, case studies, research
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 45 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 0 of 15 | The registry entry declares no key. That is what it declares, not a finding that it has no protection. |
| Latest connection test reached it | 20 of 20 |
Where it answers
https://hibot.com/mcp/publicstreamable-http
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 5 tools.
- Protocol
- 2025-06-18
- Calls itself
- hibot-public 1.0.0
- Handshake time
- 151 ms
- HTTP status
- 200
The tools it lists (5, as of 4 days ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
get_answer_methodologyThe 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.
list_blog_articlesPublished HiBot articles on AI visibility and the ANSWER framework, newest first, optionally filtered to one ANSWER category. Reference reading.
get_blog_articleOne published HiBot article by slug, rendered as readable Markdown with its canonical URL. Reference reading on AI visibility and the ANSWER framework.
search_blogKeyword search over published HiBot articles, ranked by relevance, each with its page URL. Reference reading on AI visibility and the ANSWER framework.
generate_ai_visibility_questionsGenerate 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.
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
com.hibot/hibot, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 36 days ago. The registry entry · hibot.com