Skip to main content
Glama
fengshanshan

Related Identity MCP Server

by fengshanshan
README.md
# Related Identity MCP Server

A Model Context Protocol (MCP) server that helps discover related blockchain addresses and domain names for web3 identities across different platforms.

## Tools

- 🔍 **get-related-address**
Find related addresses across Ethereum, Farcaster, Lens, and other web3 platforms. Leverages the data source in [relation-server](https://github.com/NextDotID/relation_server) of next.id.


## Configuration

Add the following configuration to your MCP client settings:

### Claude Desktop
Add to your `claude_desktop_config.json`:
```json
//to your local relate-account-service
{
  "mcpServers": {
    "relate-account": {
      "command": "node",
      "args": ["/absolute/path/to/relate-account-mcp/build/index.js"]
    },
    "env": {
        "DATA_API_URL": "https://graph.web3.bio/graphql",
        "ACCESS_TOKEN":"YOUR_ACCESS_TOKEN" //if no access_token, will be limited after a certain amount of request
    }
  }
}

//use publish service
{
  "mcpServers": {
    "relate-account": {
      "command": "npx",
      "args": [
        "-y",
        "@fengshanshan/mcp-server-relate-account"
      ],
      "env": {
        "DATA_API_URL": "https://graph.web3.bio/graphql",
        "ACCESS_TOKEN":"YOUR_ACCESS_TOKEN" //if no access_token, will be limited after a certain amount of request
        }
    }
  }
}
```

### Other MCP Clients
Use the built binary directly:
```bash
node /path/to/relate-account-mcp/build/index.js
```

## Usage

Once configured, you can use the `get-related-address` tool in your MCP client:

### Parameters
- **platform** (string): The platform to search on (e.g., "ethereum", "farcaster", "lens", "ens")
- **identity** (string): The user's identity (address, ENS domain, username, etc.)


## Development

```bash
# Install dependencies
npm install

# Build TypeScript
npm run build

# The compiled JavaScript will be in the build/ directory
```

TDQS

A3.7/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined and distinct by default.

Naming Consistency5/5

A single tool inherently exhibits perfect naming consistency, as there are no other tools to compare it against for patterns or deviations.

Tool Count2/5

One tool is too few for a server focused on identity resolution across multiple platforms, as it lacks operations like validation, creation, or management of related identities, making the scope feel incomplete.

Completeness2/5

The server has a significant gap in coverage for identity-related operations; it only retrieves related addresses but lacks tools for adding, updating, verifying, or deleting identities, which are essential for a comprehensive identity management system.

Maintenance

ActivityInactive
ResponsivenessNo issues