← Registry tracker
Claude Connector

HoverBot

See what your chatbots could not answer this week

View in the Claude registry
Category
Pending
Primary Subcategory
Pending
Integration details

Description

HoverBot is an AI chatbot platform that answers customer questions from a company's own catalog, policies, and documentation. This connector gives an assistant read-only access to one HoverBot workspace, so the people who run a support bot can ask about it in plain language instead of reading dashboards. It answers questions like: what did shoppers ask about returns last week that the bot could not answer, how does this week's conversation volume compare to last week's, and which knowledge sources mention the refund window. Nine tools are available. list_chatbots and get_chatbot return the bots in the workspace and one bot's configuration, including its system prompt and knowledge libraries. list_knowledge_sources and search_knowledge cover the files, links, text and question-and-answer pairs that ground its replies. list_conversations and get_conversation return recent shopper conversations and full transcripts, with the retrieval confidence for each turn. get_unanswered_questions reports questions the bot answered from weak grounding and questions that produced no answer at all, each with its conversation id. get_analytics_summary returns conversation and message volume, active sessions, response rate and average response time, this week against last. list_leads returns the contact details the bots captured. Every tool is read-only. The connector cannot change a chatbot, edit a knowledge base, contact a lead, or alter any setting. Access is granted by signing in to HoverBot, or by a token created in the dashboard. Either way the grant fixes which workspace the connector can read. The workspace is never taken from a tool argument, so a connector cannot reach another customer's data. Tokens are listed in the dashboard with the time each was last used, and revoking one takes effect on the next request. search_knowledge matches keywords rather than meaning; the chatbot's own answering uses semantic retrieval, and this tool does not.

Integration type
Connector
Verification status
Community connector
Platform
Claude
Category
Pending

The broad Category that contains the Primary Subcategory.

Primary Subcategory
Pending

The Primary Subcategory used for this profile’s headline score.

Secondary Subcategories
None listed

Other Subcategories where the Integration is listed.

Access
Account required
First tracked
2026-10-05
Tool count
9
Geography
US
Agent DiscoverabilityClaude Discoverability Score

Claude Connector discovery is coming soon

Community Connectors only appear in Claude’s registry.Once verified, organic discovery begins and we can calculate your score.Read more about Community Connector verification.

No spam. Unsubscribe any time.

No spam. Unsubscribe any time.

What discovery looks like

Claude showing a list of relevant Connectors in a conversation

Claude can surface verified Connectors when they match a user’s Prompt.

Primary Subcategory

Competitive lineup

No Primary Subcategory assigned yetOnce HoverBot has a Primary Subcategory, the Plugins and Connectors it competes with will appear here with their scores.
Tools

9 tools agents can invoke

Recommended guideHow to get your Claude Connector organically discoveredFollow the practical steps agents use to find, shortlist, and choose your Connector.Read guide
FAQs

HoverBot Claude Connector FAQ

How the directory, categories and Discoverability Score work.

Read the methodology
How do I improve HoverBot's Claude Connector discoverability?

The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.

Where is this profile measured?

This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.