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

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

Output 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.

Changed5 schema fields changedOct 28, 2026

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

removedInput schema / properties / request / anyOf

Removed 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"
-  }
-]

addedInput schema / properties / request / properties

Added value: +{
+  "address": {
+    "description": "Wallet address to analyze for related addresses",
+    "type": "string"
+  },
+  "chain": {
+    "default": "all",
+    "type": "string"
+  }
+}

addedInput schema / properties / request / required
```
Added value: +[
+  "address"
+]
```
addedInput schema / properties / request / type
```
Added value: +"object"
```

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

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly/non-destructive, so safety is covered; the description goes further by scoping the result set to a fixed list of 'special' connections and warning that first-funder exchange addresses usually do not belong to the same entity. That is a real analytical caveat that saves the agent from a wrong inference. It doesn't mention pagination or result volume.

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?

Purpose is front-loaded in the first sentence, with caveats following in a clearly separated note. Some waste exists ('the the' typo, an awkward multi-clause enumeration) but every sentence carries information.

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 explained, and annotations cover the safety profile. The description fills the main gap by defining which relationships count as 'related'. Only the chain parameter's behavior is left entirely to the schema.

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 100% and the nested request already documents address and chain, so the baseline applies. The description adds nothing about the chain parameter (default 'all') or how scope changes results. Marginal value beyond the schema.

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?

States a specific verb and resource: 'Get information about related addresses of an input address.' The note enumerates the exact connection types returned, which is unusual precision. It stops short of fully distinguishing itself from address_counterparties and address_first_funder, which it only gestures at.

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

Usage Guidelines4/5

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

'To get related wallets, also check address counterparties' explicitly names the complementary sibling and the condition for using it. The note about first-funder exchange withdrawal addresses being a false positive is genuine usage guidance. No explicit statement of when NOT to use this tool in favor of address_first_funder or address_labels.

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?