# @three-ws/metaplex-agent-mcp

Deploy AI agents on-chain on Solana with an EIP-8004 identity. Deploy fee funds $THREE buybacks.

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the package rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 0.2.0
- **Author:** io.github.nirholas
- **License:** Unknown
- **npm:** @three-ws/metaplex-agent-mcp
- **Source:** https://github.com/nirholas/three.ws
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

60/100 (B), scored on the package rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 9 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-01T21:44:59.606Z
- **Version scanned:** 0.2.0
- **CVEs:** none found by OSV at scan time

## Tools

10 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `agent_wallet` — Show a wallet address and its live SOL balance. Pass `asset` to derive an on-chain agent's built-in wallet
- `build_registration` — Build the Genesis-style EIP-8004 registration-v1 JSON document and its self-contained
- `get_onchain_agent` — Fetch a Metaplex Agent Registry agent by its Core asset address: name, owner, update authority, plugins
- `metaplex-agent-mcp`
- `list_onchain_agents` — The latest agents to land on-chain in the Metaplex Agent Registry, newest first, from the live three.ws
- `mint_onchain_agent` — Deploy an AI agent on-chain, Genesis-333 style: mints a Metaplex Core asset (data: URI metadata, verified
- `prepare_agent_mint` — Build the exact Genesis-style mint+register flow (Metaplex Core asset + Agent Identity) for an EXTERNAL
- `register_agent_identity` — Give an ALREADY-MINTED Metaplex Core asset its Agent Identity: writes the EIP-8004 registration document
- `send_signed_transaction` — Broadcast one or more fully signed Solana transactions (base64) IN ORDER, polling each to confirmation
- `three_status` — What the next on-chain deploy costs and why. Returns the deploy-fee schedule (a flat SOL fee on mainnet,

## Install

**Verdict: review** — Installable, but 1 thing to check first: No publisher has proved control of this listing; it is indexed, not vouched for.
**Cautions** (coverage gaps and advisories — never blocking)
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"metaplex-agent\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"@three-ws/metaplex-agent-mcp\"\n      ]\n    }\n  }\n}"
```

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on your machine; read-only tool surface.
- Floor 13, ceiling 31 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/%40three-ws%2Fmetaplex-agent-mcp
- Install plan: https://forgeregistry.com/api/v1/packages/%40three-ws%2Fmetaplex-agent-mcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/%40three-ws%2Fmetaplex-agent-mcp
- HTML page: https://forgeregistry.com/registry/%40three-ws%2Fmetaplex-agent-mcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.
