mcpField
T
three.ws Naming

three.ws Naming

Local
three.wsFinance255Updated today

About three.ws Naming

three.ws Naming is a read-only MCP server for resolving Solana .sol names, reverse-looking up a wallet's primary name, and checking whether a *.threews.sol agent handle is free. It reads public Solana mainnet data and needs no API key.

Key features

  1. 01Resolve .sol names to owning wallet addresses
  2. 02Reverse-lookup a wallet's primary .sol name
  3. 03Check whether a threews.sol handle is available
  4. 04Live public reads from Solana mainnet

Use cases

  1. 01Finding the wallet that owns a .sol name from an AI assistant
  2. 02Checking whether an agent handle is still available to claim
  3. 03Looking up the .sol name associated with a wallet address

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"nirholas-naming": {
"command": "npx",
"args": [
"-y",
"@three-ws/naming-mcp"
],
"env": {
"THREE_WS_BASE": "<THREE_WS_BASE>",
"THREE_WS_TIMEOUT_MS": "<THREE_WS_TIMEOUT_MS>"
}
}
}
}
Run commandnpx -y @three-ws/naming-mcp
Environment variables to set
THREE_WS_BASEBase URL of the three.ws API that serves /api/sns and /api/threews/subdomain. Override only when self-hosting or targeting a preview deployment.
THREE_WS_TIMEOUT_MSPer-request timeout in milliseconds. Resolution and availability checks hit a Solana RPC pool, so the default leaves room for a cold lookup.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@three-ws/naming-mcp0.1.3

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

three.ws

@three-ws/naming-mcp

The on-chain identity layer for AI agents — resolve .sol names and claim your agent a name on three.ws.

npm license node MCP Registry three.ws


A Model Context Protocol server that gives any AI assistant the three.ws naming / identity layer over stdio. Resolve a Solana .sol name to the wallet that owns it, reverse-lookup a wallet to its primary name, and check whether a *.threews.sol agent handle is still free to claim.

This is the three.ws identity layer: where avatars give your agent a face and scenes give it a world, names give it an identity. A *.threews.sol subdomain showcases an agent profile at https://three.ws/u/<label> — claiming one gives your agent a name. No API key, no signer, no payment — every call hits the public /api/sns and /api/threews/subdomain endpoints, backed by Solana / Bonfida SNS (mainnet).

Note: minting a *.threews.sol subdomain is the authenticated write path on the three.ws HTTP API. This MCP server exposes the public resolution + availability reads; once you find a free handle, claim it from your three.ws account.

Install

npm install @three-ws/naming-mcp

Or run with npx (no install):

npx @three-ws/naming-mcp

Quick start

Claude Code, one line:

claude mcp add naming -- npx -y @three-ws/naming-mcp

Claude Desktop / Cursor (claude_desktop_config.json or mcp.json):

{
	"mcpServers": {
		"naming": {
			"command": "npx",
			"args": ["-y", "@three-ws/naming-mcp"]
		}
	}
}

Inspect the surface with the MCP Inspector:

npx -y @modelcontextprotocol/inspector npx @three-ws/naming-mcp

Tools

ToolTypeWhat it does
sns_resolveread-onlyResolve a .sol name → the base58 wallet that owns it.
sns_reverseread-onlyReverse-lookup a wallet → its primary .sol name.
threews_availabilityread-onlyCheck whether <label>.threews.sol is free to claim as a three.ws agent identity.

All three are live public reads against Solana mainnet. A .sol name with no owner (or a wallet with no favorite name) returns resolved: false — a routine, expected answer, not an error.

Input parameters

sns_resolve — name (required: a .sol label, subdomain, or full name with or without the trailing .sol).

sns_reverse — address (required: a base58 Solana public key).

threews_availability — label (required: the handle to check, e.g. nick for nick.threews.sol; 1–63 chars of [a-z0-9-]).

Example

// sns_resolve
> { "name": "bonfida" }
{
  "ok": true,
  "name": "bonfida.sol",
  "address": "Fw1ETanDZafof7xEULsnq9UY6o71Tpds89tNwPkWLb1v",
  "resolved": true
}

// threews_availability
> { "label": "test" }
{
  "ok": true,
  "full": "test.threews.sol",
  "label": "test",
  "available": true,
  "owner": null,
  "on_chain_check": "ok",
  "showcase_url": null
}

Requirements

  • Node.js >= 20.
  • Network access to https://three.ws (or your own THREE_WS_BASE).
Environment variables
VariableRequiredDefault
THREE_WS_BASEnohttps://three.ws
THREE_WS_TIMEOUT_MSno20000

Links


Part of the three.ws SDK suite — 3D AI agents, on-chain identity, and agent payments.
Website · Changelog · GitHub

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.