Nansen

Finding related wallets

address_related_addresses

Read-only

Get information about related addresses of an input address.

Note: This only includes the the "special" connections 'First Funder', 'Signer', 'Previous Signer', 'Multisig Signer of', 'Previous Multisig Signer of', 'Deployed via', 'Deployed by', 'Deployed Contract', 'Created Contract', 'Created by'. To get related wallets, also check address counterparties. First funder exchange withdrawal address does usually NOT belong to the same entity as the address, only deposit addresses. Only information is that it has been funded by the exchange.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`request`	Yes	AddressRelatedAddressesRequest containing parameters and pagination settings

Output Schema

TableJSON Schema

Name	Required	Description
`rows`	No
`chains`	No	Chains that were queried.
`address`	No
`message`	No	Notice or error text when the tool returns no data rows.

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedSep 23, 2026

addedOutput schema / description

Added value: +"Structured result of `address_related_addresses`."

addedOutput schema / properties / address

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Address"
+}

addedOutput schema / properties / chains

Added value: +{
+  "description": "Chains that were queried.",
+  "items": {
+    "type": "string"
+  },
+  "title": "Chains",
+  "type": "array"
+}

addedOutput schema / properties / message

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Notice or error text when the tool returns no data rows.",
+  "title": "Message"
+}

removedOutput schema / properties / result

Removed value: -{
-  "type": "string"
-}

addedOutput schema / properties / rows

Added value: +{
+  "items": {
+    "description": "One address connected to the queried address.",
+    "properties": {
+      "address": {
+        "title": "Address",
+        "type": "string"
+      },
+      "address_label": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Address Label"
+      },
+      "block_timestamp": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Block Timestamp"
+      },
+      "chain": {
+        "title": "Chain",
+        "type": "string"
+      },
+      "relation": {
+        "description": "How the address is connected, e.g. First Funder, Signer, Deployed by.",
+        "title": "Relation",
+        "type": "string"
+      },
+      "transaction_hash": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Transaction Hash"
+      }
+    },
+    "required": [
+      "address",
+      "chain",
+      "relation"
+    ],
+    "title": "RelatedAddressRow",
+    "type": "object"
+  },
+  "title": "Rows",
+  "type": "array"
+}

removedOutput schema / required
```
Removed value: -[
-  "result"
-]
```

addedOutput schema / title

Added value: +"AddressRelatedAddressesOutput"

removedOutput schema / x-fastmcp-wrap-result
```
Removed value: -true
```

Changed1 schema field changedMay 25, 2026

changedInput schema / properties / request / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "type": "object"
-  },
-  {
-    "description": "Complete request for address related addresses (flattened).",
-    "properties": {
-      "addresses": {
-        "description": "List of wallet addresses to analyze for related addresses",
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      },
-      "chain": {
-        "default": "all",
-        "type": "string"
-      }
-    },
-    "required": [
-      "addresses"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  {
+    "description": "Complete request for address related addresses (flattened).",
+    "properties": {
+      "address": {
+        "description": "Wallet address to analyze for related addresses",
+        "type": "string"
+      },
+      "chain": {
+        "default": "all",
+        "type": "string"
+      }
+    },
+    "required": [
+      "address"
+    ],
+    "type": "object"
+  }
+]

Changed4 schema fields changedMay 19, 2026

removedInput schema / $defs

Removed value: -{
-  "AddressRelatedAddressesRequest": {
-    "description": "Complete request for address related addresses (flattened).",
-    "properties": {
-      "addresses": {
-        "description": "List of wallet addresses to analyze for related addresses",
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      },
-      "chain": {
-        "default": "all",
-        "type": "string"
-      }
-    },
-    "required": [
-      "addresses"
-    ],
-    "type": "object"
-  }
-}

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

changedInput schema / properties / request / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "type": "object"
-  },
-  {
-    "$ref": "#/$defs/AddressRelatedAddressesRequest"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  {
+    "description": "Complete request for address related addresses (flattened).",
+    "properties": {
+      "addresses": {
+        "description": "List of wallet addresses to analyze for related addresses",
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "chain": {
+        "default": "all",
+        "type": "string"
+      }
+    },
+    "required": [
+      "addresses"
+    ],
+    "type": "object"
+  }
+]

addedInput schema / properties / request / description

Added value: +"AddressRelatedAddressesRequest containing parameters and pagination settings"

First observedFeb 18, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already mark this as read-only and non-destructive, but the description adds meaningful behavioral detail: it narrows the result scope to a specific list of connection types, cross-references another sibling tool, and warns about a common misinterpretation around exchange withdrawal addresses. This goes well beyond what annotations convey.

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?

The description is front-loaded with the core purpose, followed by focused caveats and cross-references. All sentences earn their place, though the minor typo 'the the' and slightly awkward wording in the final caveat keep it from being perfectly polished.

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 has only one parameter, a fully covered schema, an output schema, and clarifying annotations, this description is complete. It tells the agent what the tool returns, what it excludes, which sibling to use for broader results, and how to interpret a specific edge case.

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 the address and chain parameters. The description does not add parameter-level detail, but it does clarify that the input is an address and that the output is about its related addresses. This meets the baseline for a fully-covered 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 states a clear verb and resource: 'Get information about related addresses of an input address.' It also distinguishes itself from siblings by explicitly listing the special connection types included and telling the agent to check address counterparties for related wallets, so there is no confusion with address_counterparties or address_first_funder.

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 explicitly says this tool only includes special connections and that to get related wallets the agent should also check 'address counterparties.' It also provides a domain-specific caveat about exchange withdrawal addresses not belonging to the same entity, which clarifies when the data should be interpreted cautiously.

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

All Nansen 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.

Resources

Need Help?