Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.herohunt-ai/herohunt-mcp

NPM · HEROHUNT-MCP · SCANNED SEP 20

People search API - find 1 billion candidates across LinkedIn and GitHub with real-time data.

Available components

0 this week 81 Trust /100
Trust breakdown (7 categories)

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 Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
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 Management90
  • Stability observed for 27 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
Install

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

# add to Claude Code
claude mcp add herohunt-ai-herohunt-mcp -- npx -y herohunt-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "herohunt-ai-herohunt-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "herohunt-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "herohunt-ai-herohunt-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "herohunt-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add herohunt-ai-herohunt-mcp -- npx -y herohunt-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "herohunt-ai-herohunt-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "herohunt-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add herohunt-ai-herohunt-mcp --command npx --arg -y --arg herohunt-mcp
# ~/.hermes/config.yaml
mcp_servers:
  herohunt-ai-herohunt-mcp:
    command: "npx"
    args: ["-y", "herohunt-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "herohunt-ai-herohunt-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "herohunt-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add herohunt-ai-herohunt-mcp -t stdio -c npx -a -y herohunt-mcp
// mcp.json
{
  "mcpServers": {
    "herohunt-ai-herohunt-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "herohunt-mcp"
      ]
    }
  }
}
Changelog

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.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 16 Sept 26 +1
    • Stability: 0.97 → pass security
  • 14 Sept 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.

  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 9 Sept 26 +1
    • Stability: 0.97 → pass security
  • 7 Sept 26 +1
    • Security disclosure: unverified → fail functional
Diagnostics

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 20 Sept 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 →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 10 exposed · ~630 tokens

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 →

Tool Tokens
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.

NameTypeReqDescription
includeLogsbooleanInclude pipeline logs.
limitintegerNumber of past searches (default 20).
pageintegerHistory page.
per_search_pageintegerProfiles per past search (default 10).
returnAllProfilesbooleanInclude 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.

NameTypeReqDescription
expiresAtstringISO-8601 expiry date (optional).
namestringyesFriendly name for the key (e.g. "CI Bot").
scopesarrayPermission 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.

NameTypeReqDescription
keyIdstringyesID 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.

NameTypeReqDescription
keyIdstringyesID 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.

NameTypeReqDescription
enrichbooleanRequest email/phone enrichment for LinkedIn profiles.
filtersobjectStructured filters.
includeLogsbooleanInclude pipeline trace logs.
maxResultsintegerMax profiles to collect (default 100). Charged up front.
pageintegerPage number.
per_pageintegerResults per page (max 50, default 10).
querystringNatural language query. Required for new searches.
returnAllProfilesbooleanReturn all matched profiles, not just current page.
searchIdstringExisting search ID for pagination.
timeoutMsintegerMax 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.

NameTypeReqDescription
enrichbooleanRequest enrichment (+1 credit per enriched profile).
includeLogsbooleanInclude pipeline logs.
pageintegerPage number.
per_pageintegerResults per page.
returnAllProfilesbooleanReturn all matched profiles.
searchIdstringyesID of existing search to paginate.

No output schema declared.

No examples provided.

Common questions

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 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 20 September 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.