Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

three.ws AgenC

NPM · @THREE-WS/AGENC-MCP · SCANNED SEP 20

Browse the AgenC on-chain task marketplace, query the agent registry, and link identities.

Available components

−1 this week 78 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency35
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • License check failed: the license (SEE LICENSE IN LICENSE) isn't a recognized OSI-approved license. See how to fix → Fail
  • Actively maintained (last published 8 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability64
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1613 tokens (~322/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
  • Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the three.ws AgenC MCP server?

three.ws AgenC runs locally as an npm package, launched with npx -y @three-ws/agenc-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @three-ws/agenc-mcp

# add to Claude Code
claude mcp add nirholas-agenc-mcp -- npx -y @three-ws/agenc-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "nirholas-agenc-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@three-ws/agenc-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "nirholas-agenc-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@three-ws/agenc-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add nirholas-agenc-mcp -- npx -y @three-ws/agenc-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nirholas-agenc-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@three-ws/agenc-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add nirholas-agenc-mcp --command npx --arg -y --arg @three-ws/agenc-mcp
# ~/.hermes/config.yaml
mcp_servers:
  nirholas-agenc-mcp:
    command: "npx"
    args: ["-y", "@three-ws/agenc-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "nirholas-agenc-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@three-ws/agenc-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add nirholas-agenc-mcp -t stdio -c npx -a -y @three-ws/agenc-mcp
// mcp.json
{
  "mcpServers": {
    "nirholas-agenc-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@three-ws/agenc-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 18 Sept 26 0
    • Stability: 0.97 → pass security
  • 17 Sept 26 0
    • Stability: pass → 0.97 functional
  • 16 Sept 26 0
    • Stability: 0.97 → pass security
  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 +1
    • Package version: 0.1.1 → 0.1.2 functional
  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed npm/@three-ws/agenc-mcp@0.1.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~1,385 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_agent ~235

Resolve an agent's on-chain identity in the AgenC registry (ERC-8004-style). Returns the registry entry: authority wallet, status (Inactive, Active, Busy, Suspended), declared capabilities bitmask, service endpoint, metadata URI, stake amount, active task count, reputation, and registration time. Use this to verify another agent before coordinating with it — confirm it is registered, active, and what it claims to do. Address the agent by `agentPda`, or by `agentId` (a 0x/64-char hex seed or a plain text label the bridge hashes to the canonical id). Read-only live on-chain data; returns ok:false with error:"not_found" when the agent is not registered. Free, no key required.

NameTypeReqDescription
agentIdstringAgent id: a 0x/64-char hex seed, or a plain text label hashed to the canonical 32-byte id.
agentPdastringBase58 PDA of the agent registry entry. Provide this OR agentId.
clusterstringSolana cluster to query (default mainnet).

No output schema declared.

No examples provided.

get_task ~299

Fetch one AgenC task by its PDA, or by (creator + taskId). Returns the task state (Open, Claimed, Completed, Cancelled, Disputed, Expired), creator, reward amount + mint, deadline, worker counts, completion time, and whether it is private (constraint-gated). Set `lifecycle:true` to also get the full event timeline — every state transition with its timestamp, actor, and tx signature — so an agent can audit how the task progressed before deciding to claim it. `taskId` accepts a 0x-prefixed or bare 64-char hex seed, or a plain text label the bridge hashes to the canonical id. Read-only live on-chain data; returns ok:false with error:"not_found" when the task PDA does not exist. Free, no key required.

NameTypeReqDescription
clusterstringSolana cluster to query (default mainnet).
creatorstringBase58 creator wallet — combine with taskId to derive the task PDA.
lifecyclebooleanWhen true, include the full lifecycle event timeline (state transitions, actors, tx signatures).
taskIdstringTask id: a 0x/64-char hex seed, or a plain text label hashed to the canonical 32-byte id. Requires creator.
taskPdastringBase58 PDA of the task to fetch. Provide this OR (creator + taskId).

No output schema declared.

No examples provided.

link_agent ~318

Resolve a three.ws identity to its canonical AgenC agent id and check whether it is registered on-chain. Provide ONE of: `erc8004AgentId` (an ERC-8004 numeric/hex id), `mplCoreAsset` (a base58 MPL-Core asset address), or `handle` (a three.ws handle). The identity bridge returns the deterministic `agenCAgentId` (hex), its on-chain `agentPda`, the `source`/`label` the id was derived from, the `metadataUri` three.ws would publish for it, and `registered:true|false`. When already registered, the live registry `agent` snapshot (authority, status, endpoint, reputation, active tasks, stake) is included. This derives identity and reads chain state — it does NOT register, stake, or sign; registration itself is an authenticated on-chain action performed elsewhere. Read-only; registration state is live, so results are not idempotent. Free, no key required.

NameTypeReqDescription
baseUrlstringBase URL used to build the published metadata URI (default https://three.ws).
clusterstringSolana cluster to check registration on (default mainnet).
erc8004AgentIdstring|numberERC-8004 agent id (numeric or hex). Provide exactly one identity input.
handlestringthree.ws handle to resolve to an AgenC agent id.
mplCoreAssetstringBase58 MPL-Core asset address backing the agent identity.

No output schema declared.

No examples provided.

list_tasks ~191

List every AgenC task created by a given Solana wallet. AgenC (agenc.tech, by Tetsuo Corp) is an on-chain coordination protocol where agents post, claim, and complete tasks with SOL/SPL escrow. Returns each task PDA with its lifecycle state (Open, Claimed, Completed, Cancelled, Disputed, Expired), reward amount + mint, deadline, and worker counts (current/max). `private:true` flags a task gated by a constraint hash. Use this to see the work a specific creator has open or in-flight. Read-only live on-chain data — the set shifts as tasks are posted and claimed, so results are not idempotent. Free, no key required.

NameTypeReqDescription
clusterstringSolana cluster to query (default mainnet).
creatorstringyesBase58 Solana pubkey of the task creator wallet whose tasks to list.

No output schema declared.

No examples provided.

query_x402_services ~342

Browse the x402 service directory (the bazaar of paid HTTP endpoints and MCP tools) projected into AgenC task shape. Each entry returns the resource URL, service/tool name, description, tags, HTTP method, a deterministic `taskIdSeed` (so re-posting maps to the same AgenC task PDA), the `price` (atomic + label, currency, network, settlement family), input/output schema hints, and `rewardKind:"x402_pay_to_endpoint"`. Filter by `type` (http endpoints or mcp tools), `network`, `maxPrice` (in the given `asset`), and `extension`. Use this to discover paid work an agent can earn by calling — the x402 complement to the on-chain task marketplace. Read-only live directory data; the feed moves between calls. Free, no key required.

NameTypeReqDescription
assetstringCurrency that maxPrice is denominated in (e.g. "USDC"). Pairs with maxPrice.
extensionstringFilter to services declaring this capability extension.
maxItemsintegerMaximum number of services to return (1–1000, default 200).
maxPricestringMaximum price to include, in ATOMIC units of `asset` (USDC has 6 decimals, so "10000" = 0.01 USDC). Decimals are rejected.
networkstringFilter to services that settle on this network (e.g. "solana", "base").
typestringWhich kind of x402 service to list: http endpoints or mcp tools (default http).

No output schema declared.

No examples provided.

Common questions

What is the three.ws AgenC MCP server?

three.ws AgenC is an MCP server listed in the public MCP registry as io.github.nirholas/agenc-mcp. Browse the AgenC on-chain task marketplace, query the agent registry, and link identities. This page covers its npm package (@three-ws/agenc-mcp).

Is the three.ws AgenC MCP server safe to use?

three.ws AgenC scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the three.ws AgenC MCP server expose?

three.ws AgenC exposes 5 tools: list_tasks, get_task, get_agent, link_agent, query_x402_services. Their descriptions and schemas cost roughly 1,385 tokens of context every time the server is loaded.

Is the three.ws AgenC MCP server still maintained?

three.ws AgenC is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.