h1-hacker-mcp

Overview Schema Source Related Servers Discussions Admin

search_hacktivity

Read-onlyIdempotent

Search publicly disclosed HackerOne hacktivity reports with Lucene queries and filters like severity, asset, CWE, CVE, reporter, team, award, and date. Sort by activity, disclosure, bounty, or votes.

Instructions

Search publicly disclosed hacktivity reports.

query is an Apache Lucene query. Filters: severity_rating, asset_type,
substate, cwe, cve_ids, reporter, team, total_awarded_amount, disclosed_at,
has_collaboration, disclosed. Example:
severity_rating:critical AND disclosed_at:>=01-01-1970.
sort is latest_disclosable_activity_at, disclosed_at, total_awarded_amount,
or votes. Prefix with - for descending order. The API default is
-latest_disclosable_activity_at.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`sort`	No
`query`	No
`page_size`	No
`page_number`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 3, 2026

TDQS

A3.7/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), so the bar is lower. The description still adds real behavioral context beyond them: the API's default sort order, the '-' prefix convention for descending sort, and the Lucene query dialect. It omits pagination behavior and result-size limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose, then filters, then sort semantics. Each sentence carries information and there is no filler, though the filter list is a dense run-on that could be formatted more scannably.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described. Query and sort semantics are well covered, and pagination parameters have usable defaults in the schema (25/1). The only real gap is the absence of any explicit pagination semantics, which keeps it from a 5.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must carry the load. It does well for query (Apache Lucene syntax plus a concrete example) and sort (four allowed values, '-' for descending, documented default), but page_size and page_number receive no explanation at all in either the schema or the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Search publicly disclosed hacktivity reports.' The word 'publicly disclosed' implicitly distinguishes it from the account-scoped siblings (list_my_reports, get_report), but no sibling is named explicitly, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the filter list and the Lucene example, which tell an agent what can be searched, but there is no explicit 'use this when / use X instead' guidance and no mention of when a scoped tool like list_my_reports would be preferable.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server