MCP SERVERGive it one web3 identity — an address, an ENS name, a Farcaster or Lens handle — and get back the other identities linked to it across platforms.
LABSCO SUMMARY
Identity across web3 platforms is fragmented by design — an address, an ENS name and a Farcaster handle are separate namespaces with no built-in join. Resolving between them is the first step of almost any real research task and is otherwise several manual lookups. Being a thin client over next.id's relation graph is both the strength and the limit: the answer is only as complete as that graph, and an identity absent from it returns nothing rather than a maybe. Worth knowing that this returns claimed and verified links, not a behavioural inference — an absence here is not evidence that two accounts are unrelated.
A single-tool identity resolver over next.id's relation graph, covering Ethereum addresses and domain names alongside Farcaster, Lens and other web3 platforms.
Nothing to supply. The configuration points at a relation service, which can be the public one or your own.
One command — npx -y @fengshanshan/server-relate-account
USE CASES
Hand it the address and get the ENS names, Farcaster and Lens handles linked to it, instead of checking each platform separately.
Start from the social identity you have and resolve to the addresses attached to it.
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
get-related-addressRetrieves all related identities associated with a specific platform identity. This tool helps discover cross-platform connections for the same person or entity. Use cases include: 1) Finding all accounts (Lens, Farcaster, ENS, etc.) belonging to the same person, 2) Resolving domain names to their underlying addresses (ENS domains, Lens handles, etc.)
BEFORE YOU INSTALL
1 tool when we connected.
npx on PATH
CONTEXT COST
Rated by the size of the one tool definition that rides along on every turn
INSTALLATION
git clone https://github.com/fengshanshan/relate-account-mcp
cd relate-account-mcp
# Install dependencies
npm install
# Build TypeScript
npm run build
# The compiled JavaScript will be in the build/ directorynpx -y @fengshanshan/server-relate-account{
"mcpServers": {
"relate-account": {
"command": "npx",
"args": [
"-y",
"@fengshanshan/server-relate-account"
],
"env": {
"DATA_API_URL": "https://graph.web3.bio/graphql",
"ACCESS_TOKEN": "<YOUR_ACCESS_TOKEN>"
}
}
}
}ACCESS_TOKEN is optional: the README says that without one, requests are limited after a certain amount. Delete that line if you do not have a token.
node <YOUR_PATH_TO_RELATE_ACCOUNT_MCP>/build/index.jsMCP servers
noditlabs
nirholas
maestro-org