token-naming-mcpSAFE
Resolve Solana .sol names and check *.threews.sol agent-identity availability from any AI agent. sns_resolve maps a .sol name to its owner wallet, sns_reverse maps a wallet to its primary name, and threews_availability checks whether a three.ws agent handle is free to claim. No key, no signer, no pa
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
@three-ws/naming-mcp
The on-chain identity layer for AI agents — resolve .sol names and claim your agent a name on three.ws.
A Model Context Protocol server that gives any AI assistant the three.ws naming / identity layer over stdio. Resolve a Solana.solname to the wallet that owns it, reverse-lookup a wallet to its primary name, and check whether a*.threews.solagent 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/ — 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 ac7094e0b482daOBSERVED · 2026-10-10Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.
claude mcp add naming-mcp -- npx -y @three-ws/[email protected]
Exposed tools (1)
1 read · 0 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
sns_resolve | read | Resolve a Solana Name Service (.sol) name to the base58 wallet address that owns it. Accepts a bare label, a subdomain, or the full name with or without the trailing |
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- declared (1 observation(s))
- Shell
- none-observed
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (4)
.nojekyll
@modelcontextprotocol/sdk, zod
- **Report a bug** with the [bug form](https://github.com/nirholas/token-naming-mcp/issues/new?template=bug.yml). Include the version, your Node version and the smallest reproduction you can.
Know someone who would use it? [Post on X](https://twitter.com/intent/tweet?text=token-naming-mcp%3A%20Resolve%20Solana%20.sol%20names%20and%20check%20*.threews.sol%20agent-identity%20availability%20f
Gates applied: no_behavioural_pass.
7094e0b482dafull audit observations/trust-audit/mcp-server/nirholas__token-naming-mcp.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-10 | 7094e0b482da | SAFE | B | 89 | first audit |
Questions
What is the token-naming-mcp MCP server?
Resolve Solana .sol names and check *.threews.sol agent-identity availability from any AI agent. sns_resolve maps a .sol name to its owner wallet, sns_reverse maps a wallet to its primary name, and threews_availability checks whether a three.ws agent handle is free to claim. No key, no signer, no pa
What tools does token-naming-mcp expose?
1 in total: 1 read-only, 0 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is token-naming-mcp safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.
What credentials does token-naming-mcp need?
No credential environment variables were found in its source, so it appears to need none.
How does token-naming-mcp run?
It speaks stdio, so it runs as a local process your client starts. It is published on npm as @three-ws/naming-mcp at 0.1.3.
How current is this page?
The grade is for one exact copy of the source (7094e0b482da), read on 2026-10-10. The repository is watched and re-audited when it changes.