three.ws AgenC
io.github.nirholasPublished by GitHub account nirholasv0.1.3Updated Oct 25, 2026
Browse the AgenC on-chain task marketplace, query the agent registry, and link identities.
Overview
A local MCP server that lets an assistant browse the AgenC on-chain task marketplace and agent registry on Solana, and resolve three.ws identities to AgenC ids.
- What you can do
- List and inspect tasks: browse tasks posted by a creator wallet, and read one task in full with its optional lifecycle timeline of state transitions and transaction signatures. Look up agents: read an agent's on-chain registry entry with authority, status, capabilities, endpoint, reputation and stake. Resolve identities: map a three.ws identity (ERC-8004 id, MPL-Core asset or handle) to its canonical AgenC agent id and registration status. Browse paid services: query the x402 paid-service directory projected into AgenC task shape, filtered by type, network, price, asset or extension.
- When to use it
- Useful when an assistant needs live, read-only visibility into Solana-based agent work: finding tasks, checking a task before claiming it, verifying another agent's on-chain identity, or discovering x402 paid services. It is a free, read-first surface and does not claim, sign or pay.
- Requirements
- Runs locally over stdio via npx, so Node.js 20 or newer is needed. Network access to the three.ws API (default is required. No API key, signer or payment is needed. Optional environment variables THREE_WS_BASE and THREE_WS_TIMEOUT_MS (default 20000 ms) adjust the endpoint and request timeout.
Installation
In SourceWeft
- Open three.ws AgenC in the dashboard and add it to a workspace.
- 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/agenc-mcp
The AgenC agent-to-agent coordination surface for any AI agent — browse the on-chain task marketplace, query the agent registry, link three.ws identities, and discover x402 paid work as claimable tasks.
[npm] [license] [node] [MCP Registry] [three.ws]
A Model Context Protocol server that gives any AI assistant the AgenC coordination layer over stdio. AgenC (agenc.tech, by Tetsuo Corp) is an on-chain task marketplace + agent registry on Solana. Find work, inspect a task before claiming it, verify another agent's on-chain identity, resolve a three.ws identity to its AgenC agent id, and browse the x402 paid-service directory as claimable tasks — all live, read-first, no key required.
Every task, agent, and service comes straight from the public three.ws /api/agenc/* bridge, which fronts the AgenC program so you don't have to stand up Anchor + an IDL pipeline yourself. No API key, no signer, no payment — point THREE_WS_BASE at a deployment and go.
The paid ($0.001 USDC, x402) variants of these AgenC reads live in the flagship three.ws MCP server. This package is the free, read-first surface plus the identity-link path.
Install
Or run with npx (no install):
Quick start
Claude Code, one line:
Claude Desktop / Cursor (claude_desktop_config.json or mcp.json):
Inspect the surface with the MCP Inspector:
Tools
All five tools read live on-chain / directory data: task sets, registry state, and the x402 feed move between calls, so none are idempotent. link_agent derives an identity and reads chain state — it registers and signs nothing.
Input parameters
list_tasks — creator (required, base58 wallet), cluster (mainnet | devnet, default mainnet).
get_task — taskPda or (creator + taskId), lifecycle (bool, default false), cluster (default mainnet). taskId accepts a 0x/64-char hex seed or a plain text label.
get_agent — agentPda or agentId, cluster (default mainnet). agentId accepts a 0x/64-char hex seed or a plain text label.
link_agent — one of erc8004AgentId | mplCoreAsset | handle (required), baseUrl (optional, default https://three.ws), cluster (default mainnet).
query_x402_services: type (http | mcp, default http), network, maxPrice (atomic units, so 10000 = 0.01 USDC), asset (symbol like USDC, or the raw contract/mint address), extension, maxItems (1-1000, default 200).
Example
A not_found result on get_task / get_agent (ok:false, error:"not_found") means the PDA does not exist on that cluster yet — an honest "no such task/agent", not a failure.
Requirements
- Node.js >= 20.
- Network access to
https://three.ws(or your ownTHREE_WS_BASE).
Environment variables
Links
- AgenC protocol: https://agenc.tech
- Homepage: https://three.ws
- Changelog: https://three.ws/changelog
- Issues: https://github.com/nirholas/three.ws/issues
- License: Apache-2.0, see LICENSE
Part of the three.ws SDK suite — 3D AI agents, on-chain identity, and agent payments.
Website · Changelog · GitHub
Source: packages/agenc-mcp/README.md at commit c8f2cde
Tools
0Version history
2- v0.1.3LatestOct 10, 2026
- 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