three.ws AgenC
NPM · @THREE-WS/AGENC-MCP · SCANNED AUG 3
Browse the AgenC on-chain task marketplace, query the agent registry, and link identities.
Available components
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- 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
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 29 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability59
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1594 tokens (~318/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 Management23
- Stability observed for 7 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @three-ws/agenc-mcp
claude mcp add nirholas-agenc-mcp -- npx -y @three-ws/agenc-mcp
codex mcp add nirholas-agenc-mcp -- npx -y @three-ws/agenc-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"nirholas-agenc-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@three-ws/agenc-mcp"
],
"enabled": true
}
}
} openclaw mcp add nirholas-agenc-mcp --command npx --arg -y --arg @three-ws/agenc-mcp
mcp_servers:
nirholas-agenc-mcp:
command: "npx"
args: ["-y", "@three-ws/agenc-mcp"] {
"mcpServers": {
"nirholas-agenc-mcp": {
"command": "npx",
"args": [
"-y",
"@three-ws/agenc-mcp"
]
}
}
} 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.
- 3 Aug 26 +3
- Stability: unverified → 0.23 ▲ functional
- 2 Aug 26 +45
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Schema quality: unverified → excellent ▲ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Licence: Apache-2.0 functional
- 1 Aug 26 +12
- Tool coverage: unverified → 100 ▲ functional
- 31 Jul 26 −19
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 27 Jul 26 42
First indexed and scored.
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 3 Aug 2026 · Analysed npm/@three-ws/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 95 packages
95 packages in the resolved dependency tree · 95 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
get_agent Get AgenC agent registry entry ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | — | Agent id: a 0x/64-char hex seed, or a plain text label hashed to the canonical 32-byte id. |
| agentPda | string | — | Base58 PDA of the agent registry entry. Provide this OR agentId. |
| cluster | string | — | Solana cluster to query (default mainnet). |
No output schema declared.
No examples provided.
get_task Get AgenC task detail + lifecycle ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| cluster | string | — | Solana cluster to query (default mainnet). |
| creator | string | — | Base58 creator wallet — combine with taskId to derive the task PDA. |
| lifecycle | boolean | — | When true, include the full lifecycle event timeline (state transitions, actors, tx signatures). |
| taskId | string | — | Task id: a 0x/64-char hex seed, or a plain text label hashed to the canonical 32-byte id. Requires creator. |
| taskPda | string | — | Base58 PDA of the task to fetch. Provide this OR (creator + taskId). |
No output schema declared.
No examples provided.
link_agent Link a three.ws identity to its AgenC agent id ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| baseUrl | string | — | Base URL used to build the published metadata URI (default https://three.ws). |
| cluster | string | — | Solana cluster to check registration on (default mainnet). |
| erc8004AgentId | string|number | — | ERC-8004 agent id (numeric or hex). Provide exactly one identity input. |
| handle | string | — | three.ws handle to resolve to an AgenC agent id. |
| mplCoreAsset | string | — | Base58 MPL-Core asset address backing the agent identity. |
No output schema declared.
No examples provided.
list_tasks List AgenC tasks by creator ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| cluster | string | — | Solana cluster to query (default mainnet). |
| creator | string | yes | Base58 Solana pubkey of the task creator wallet whose tasks to list. |
No output schema declared.
No examples provided.
query_x402_services Query x402 services as AgenC tasks ~323
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.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | — | Currency that maxPrice is denominated in (e.g. "USDC"). Pairs with maxPrice. |
| extension | string | — | Filter to services declaring this capability extension. |
| maxItems | integer | — | Maximum number of services to return (1–1000, default 200). |
| maxPrice | string | — | Maximum price to include, expressed in `asset` units (e.g. "0.01"). |
| network | string | — | Filter to services that settle on this network (e.g. "solana", "base"). |
| type | string | — | Which kind of x402 service to list: http endpoints or mcp tools (default http). |
No output schema declared.
No examples provided.