Skip to main content
Glama
GreyNoise-Intelligence

greynoise-mcp-server

Official

List Callback IPs

list-callback-ips
Read-only

Retrieve a paginated list of callback and C2 IPs filtered by attack stage, file attributes, date ranges, and scanner IPs.

Instructions

Paginated list of callback/C2 IPs filtered by attack stage, first/last seen date ranges, file attributes, and scanner associations. Dates are YYYY-MM-DD.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ipsNoFilter to this specific set of callback IPs
pageNoZero-indexed page number (default 0)
file_hashNoFile SHA256 hash
file_nameNoFile name substring match
file_typeNoFile MIME type (e.g. "application/x-executable")
has_filesNotrue = only IPs with malware files; false = only IPs without files
page_sizeNoResults per page, 1-100 (default 20)
is_stage_1Notrue = file was downloaded from this IP (stage 1)
is_stage_2Notrue = suspected C2 based on VT/sandbox analysis (stage 2)
scanner_ipsNoFilter to IPs associated with these scanner IPs
last_seen_afterNoOnly IPs last seen after this date (YYYY-MM-DD)
first_seen_afterNoOnly IPs first seen after this date (YYYY-MM-DD)
last_seen_beforeNoOnly IPs last seen before this date (YYYY-MM-DD)
first_seen_beforeNoOnly IPs first seen before this date (YYYY-MM-DD)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
itemsNo
totalNo
page_sizeNo
Behavior4/5

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

Annotations declare readOnlyHint=true and openWorldHint=true. The description adds context about pagination, date format (YYYY-MM-DD), and filter options, which goes beyond the annotations by clarifying the tool's operational behavior (e.g., paginated, filterable).

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

Conciseness5/5

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

Single sentence that front-loads the purpose and then efficiently lists filter categories. Every word earns its place; no redundancy.

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

Completeness5/5

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

Given the tool's complexity (14 optional parameters) and the presence of an output schema, the description adequately summarizes the tool's functionality. The output schema covers return values, and the annotation indicates safe read-only behavior, so no further behavioral details are necessary.

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 description coverage is 100%, so schema already documents all 14 parameters. The description adds marginal value by grouping filters into categories (attack stage, dates, file attributes, scanner associations) and specifying date format, but does not explain parameter interaction or defaults beyond schema.

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

Purpose5/5

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

The description clearly states it is a 'paginated list of callback/C2 IPs' with specific filters (attack stage, dates, file attributes, scanner associations). It distinguishes itself from sibling tools like 'lookup-ip-context' or 'get-blocklist-ips' by focusing on filtered, paginated lists.

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?

The description implies usage for listing IPs with various filters but does not explicitly mention when to use this tool versus alternatives (e.g., lookup-ip-context for single IP details). No guidance on exclusions or preferred use cases.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/GreyNoise-Intelligence/greynoise-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server