Hackertarget
NPM · @PIPEWORX/MCP-HACKERTARGET · 2 COMPONENTS
HackerTarget MCP.
Available components
Last scanned (13 hours ago)
Scores higher than 81% of npm servers
Category Security
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 Security100
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-hackertarget). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 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 (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1859 tokens (~132/item across 14 items; 14 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 3 Nov 26 +27
- Malware scan: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → pass ▲ functional
- 2 Nov 26 −24
- Malware scan: pass → unverified ▼ security
- Known CVEs: pass → unverified ▼ security
- Dependency health: pass → unverified ▼ functional
- Stability: unverified → 0.13 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 81
First indexed and scored.
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-hackertarget@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-hackertarget |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-hackertarget/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3637387695 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:1c1e54df4c46b562aa90979c6e74a6a589273f84beabad5e82fd8c7a07f1fbf47658e02040cd7945120bc5aed7f2a43d061b69ceb42ec0637f4f57476 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
as_lookup ~101
"Which ASN owns [IP]" / "what network is this address on" / "who is the upstream provider" — autonomous system lookup via HackerTarget, returning the ASN, the announced prefix and the network's name for an address. Use to attribute an address to a hosting provider, ISP or cloud region.
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | IPv4 address or ASN, e.g. "1.1.1.1" or "AS13335". |
No output schema declared.
No examples provided.
dns_host_search ~109
"Subdomains of [domain]" / "what hosts exist under [X]" / "find an admin or staging subdomain" — passive DNS host search via HackerTarget, listing known subdomains of a domain with their IPs, drawn from previously observed DNS data rather than by guessing names. Use for attack-surface inventory or to find a forgotten staging host.
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | Registrable domain to enumerate, e.g. "pipeworx.io" (not a subdomain). |
No output schema declared.
No examples provided.
dns_lookup ~107
"Resolve [domain]" / "what IP does [site] point at" / "A records for [X]" — forward DNS lookup via HackerTarget, returning the A/AAAA/MX/NS/SOA records the resolver holds for a hostname. Use to check where a domain currently points, or to confirm a DNS change has propagated.
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | Hostname to resolve, e.g. "pipeworx.io". Not a URL — strip the scheme and path. |
No output schema declared.
No examples provided.
find_shared_dns ~99
"What else uses this nameserver" / "domains sharing DNS with [X]" — shared-nameserver search via HackerTarget, listing other domains served by the same DNS server. Use to map the infrastructure footprint of an operator, or to see who else would be affected if a nameserver went down.
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | Nameserver hostname or a domain whose nameservers to pivot on, e.g. "ns1.example.com". |
No output schema declared.
No examples provided.
geoip ~112
"Where is [IP] located" / "what country is this address in" / "geolocate an IP" — IP geolocation via HackerTarget, returning country, state/region, city and coordinates for an address. City-level accuracy is approximate and a VPN or CDN address reports its datacenter, not its user. Use for coarse traffic attribution, never to locate a person.
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | IPv4 or IPv6 address, e.g. "104.18.0.1". |
No output schema declared.
No examples provided.
http_headers ~114
"What headers does [site] return" / "what server runs [X]" / "check the security headers" / "does [site] redirect" — HTTP response headers fetched by HackerTarget, including status line, Server, redirect Location, and security headers such as HSTS and CSP. Use to fingerprint a stack or audit header hygiene without loading the page yourself.
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | Hostname or full URL, e.g. "pipeworx.io" or "https://pipeworx.io/". |
No output schema declared.
No examples provided.
mtr ~210
"Network path to [host]" / "where does traffic to [X] slow down" / "per-hop latency" — mtr report via HackerTarget, combining traceroute and ping into a per-hop table of loss and latency measured FROM HackerTarget's probe host, not from you. Use to see which network hop is losing packets. REQUIRES AN API KEY: HackerTarget gates this endpoint, and the keyless tier answers "error valid key required" (verified 2026-09-16).
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Your HackerTarget API key, from the member dashboard. HackerTarget requires an API key for whois, mtr and traceroute — its free tier refuses those three with "error valid key required". Pipeworx supp… |
| target | string | yes | Hostname or IP to trace to, e.g. "1.1.1.1". |
No output schema declared.
No examples provided.
nping ~104
"Is [host] up" / "ping [X]" / "round-trip time to [address]" — ICMP ping via HackerTarget, reporting reachability and round-trip time from HackerTarget's probe host. Use for a liveness check when you cannot ping from where you are. A host that blocks ICMP reads as down even when it serves traffic.
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | Hostname or IP to ping, e.g. "pipeworx.io". |
No output schema declared.
No examples provided.
page_links ~117
"What does [page] link to" / "extract every link from [URL]" / "outbound links on a page" — link extraction via HackerTarget, fetching one web page and returning the URLs it links to. Use to map a site section or find outbound references. One page only — it does not crawl, and it returns the links as published, not their fetched status.
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | Full URL of the page to read, e.g. "https://pipeworx.io/". Include the scheme. |
No output schema declared.
No examples provided.
reverse_dns ~107
"What hostname is [IP]" / "reverse DNS for [address]" / "PTR record lookup" — reverse DNS (PTR) lookup via HackerTarget, mapping an IP address back to the hostname its owner published. Use to identify the operator behind an address in a log line. Returns nothing when no PTR record is set, which is common for cloud IPs.
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | IPv4 or IPv6 address, e.g. "8.8.8.8". |
No output schema declared.
No examples provided.
reverse_ip ~104
"What else is hosted on [IP]" / "other sites on the same server" / "reverse IP lookup" — reverse IP lookup via HackerTarget, listing hostnames known to resolve to one address. Use to spot shared hosting or to find sibling properties of an operator. A CDN address returns many unrelated sites, so co-location is not evidence of common ownership.
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | IPv4 address, e.g. "104.18.0.1". |
No output schema declared.
No examples provided.
subnet_lookup ~115
"What is the range of [CIDR]" / "how many hosts in a /24" / "network and broadcast address for [X]" / "subnet calculator" — subnet arithmetic via HackerTarget, returning network address, broadcast address, usable host range, netmask and host count for a CIDR block. A pure calculation over the input; it does not probe the network.
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | CIDR block or address with prefix, e.g. "192.168.1.0/24". |
No output schema declared.
No examples provided.
traceroute ~196
"Traceroute to [host]" / "what route does traffic take to [X]" / "how many hops to [address]" — traceroute via HackerTarget, listing the routers between HackerTarget's probe host and the target. The path is measured from their network, not yours. REQUIRES AN API KEY: HackerTarget gates this endpoint, and the keyless tier answers "error valid key required" (verified 2026-09-16).
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Your HackerTarget API key, from the member dashboard. HackerTarget requires an API key for whois, mtr and traceroute — its free tier refuses those three with "error valid key required". Pipeworx supp… |
| target | string | yes | Hostname or IP to trace to, e.g. "pipeworx.io". |
No output schema declared.
No examples provided.
whois ~209
"Who owns [domain]" / "when does [X] expire" / "whois lookup" / "registrar for [site]" — WHOIS record via HackerTarget for a domain or IP: registrar, creation and expiry dates, nameservers, and whatever contact fields the registry still publishes. REQUIRES AN API KEY: HackerTarget gates this endpoint, and the keyless tier answers "error valid key required" (verified 2026-09-16). For keyless WHOIS use ripe_stat_whois.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Your HackerTarget API key, from the member dashboard. HackerTarget requires an API key for whois, mtr and traceroute — its free tier refuses those three with "error valid key required". Pipeworx supp… |
| target | string | yes | Domain name or IP address, e.g. "pipeworx.io". |
No output schema declared.
No examples provided.
How do I install the Hackertarget MCP server?
Hackertarget runs locally as an npm package, launched with npx -y @pipeworx/mcp-hackertarget. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-hackertarget
claude mcp add pipeworx-io-hackertarget -- npx -y @pipeworx/mcp-hackertarget
What is the Hackertarget MCP server?
Hackertarget is an MCP server listed in the public MCP registry as io.github.pipeworx-io/hackertarget. HackerTarget MCP. This page covers its npm package (@pipeworx/mcp-hackertarget).
Is the Hackertarget MCP server safe to use?
Hackertarget scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Hackertarget MCP server expose?
Hackertarget exposes 14 tools: dns_lookup, reverse_dns, mtr, nping, dns_host_search, and 9 more. Their descriptions and schemas cost roughly 1,804 tokens of context every time the server is loaded.
Is the Hackertarget MCP server still maintained?
Hackertarget is still listed as active in the MCP registry. We last reached this channel on 5 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 Hackertarget MCP server under?
Hackertarget declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Hackertarget MCP server?
VerifyMCP ran 16 checks on Hackertarget, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.