greynoise-mcp-server

Official

by GreyNoise-Intelligence

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

List Blocklists

list-blocklists

Read-only

Retrieve blocklists from a GreyNoise workspace with pagination controls to review blocked indicators and manage workspace blocklists.

Instructions

List the blocklists in a workspace.

Input Schema

Name	Required	Description
`limit`	No	Max blocklists to return (1-100)
`offset`	No	Pagination offset
`workspace_id`	No	Workspace ID (UUID). Defaults to the workspace the API key is bound to.

Output Schema

Name	Required	Description	Default
`limit`	No
`total`	No
`offset`	No
`blocklists`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.5.5Nov 2, 2026
- removedOutput schema / properties / blocklists / items / properties / ip_limit / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / blocklists / items / properties / ip_limit / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / blocklists / items / properties / name / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / blocklists / items / properties / name / type
```
Added value: +[
+  "string",
+  "null"
+]
```
Addedv0.5.3Jul 21, 2026

TDQS

B3.3/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered, but the description adds no context of its own: nothing about default result size, pagination behavior, or ordering. It neither contradicts nor enriches the structured metadata.

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?

A single front-loaded sentence with zero waste and no filler. It is appropriately sized, though its brevity borders on under-specification rather than crispness.

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?

The tool is simple: no required params, full schema coverage, an output schema that documents return values, and annotations covering the safety profile. The description is sufficient to invoke it correctly; only the relationship to get-blocklist and pagination expectations are left unstated.

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% and all three parameters (limit, offset, workspace_id) carry their own descriptions including defaults and ranges, so the schema does the heavy lifting. The description contributes nothing about parameters, which is acceptable at baseline but no more.

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 states a specific verb ('List') and resource ('blocklists') with scope ('in a workspace'), so an agent knows exactly what it returns. It does not, however, distinguish itself from the sibling get-blocklist (single retrieval) or get-blocklist-ips, leaving the collection-vs-single distinction implicit.

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 only implied by the verb 'List' and the workspace scope; there is no explicit when-to-use, no exclusion, and no pointer to get-blocklist for single-record lookups. An agent can infer it is the enumeration endpoint, but must reason about alternatives itself.

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

Deploy Server