HiBot MCP Servers

HiBot speaks the Model Context Protocol, the open standard AI assistants use to reach outside data. Two servers are available: a public one anyone can connect, and a private one that serves your own audit results to the agent doing the fixing.

Both servers hand out data HiBot has already captured and scored. Our audits are run by human specialists in logged-out, neutral sessions, so no tool here queries an AI engine, checks your visibility live, or re-scores anything. If you want fresh numbers, that takes a new audit.

The Public Server

URL: https://hibot.com/mcp/public (no authentication)

Made for any AI user who wants HiBot's public knowledge: the ANSWER methodology and its scoring rubric, the Pulse and Panorama plans, our published case studies, and the blog. Every result links back to the page it came from on hibot.com.

  • get_answer_methodology: the six ANSWER categories, rubric, weights, and score bands
  • get_plans: Pulse and Panorama pricing and what each report includes
  • list_case_studies and get_case_study: real audits of brands like Oura and Costco
  • list_blog_articles, get_blog_article, and search_blog: our published research

The Private Server

URL: https://hibot.com/mcp (Bearer API key)

Your delivered audits as a dataset an agent can work from: scores and dimensions, the word-for-word answers each engine gave, the claims log, citations, competitive standing, and trends across re-audits. Your agent can also record progress on each recommendation and log dated notes on your timeline, so the next audit reads against what you actually changed. HiBot measures; your agent implements.

Keys are minted on the API Keys page in your account. Each key is shown once, is stored only as a hash, and can be revoked at any time. A key reads the account it belongs to and nothing else.

Connecting From Claude Code

> claude mcp add --transport http hibot-public https://hibot.com/mcp/public
> claude mcp add --transport http hibot https://hibot.com/mcp \
    --header "Authorization: Bearer hb_live_..."

Any MCP client that supports HTTP transport with custom headers works the same way. Requests are JSON-RPC 2.0 over POST; both servers are rate limited.

Ground Rules

  • Reports are private client data. The private server authenticates every call and serves only the key owner's own delivered audits.
  • Write tools touch your own tracking metadata (progress status, notes) and never the stored findings, scores, or recommendations.
  • Trend data reports observed differences between runs, lined up with your timeline notes. AI answers are noisy, so we never claim one change caused another.

Questions? Write to [email protected]. Not a customer yet? Get your first audit.

Connect our AI visibility playbook to your AI