blockscout-mcp-server

Get Transactions by Address

get_transactions_by_address

Read-only

Retrieves native currency transfers and smart contract interactions (calls, internal txs) for an address.
**EXCLUDES TOKEN TRANSFERS**: Filters out direct token balance changes (ERC-20, etc.). You'll see calls *to* token contracts, but not the `Transfer` events. For token history, use `get_token_transfers_by_address`.
A single tx can have multiple records from internal calls.
Requires an `age_from` date to scope results for performance and relevance.
**SUPPORTS PAGINATION**: If response includes 'pagination' field, use the provided next_call to get additional pages.

Input Schema

TableJSON Schema

Name	Required	Description
`age_to`	No	End date and time (e.g 2025-05-22T22:30:00.00Z). Adding this bounds the upper end of the date range started by `age_from`.
`cursor`	No	The pagination cursor from a previous response to get the next page of results.
`address`	Yes	Address which either sender or receiver of the transaction
`methods`	No	A method signature to filter transactions by (e.g 0x304e6ade). Filters the (optionally date-bounded) results to a specific method signature.
`age_from`	Yes	Start date and time (e.g 2025-05-22T23:00:00.00Z). Alone, returns all transactions to/from the address since this date.
`chain_id`	Yes	The ID of the blockchain
`session_id`	No	Opaque session identifier.

Output Schema

TableJSON Schema

Name	Required	Description
`data`	Yes	The main data payload of the tool's response.
`notes`	No	A list of important contextual notes, such as warnings about data truncation or data quality issues.
`pagination`	No	Pagination information, present only if the 'data' is a single page of a larger result set.
`content_text`	No	Optional human-readable summary used for MCP content responses.
`instructions`	No	A list of suggested follow-up actions or instructions for the LLM to plan its next steps.
`data_description`	No	A list of notes explaining the structure, fields, or conventions of the 'data' payload.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 10, 2026

changedInput schema / properties / age_from / description

Previous value: -"Start date and time (e.g 2025-05-22T23:00:00.00Z)."New value: +"Start date and time (e.g 2025-05-22T23:00:00.00Z). Alone, returns all transactions to/from the address since this date."

changedInput schema / properties / age_to / description

Previous value: -"End date and time (e.g 2025-05-22T22:30:00.00Z)."New value: +"End date and time (e.g 2025-05-22T22:30:00.00Z). Adding this bounds the upper end of the date range started by `age_from`."

changedInput schema / properties / methods / description

Previous value: -"A method signature to filter transactions by (e.g 0x304e6ade)"New value: +"A method signature to filter transactions by (e.g 0x304e6ade). Filters the (optionally date-bounded) results to a specific method signature."

addedInput schema / properties / session_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Opaque session identifier.",
+  "title": "Session Id"
+}

Changed24 schema fields changedMay 1, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

removedInput schema / additionalProperties
```
Removed value: -false
```

changedInput schema / properties / address / description

Previous value: -"Address to query"New value: +"Address which either sender or receiver of the transaction"

addedInput schema / properties / address / title
```
Added value: +"Address"
```

changedInput schema / properties / age_from / description

Previous value: -"Start date/time (ISO 8601)"New value: +"Start date and time (e.g 2025-05-22T23:00:00.00Z)."

addedInput schema / properties / age_from / title
```
Added value: +"Age From"
```

addedInput schema / properties / age_to / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / age_to / default
```
Added value: +null
```

changedInput schema / properties / age_to / description

Previous value: -"End date/time (ISO 8601)"New value: +"End date and time (e.g 2025-05-22T22:30:00.00Z)."

addedInput schema / properties / age_to / title
```
Added value: +"Age To"
```
removedInput schema / properties / age_to / type
```
Removed value: -"string"
```
addedInput schema / properties / chain_id / title
```
Added value: +"Chain Id"
```

addedInput schema / properties / cursor / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / cursor / default
```
Added value: +null
```

changedInput schema / properties / cursor / description

Previous value: -"Pagination cursor"New value: +"The pagination cursor from a previous response to get the next page of results."

addedInput schema / properties / cursor / title
```
Added value: +"Cursor"
```
removedInput schema / properties / cursor / type
```
Removed value: -"string"
```

addedInput schema / properties / methods / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / methods / default
```
Added value: +null
```

changedInput schema / properties / methods / description

Previous value: -"Method signature filter (e.g. 0x304e6ade)"New value: +"A method signature to filter transactions by (e.g 0x304e6ade)"

addedInput schema / properties / methods / title
```
Added value: +"Methods"
```
removedInput schema / properties / methods / type
```
Removed value: -"string"
```

addedInput schema / title

Added value: +"get_transactions_by_addressArguments"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "AdvancedFilterItem": {
+      "additionalProperties": true,
+      "description": "Represents a single item from the advanced filter API response.",
+      "properties": {
+        "from": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null,
+          "description": "The sender address.",
+          "title": "From"
+        },
+        "to": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null,
+          "description": "The recipient address.",
+          "title": "To"
+        }
+      },
+      "title": "AdvancedFilterItem",
+      "type": "object"
+    },
+    "NextCallInfo": {
+      "description": "A structured representation of the tool call required to get the next page.",
+      "properties": {
+        "params": {
+          "additionalProperties": true,
+          "description": "A complete dictionary of parameters for the next tool call, including the new cursor.",
+          "title": "Params",
+          "type": "object"
+        },
+        "tool_name": {
+          "description": "The name of the tool to call for the next page.",
+          "title": "Tool Name",
+          "type": "string"
+        }
+      },
+      "required": [
+        "tool_name",
+        "params"
+      ],
+      "title": "NextCallInfo",
+      "type": "object"
+    },
+    "PaginationInfo": {
+      "description": "Contains the structured information needed to retrieve the next page of results.",
+      "properties": {
+        "next_call": {
+          "$ref": "#/$defs/NextCallInfo",
+          "description": "The structured tool call required to fetch the subsequent page."
+        }
+      },
+      "required": [
+        "next_call"
+      ],
+      "title": "PaginationInfo",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "content_text": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "description": "Optional human-readable summary used for MCP content responses.",
+      "title": "Content Text"
+    },
+    "data": {
+      "description": "The main data payload of the tool's response.",
+      "items": {
+        "$ref": "#/$defs/AdvancedFilterItem"
+      },
+      "title": "Data",
+      "type": "array"
+    },
+    "data_description": {
+      "anyOf": [
+        {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "description": "A list of notes explaining the structure, fields, or conventions of the 'data' payload.",
+      "title": "Data Description"
+    },
+    "instructions": {
+      "anyOf": [
+        {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "description": "A list of suggested follow-up actions or instructions for the LLM to plan its next steps.",
+      "title": "Instructions"
+    },
+    "notes": {
+      "anyOf": [
+        {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "description": "A list of important contextual notes, such as warnings about data truncation or data quality issues.",
+      "title": "Notes"
+    },
+    "pagination": {
+      "anyOf": [
+        {
+          "$ref": "#/$defs/PaginationInfo"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "description": "Pagination information, present only if the 'data' is a single page of a larger result set."
+    }
+  },
+  "required": [
+    "data"
+  ],
+  "title": "ToolResponse[list[AdvancedFilterItem]]",
+  "type": "object"
+}

Changed27 schema fields changedMar 12, 2026

addedInput schema / $schema

Added value: +"http://json-schema.org/draft-07/schema#"

addedInput schema / additionalProperties
```
Added value: +false
```

changedInput schema / properties / address / description

Previous value: -"Address which either sender or receiver of the transaction"New value: +"Address to query"

removedInput schema / properties / address / title
```
Removed value: -"Address"
```

removedInput schema / properties / age_from / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / age_from / default
```
Removed value: -null
```

changedInput schema / properties / age_from / description

Previous value: -"Start date and time (e.g 2025-05-22T23:00:00.00Z)."New value: +"Start date/time (ISO 8601)"

removedInput schema / properties / age_from / title
```
Removed value: -"Age From"
```
addedInput schema / properties / age_from / type
```
Added value: +"string"
```

removedInput schema / properties / age_to / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / age_to / default
```
Removed value: -null
```

changedInput schema / properties / age_to / description

Previous value: -"End date and time (e.g 2025-05-22T22:30:00.00Z)."New value: +"End date/time (ISO 8601)"

removedInput schema / properties / age_to / title
```
Removed value: -"Age To"
```
addedInput schema / properties / age_to / type
```
Added value: +"string"
```
removedInput schema / properties / chain_id / title
```
Removed value: -"Chain Id"
```

removedInput schema / properties / cursor / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / cursor / default
```
Removed value: -null
```

changedInput schema / properties / cursor / description

Previous value: -"The pagination cursor from a previous response to get the next page of results."New value: +"Pagination cursor"

removedInput schema / properties / cursor / title
```
Removed value: -"Cursor"
```
addedInput schema / properties / cursor / type
```
Added value: +"string"
```

removedInput schema / properties / methods / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / methods / default
```
Removed value: -null
```

changedInput schema / properties / methods / description

Previous value: -"A method signature to filter transactions by (e.g 0x304e6ade)"New value: +"Method signature filter (e.g. 0x304e6ade)"

removedInput schema / properties / methods / title
```
Removed value: -"Methods"
```
addedInput schema / properties / methods / type
```
Added value: +"string"
```

changedInput schema / required

Previous value: -[
-  "chain_id",
-  "address"
-]New value: +[
+  "chain_id",
+  "address",
+  "age_from"
+]

removedInput schema / title

Removed value: -"get_transactions_by_addressArguments"

First observedJan 31, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the readOnlyHint/openWorldHint/destructiveHint annotations, the description adds critical behavioral details: token transfers are filtered out, a single transaction can produce multiple records due to internal calls, the age_from requirement for performance, and pagination behavior. This goes beyond the structured annotations and provides valuable context without contradiction.

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?

The description is compact yet highly informative, using bold header-like cues for key exclusions and pagination. Every sentence serves a purpose: scope, exclusions, multi-record caveat, required input, and pagination. No filler or 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 (7 parameters, output schema present) and the rich annotations, the description covers all essential behaviors: what is retrieved, what is excluded, multi-record behavior, required field, and pagination instructions. It is fully adequate for an agent to select and invoke the tool correctly.

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 the schema already documents all parameters with detailed descriptions. The tool description adds minimal extra value for parameter understanding, only reinforcing the age_from requirement and pagination via cursor/next_call. This meets the baseline for high schema coverage.

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 the tool retrieves native currency transfers and smart contract interactions for an address, with an explicit exclusion of token transfers. It distinguishes itself from the sibling tool get_token_transfers_by_address by naming that alternative for token history, so the purpose is specific and well-scoped.

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

Usage Guidelines5/5

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

The description gives explicit when-to-use guidance: for token history, use get_token_transfers_by_address instead, and requires an age_from date to scope results. It also explains pagination usage with the 'pagination' field and next_call, providing clear context for when and how to use the tool.

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

All blockscout-mcp-server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Get Transactions by Address

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources