Skip to main content
Glama

Server Details

HackerTarget MCP.

The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
0.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-hackertarget
GitHub Stars
0
Server Listing
HackerTarget MCP
ChatGPT
–
Claude
–

TDQS

A3.8/5.0

Scored across 58 tools

Disambiguation3/5

Many tools are clearly distinct (dns_lookup vs reverse_ip vs geoip), but several clusters overlap heavily: ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded / deep_research / discover_tools / suggest_questions all occupy the 'route my question' space, and ask_pipeworx_beta is documented as currently behaving exactly like ask_pipeworx. The prediction-market family (polymarket_edges, polymarket_arbitrage, polymarket_fill_risk, polymarket_edge_tracker, polymarket_kalshi_spread, bet_research, release_calendar_markets, kalshi_weather_edge, prediction_calibration, updown_venue_compare, updown_divergence_rate) has real boundary blur, e.g. partition-overround scanning appears in both polymarket_edges and polymarket_arbitrage. Long descriptions do explicitly route the agent ('prefer over', 'use X when'), which is why this lands at 3 rather than lower.

Naming Consistency3/5

Everything is snake_case, which is good, but the construction varies: verb-first (resolve_entity, compare_entities, validate_claim, scan_dependency, generate_llms_txt), noun-first (dns_lookup, as_lookup, subnet_lookup, kalshi_weather_edge, polymarket_edges), suffixed (ai_visibility_check), and bare single words (whois, geoip, mtr, nping, traceroute, recall, forget, subscribe). The mixed verb/noun-first pattern plus bare-noun legacy network tools keeps it at 'readable but inconsistent'.

Tool Count2/5

58 tools is well beyond the 15-tool band where an agent can hold the surface in mind, and the set spans at least six unrelated domains (network recon, SEC/company research, prediction markets, AI visibility, npm dependency scanning, agent memory/subscriptions). Each tool may earn its place individually, but the aggregate is too large for reliable selection without repeated discovery calls.

Completeness3/5

Within each sub-domain coverage is actually strong and lifecycle-complete: memory has remember/recall/forget, subscriptions have subscribe/list/unsubscribe/recent_alerts, companies have resolve/profile/facts/compare/changes/register-search, DNS/network has forward, reverse, ASN, subnet, WHOIS, headers, traceroute, ping. The gap is at the set level — there is no general-purpose 'fetch this URL' or web-search primitive exposed (fetch_url is only referenced as an internal dependency), and the branded 'Hackertarget' scope is not what the tool surface actually covers, so the boundary of the domain is undefined and 'complete' cannot be meaningfully satisfied.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.