io.github.herohunt-ai/herohunt-mcp
NPM · HEROHUNT-MCP
People search API - find 1 billion candidates across LinkedIn and GitHub with real-time data.
Available components
Last scanned (21 hours ago)
Scores higher than 55% of npm servers
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 176 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 630 tokens (~63/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "api_keys_revoke" implies "revoke" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 −2
- Stability: pass → 0.90 functional
- 28 Oct 26 +1
- Stability: 0.97 → pass security
- 27 Oct 26 −1
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 21 Oct 26 +1
- Stability: 0.97 → pass security
- 20 Oct 26 −1
- Stability: pass → 0.97 functional
- 17 Oct 26 +3
- Stability: 0.83 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed npm/herohunt-mcp@1.0.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
account_billing_portal_link ~23
Get Stripe Customer Portal URL for managing subscriptions. Free.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
account_searches_list ~86
List past searches with first-page profiles. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| includeLogs | boolean | – | Include pipeline logs. |
| limit | integer | – | Number of past searches (default 20). |
| page | integer | – | History page. |
| per_search_page | integer | – | Profiles per past search (default 10). |
| returnAllProfiles | boolean | – | Include all profiles per search. |
No output schema declared.
No examples provided.
account_upgrade_link ~24
Get a dashboard URL prefilled with account email for plan upgrades. Free.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
account_usage_get ~30
Get plan, total/used/remaining credits, rate limit, and next credit reset date. Free.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
api_keys_create ~76
Create a new API key. Full key is returned only once. Store it immediately.
| Name | Type | Req | Description |
|---|---|---|---|
| expiresAt | string | – | ISO-8601 expiry date (optional). |
| name | string | yes | Friendly name for the key (e.g. "CI Bot"). |
| scopes | array | – | Permission scopes. Defaults to people:search. |
No output schema declared.
No examples provided.
api_keys_list ~21
List API key prefixes, scopes, and last-used timestamps.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
api_keys_revoke ~35
Permanently revoke an API key. Irreversible.
| Name | Type | Req | Description |
|---|---|---|---|
| keyId | string | yes | ID of the key to revoke. |
No output schema declared.
No examples provided.
api_keys_rotate ~37
Rotate an API key: deactivate old, issue new with same scopes.
| Name | Type | Req | Description |
|---|---|---|---|
| keyId | string | yes | ID of the key to rotate. |
No output schema declared.
No examples provided.
people_search ~201
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.
| Name | Type | Req | Description |
|---|---|---|---|
| enrich | boolean | – | Request email/phone enrichment for LinkedIn profiles. |
| filters | object | – | Structured filters. |
| includeLogs | boolean | – | Include pipeline trace logs. |
| maxResults | integer | – | Max profiles to collect (default 100). Charged up front. |
| page | integer | – | Page number. |
| per_page | integer | – | Results per page (max 50, default 10). |
| query | string | – | Natural language query. Required for new searches. |
| returnAllProfiles | boolean | – | Return all matched profiles, not just current page. |
| searchId | string | – | Existing search ID for pagination. |
| timeoutMs | integer | – | Max wait time in ms. |
No output schema declared.
No examples provided.
people_search_paginate ~97
Fetch additional pages for an existing search. Free unless enrich is enabled.
| Name | Type | Req | Description |
|---|---|---|---|
| enrich | boolean | – | Request enrichment (+1 credit per enriched profile). |
| includeLogs | boolean | – | Include pipeline logs. |
| page | integer | – | Page number. |
| per_page | integer | – | Results per page. |
| returnAllProfiles | boolean | – | Return all matched profiles. |
| searchId | string | yes | ID of existing search to paginate. |
No output schema declared.
No examples provided.
How do I install the io.github.herohunt-ai/herohunt-mcp server?
io.github.herohunt-ai/herohunt-mcp runs locally as an npm package, launched with npx -y herohunt-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · herohunt-mcp
claude mcp add herohunt-ai-herohunt-mcp -- npx -y herohunt-mcp
What is the io.github.herohunt-ai/herohunt-mcp server?
io.github.herohunt-ai/herohunt-mcp is listed in the public MCP registry as io.github.herohunt-ai/herohunt-mcp. People search API - find 1 billion candidates across LinkedIn and GitHub with real-time data. This page covers its npm package (herohunt-mcp).
Is the io.github.herohunt-ai/herohunt-mcp server safe to use?
io.github.herohunt-ai/herohunt-mcp scores 77 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.herohunt-ai/herohunt-mcp server expose?
io.github.herohunt-ai/herohunt-mcp exposes 10 tools: people_search, people_search_paginate, account_usage_get, account_searches_list, account_upgrade_link, and 5 more. Their descriptions and schemas cost roughly 630 tokens of context every time the server is loaded.
Is the io.github.herohunt-ai/herohunt-mcp server still maintained?
io.github.herohunt-ai/herohunt-mcp is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.herohunt-ai/herohunt-mcp server under?
io.github.herohunt-ai/herohunt-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.