three.ws Naming

io.github.nirholasPublished by GitHub account nirholasv0.1.3Updated Oct 25, 2026

On-chain identity for AI agents: resolve .sol names, reverse-lookup wallets, check handles.

VerifiedSTDIODesktop onlyWeb Search & ScrapingFinance

Overview

AI-generated overview

A local stdio MCP server that lets an assistant resolve Solana .sol names, reverse-look up wallets, and check whether a three.ws agent handle is free.

What you can do
Resolve a .sol name, subdomain, or full name to the base58 wallet that owns it, with unresolved names returned as resolved: false rather than an error. Reverse-look up a base58 Solana public key to its primary .sol name. Check whether a label is still available as a threews.sol agent handle, returning availability, owner, and showcase URL. All three are read-only public lookups against Solana mainnet.
When to use it
Useful when an assistant needs to map Solana names to wallets or wallets to names, or when a user wants to check whether a three.ws agent handle is still free before claiming it from their three.ws account.
Requirements
Node.js 20 or newer, run locally via npx or npm install. Network access to three.ws (or a custom THREE_WS_BASE). Optional environment variables THREE_WS_BASE and THREE_WS_TIMEOUT_MS. No API key, signer, or account needed for the reads.
Before you install
Only public read paths are exposed; claiming a subdomain is done separately through a three.ws account and is not performed by this server. Lookups go to the three.ws API and Solana mainnet, so queried names and wallet addresses leave the machine. THREE_WS_BASE can redirect requests to another host if changed.

Installation

In SourceWeft

  1. Open three.ws Naming in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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

bash
npm install @three-ws/naming-mcp

Or run with npx (no install):

bash
npx @three-ws/naming-mcp

Quick start

Claude Code, one line:

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

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

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

Inspect the surface with the MCP Inspector:

bash
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

jsonc
// 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

Source: packages/naming-mcp/README.md at commit c8f2cde

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v0.1.3LatestOct 10, 2026
  2. v0.1.2Sep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts