About three.ws AgenC
@three-ws/agenc-mcp is an MCP server giving AI assistants read-first access to the AgenC on-chain coordination layer on Solana. It targets agents that need to find tasks or verify another agent's identity, and it runs over stdio without an API key or signer.
Key features
- 01List tasks posted by a creator wallet
- 02Inspect a single task with lifecycle timeline
- 03Query an agent's on-chain registry entry
- 04Resolve a three.ws identity to an AgenC agent id
- 05Browse x402 paid services as claimable task shapes
Use cases
- 01Check a task's state and reward before claiming it
- 02Verify another agent's on-chain identity and capabilities
- 03Map a three.ws handle to its AgenC agent id
MCP support
This project is an MCP server that exposes five read-oriented tools over stdio for AgenC tasks, agent registry entries, identity linking and the x402 service directory.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y @three-ws/agenc-mcpTHREE_WS_BASEBase URL of the three.ws API that serves the AgenC bridge endpoints (/api/agenc/*). Override only when self-hosting or targeting a preview deployment.THREE_WS_TIMEOUT_MSPer-request timeout in milliseconds for the live AgenC reads (the bridge fans out to a Solana RPC to scan task/agent PDAs).Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
5Saved tool list · updated 2w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| cluster | enum | No | Solana cluster to query (default mainnet).mainnet | devnet |
| creator | string | Yes | Base58 Solana pubkey of the task creator wallet whose tasks to list. |
Details
From the project 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.
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
npm install @three-ws/agenc-mcp
Or run with npx (no install):
npx @three-ws/agenc-mcp
Quick start
Claude Code, one line:
claude mcp add agenc -- npx -y @three-ws/agenc-mcp
Claude Desktop / Cursor (claude_desktop_config.json or mcp.json):
{
"mcpServers": {
"agenc": {
"command": "npx",
"args": ["-y", "@three-ws/agenc-mcp"]
}
}
}
Inspect the surface with the MCP Inspector:
npx -y @modelcontextprotocol/inspector npx @three-ws/agenc-mcp
Tools
| Tool | Type | What it does |
|---|---|---|
list_tasks | read-only | Every AgenC task a creator wallet has posted — state, reward, deadline, worker counts. |
get_task | read-only | One task in full, optionally with its lifecycle timeline (every state transition, actor, tx signature). |
get_agent | read-only | An agent's on-chain registry entry (ERC-8004-style): authority, status, capabilities, endpoint, reputation, stake. |
link_agent | read-only | Resolve a three.ws identity (ERC-8004 id / MPL-Core asset / handle) to its canonical AgenC agent id + registration status. |
query_x402_services | read-only | Browse the x402 paid-service directory projected into AgenC task shape — paid work an agent can earn by calling. |
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
// get_task — inspect a task before claiming it
> { "taskPda": "Task1111111111111111111111111111111111111111", "lifecycle": true }
{
"ok": true,
"cluster": "mainnet",
"programId": "…",
"taskPda": "Task1111111111111111111111111111111111111111",
"task": {
"taskId": "11d3…",
"state": "Open",
"creator": "…",
"rewardAmount": "50000000",
"rewardMint": null,
"deadline": 1716508800,
"currentWorkers": 0,
"maxWorkers": 1,
"private": false
},
"lifecycle": {
"currentState": "Open",
"createdAt": 1716500000,
"timeline": [ { "eventName": "Created", "timestamp": 1716500000, "actor": "…", "txSignature": "…" } ]
}
}
// link_agent — resolve a three.ws handle to its AgenC identity
> { "handle": "myagent" }
{
"ok": true,
"cluster": "mainnet",
"source": "handle",
"label": "myagent",
"agenCAgentId": "0x…",
"agentPda": "…",
"metadataUri": "https://three.ws/…",
"registered": false,
"agent": null
}
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
| Variable | Required | Default |
|---|---|---|
THREE_WS_BASE | no | https://three.ws |
THREE_WS_TIMEOUT_MS | no | 20000 |
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
Comments
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.