_ registry / mcp streamable-http · checked 13m ago

hibot-public

https://hibot.com

Registry code: a5e128c047d5c4fd

api record

Tools for measuring and researching AI visibility: how AI answer engines (ChatGPT, Perplexity, Google, Claude, Grok) surface, recommend, and represent brands, using the ANSWER framework. Use them to explain the methodology and its scoring, read and search HiBot's published research articles, and generate the AI-visibility questions customers ask about any brand from its website (generate_ai_visibility_questions), mapped to the six ANSWER categories. Everything returns already-published material or generated questions; nothing here queries an AI engine live or scores anything. HiBot is a…

endpoint
https://hibot.com/mcp/public
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is hibot-public live?
Yes — it answered the hub's last check (checked 13m ago). It answered 99% of checks over the last 30 days.
Is hibot-public free to use?
Yes — the hub reached it with no key and no payment.
What tools does hibot-public have?
5 tools: generate_ai_visibility_questions, search_blog, get_blog_article, get_answer_methodology, list_blog_articles.
Is hibot-public safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
98.7%

90 days 99.3%· all time 99.3%

latency
502ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 285 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • unknown → live
_ what it is for
used for
  • generate ai visibility questions for a brand
  • read the ai visibility scoring methodology
  • search articles on ai visibility
takes → gives
text, web pages → text, data
tools
5 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 5 tools
2 open 3 never probed 2 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_answer_methodology reads open 14h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • list_blog_articles reads open 14h ago

    Published HiBot articles on AI visibility and the ANSWER framework, newest first, optionally filtered to one ANSWER category. Reference reading.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 50,
          "minimum": 1,
          "description": "Articles to return. Default 20."
        },
        "offset": {
          "type": "integer",
          "minimum": 0,
          "description": "Articles to skip for paging. Default 0."
        },
        "category": {
          "type": "string",
          "description": "Optional ANSWER category slug: general, appearance, nomination, showdown, worth, expertise, or reputation."
        }
      },
      "additionalProperties": false
    }
    arguments 21 lines
  • generate_ai_visibility_questions reads unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "website"
      ],
      "properties": {
        "website": {
          "type": "string",
          "description": "The brand's website or domain, e.g. example.com. Required."
        },
        "brandName": {
          "type": "string",
          "description": "Optional. Only needed if the site cannot be read automatically (a JavaScript-heavy or very small site)."
        },
        "description": {
          "type": "string",
          "description": "Optional. One line on what the business sells. Only needed if the site cannot be read automatically."
        }
      },
      "additionalProperties": false
    }
    arguments 21 lines
  • search_blog reads unknown 11h ago

    Keyword search over published HiBot articles, ranked by relevance, each with its page URL. Reference reading on AI visibility and the ANSWER framework.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 20,
          "minimum": 1,
          "description": "Results to return. Default 10."
        },
        "query": {
          "type": "string",
          "description": "Keywords to search for."
        }
      },
      "additionalProperties": false
    }
    arguments 19 lines
  • get_blog_article reads unknown 14h ago

    One published HiBot article by slug, rendered as readable Markdown with its canonical URL. Reference reading on AI visibility and the ANSWER framework.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "Article slug from list_blog_articles or search_blog."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id a5e128c047d5c4fd.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/a5e128c047d5c4fd/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/a5e128c047d5c4fd/badge.svg)](https://brick.blue/agent/a5e128c047d5c4fd?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.