herohunt-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HEROHUNT_API_KEY | Yes | Your People Search API key | |
| HEROHUNT_MCP_URL | No | Override the MCP endpoint URL | https://api.herohunt.ai/api/v1/mcp |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| people_searchA | Search for people profiles using natural language across LinkedIn, GitHub, and StackOverflow. Credits: 1 per reserved slot up front (default maxResults=100). Enrichment: +1 credit per LinkedIn profile with contact info. |
| people_search_paginateC | Fetch additional pages for an existing search. Free unless enrich is enabled. |
| account_usage_getB | Get plan, total/used/remaining credits, rate limit, and next credit reset date. Free. |
| account_searches_listC | List past searches with first-page profiles. Free. |
| account_upgrade_linkB | Get a dashboard URL prefilled with account email for plan upgrades. Free. |
| account_billing_portal_linkA | Get Stripe Customer Portal URL for managing subscriptions. Free. |
| api_keys_listA | List API key prefixes, scopes, and last-used timestamps. |
| api_keys_createA | Create a new API key. Full key is returned only once. Store it immediately. |
| api_keys_rotateA | Rotate an API key: deactivate old, issue new with same scopes. |
| api_keys_revokeB | Permanently revoke an API key. Irreversible. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Tools are cleanly separated across three domains: people search, account management, and API keys. The two search tools are distinct (initial search vs. pagination), and account and API key tools have clearly different purposes. No overlapping or ambiguous functions.
All tools follow a consistent verb_noun pattern in snake_case, e.g., people_search, account_usage_get, api_keys_create. The naming style is uniform and predictable, with minor but acceptable variation in verbs (get, list, create, etc.).
10 tools is well-scoped for a server combining people search, account management, and API key management. Each tool serves a distinct and necessary function, with no redundancy or excessive granularity.
The set covers core workflows: search with pagination, account usage and history, billing and upgrade links, and full CRUD for API keys. Minor gaps include no direct profile detail retrieval (beyond search results) and no API key scope update (rotate reuses same scopes).