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.

Metaplex Agent Registry

NPM · @THREE-WS/METAPLEX-AGENT-MCP

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

0 this week 77 Trust /100

Last scanned (5 hours ago)

Scores higher than 55% of npm servers

Category Crypto and Web3

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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 49 of 172 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency48
  • 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 54 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability63
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 3343 tokens (~371/item across 9 items; 9 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
  • All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 10 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
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.

  • 31 Oct 26 0
    • Stability: 0.97 → pass security
  • 30 Oct 26 0
    • Stability: pass → 0.97 functional
  • 24 Oct 26 −3
    • CVE-2023-54404 affects this package: high ▼ security
    • Known CVEs: CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. security
    • Stability: 0.97 → pass security
  • 23 Oct 26 0
    • Stability: pass → 0.97 functional
  • 17 Oct 26 0
    • Stability: 0.97 → pass security
  • 16 Oct 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.

  • 14 Oct 26 +42
    • Injection markers: unverified → pass ▲ security
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • Stability: unverified → 0.90 ▲ functional
    • Package version: 0.2.0 → 0.2.1 functional
  • 12 Oct 26 0
    • Package version: 0.2.0 → 0.2.1 functional
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 5 Nov 2026 · Analysed npm/@three-ws/metaplex-agent-mcp@0.2.1

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 →

Vulnerabilities 5 findings
ID CVE Severity Vector Fix available
GHSA-528h-pc64-c93x CVE-2026-71429 medium CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-hqr4-qq8f-hg3x CVE-2026-104182 medium CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-mjw6-4jj6-33hc CVE-2026-104183 medium CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L yes
GHSA-w5hq-g745-h8pq CVE-2026-41907 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N yes
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 172 packages
Packages resolved 172
Deprecated 1
Stale 48
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 9 exposed · ~3,133 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
agent_wallet ~166

Show a wallet address and its live SOL balance. Pass `asset` to derive an on-chain agent's built-in wallet (the Metaplex Core Asset Signer PDA, the wallet shown on metaplex.com/agents). Pass `address` to inspect any wallet. Pass neither to see the configured signing wallet, e.g. to confirm it is funded before mint_onchain_agent. On mainnet it also reports the wallet $THREE balance and the deploy-fee tier that balance earns (see three_status). Read-only; never moves funds.

NameTypeReqDescription
addressstring–A wallet address to inspect verbatim.
assetstring–A Core asset address: derives that agent's built-in wallet.
networkstring–Cluster. Defaults to the configured network.

No output schema declared.

No examples provided.

build_registration ~251

Build the Genesis-style EIP-8004 registration-v1 JSON document and its self-contained data:application/json;base64 URI, without touching Solana. Use it to preview exactly what mint_onchain_agent / register_agent_identity will write on-chain, or to host the document yourself and pass it back as registration_uri.

NameTypeReqDescription
activeboolean–Registration active flag. Default true.
assetstring–Asset address for the default chain-registry entry when no registrations are given.
descriptionstring–Agent description.
imagestring–Thumbnail image URL.
model_urlstring–3D model URL (GLB), written as model.uri.
namestringyesAgent name.
networkstring–Network for the default chain-registry entry. Defaults to the configured network.
registrationsarray–External registry entries.
servicesarray–Services the agent offers.
supported_trustarray–Default ['reputation'].
threews_agent_idstring–three.ws agent UUID for the Genesis-exact three.ws entry.
x402_supportboolean–Advertise x402 payment support. Default false.

No output schema declared.

No examples provided.

get_onchain_agent ~128

Fetch a Metaplex Agent Registry agent by its Core asset address: name, owner, update authority, plugins (royalties, verified creators, immutable metadata, attributes), the decoded asset metadata and EIP-8004 registration documents, whether the identity PDA exists, and the built-in agent wallet (Asset Signer PDA) with its live SOL balance. Read-only. Works on any registered agent, e.g. the three.ws Genesis mints.

NameTypeReqDescription
assetstringyesThe Core asset address (base58).
networkstring–Cluster. Defaults to the configured network.

No output schema declared.

No examples provided.

list_onchain_agents ~169

The latest agents to land on-chain in the Metaplex Agent Registry, newest first, from the live three.ws /api/deployments feed (which also indexes registrations minted outside three.ws). Each entry carries the Core asset address, name, description, image, owner, 3D and x402 flags, and explorer links. Set all_chains:true to include EVM ERC-8004 registrations in the same stream. Read-only.

NameTypeReqDescription
all_chainsboolean–Include EVM ERC-8004 registrations too. Default false (Solana only).
cursorstring–Pagination cursor from a previous call.
limitinteger–How many registrations to return. Default 12.
networkstring–Solana cluster. Defaults to the configured network.

No output schema declared.

No examples provided.

mint_onchain_agent ~898

Deploy an AI agent on-chain, Genesis-333 style: mints a Metaplex Core asset (data: URI metadata, verified creator, royalties, immutable metadata) AND registers its EIP-8004 Agent Identity, so it appears on metaplex.com/agents with its own built-in wallet. Runs as ONE atomic transaction when it fits Solana's 1232-byte limit, otherwise as create followed by register (how the Genesis 333 landed). Signs with the configured SOLANA_SECRET_KEY (or a per-call secret) and spends ~0.007 SOL in rent + fees, plus a flat SOL deploy fee on mainnet that funds $THREE buybacks (holding $THREE halves it, then waives it; devnet is free; see three_status). The fee rides in the same transaction as the mint, so a failed mint pays nothing. Without confirm:true it returns a full preview (both JSON documents, the paying wallet, every cost line including the fee and its recipient) and broadcasts NOTHING. For Phantom/Solflare users, use prepare_agent_mint.

NameTypeReqDescription
activeboolean–Registration active flag. Default true.
add_blockerboolean–Attach AddBlocker so no further plugins can be added. Default false.
attributesarray–On-chain Attributes plugin entries (real bytes in the asset account).
collection––Mint into this Metaplex Core collection. The signer must be the collection authority.
confirmboolean–Must be true to broadcast. Anything else returns a spend-nothing preview.
descriptionstring–What this agent is or does. Stored in the EIP-8004 registration document.
external_urlstring–Optional external_url in the asset metadata (e.g. the agent home page).
imagestring–Thumbnail/avatar image URL (PNG or similar). Shown on metaplex.com/agents, wallets, and explorers.
immutable_metadataboolean–Attach the ImmutableMetadata plugin so the metadata can never change. Default true (Genesis style).
metadata_attributesarray–Off-chain attributes array inside the asset metadata JSON (trait_type/value pairs).
metadata_uristring–Full override for the asset metadata URI (https or data:). Skips the built-in metadata builder.
model_urlstring–3D model URL (GLB). Written as the asset metadata animation_url and as model.uri in the registration, Genesis style.
namestringyesAgent name. Becomes the Core asset name and the registration name.
networkstring–Solana cluster. Defaults to the configured network (mainnet unless overridden).
ownerstring–Mint the asset to this owner instead of the signing wallet.
permanent_burnboolean–Attach PermanentBurnDelegate. Default false.
permanent_freezeboolean–Attach PermanentFreezeDelegate (unfrozen). Default false.
permanent_transferboolean–Attach PermanentTransferDelegate. Default false.
registration_uristring–Full override for the Agent Identity registration URI (https or data:). Skips the built-in registration builder.
registrationsarray–External registry registrations. Defaults to the chain registry entry, or the three.ws entry when threews_agent_id is set.
royalty_basis_pointsinteger–Royalty in basis points. Default 500 (5%), the Genesis value. 0 removes the Royalties plugin.
royalty_creatorsarray–Royalty split. Percentages must sum to 100. Defaults to the signing wallet at 100%.
secretstring–Per-call signing key (base58 secret key or JSON byte array). Overrides SOLANA_SECRET_KEY.
servicesarray–Services the agent offers, listed on its Metaplex agent page ({name, endpoint}).
supported_trustarray–Trust models the agent supports. Default ['reputation'] (Genesis style).
threews_agent_idstring–three.ws agent UUID. Adds the Genesis-exact registration entry {agentId, agentRegistry: "https://three.ws"}.
verified_creatorboolean–Attach the VerifiedCreators plugin with the signing wallet verified. Default true (Genesis style).
x402_supportboolean–Advertise x402 payment support in the registration document. Default false.

No output schema declared.

No examples provided.

prepare_agent_mint ~836

Build the exact Genesis-style mint+register flow (Metaplex Core asset + Agent Identity) for an EXTERNAL Solana wallet: Phantom, Solflare, Backpack, Ledger, anything. Needs no secret key. Returns unsigned transactions base64 in txs_base64 (already co-signed by the new asset keypair) with `wallet` as the fee payer: one atomic tx when it fits Solana's size limit, else create + register to sign together via signAllTransactions. The wallet signs and broadcasts, or hands the signed array to send_signed_transaction. Includes the same mainnet deploy fee as mint_onchain_agent, priced against the wallet's live $THREE balance and returned as deploy_fee_sol/deploy_fee_to before anything is signed. Broadcasts nothing itself. The blockhash expires after roughly a minute, so sign promptly and re-prepare if a wallet reports an expired transaction.

NameTypeReqDescription
activeboolean–Registration active flag. Default true.
add_blockerboolean–Attach AddBlocker so no further plugins can be added. Default false.
attributesarray–On-chain Attributes plugin entries (real bytes in the asset account).
collection––Mint into this Metaplex Core collection. The signer must be the collection authority.
descriptionstring–What this agent is or does. Stored in the EIP-8004 registration document.
external_urlstring–Optional external_url in the asset metadata (e.g. the agent home page).
imagestring–Thumbnail/avatar image URL (PNG or similar). Shown on metaplex.com/agents, wallets, and explorers.
immutable_metadataboolean–Attach the ImmutableMetadata plugin so the metadata can never change. Default true (Genesis style).
metadata_attributesarray–Off-chain attributes array inside the asset metadata JSON (trait_type/value pairs).
metadata_uristring–Full override for the asset metadata URI (https or data:). Skips the built-in metadata builder.
model_urlstring–3D model URL (GLB). Written as the asset metadata animation_url and as model.uri in the registration, Genesis style.
namestringyesAgent name. Becomes the Core asset name and the registration name.
networkstring–Solana cluster. Defaults to the configured network (mainnet unless overridden).
ownerstring–Mint the asset to this owner instead of the signing wallet.
permanent_burnboolean–Attach PermanentBurnDelegate. Default false.
permanent_freezeboolean–Attach PermanentFreezeDelegate (unfrozen). Default false.
permanent_transferboolean–Attach PermanentTransferDelegate. Default false.
registration_uristring–Full override for the Agent Identity registration URI (https or data:). Skips the built-in registration builder.
registrationsarray–External registry registrations. Defaults to the chain registry entry, or the three.ws entry when threews_agent_id is set.
royalty_basis_pointsinteger–Royalty in basis points. Default 500 (5%), the Genesis value. 0 removes the Royalties plugin.
royalty_creatorsarray–Royalty split. Percentages must sum to 100. Defaults to the signing wallet at 100%.
servicesarray–Services the agent offers, listed on its Metaplex agent page ({name, endpoint}).
supported_trustarray–Trust models the agent supports. Default ['reputation'] (Genesis style).
threews_agent_idstring–three.ws agent UUID. Adds the Genesis-exact registration entry {agentId, agentRegistry: "https://three.ws"}.
verified_creatorboolean–Attach the VerifiedCreators plugin with the signing wallet verified. Default true (Genesis style).
walletstringyesThe base58 address of the wallet that will sign, pay, and own the agent.
x402_supportboolean–Advertise x402 payment support in the registration document. Default false.

No output schema declared.

No examples provided.

register_agent_identity ~382

Give an ALREADY-MINTED Metaplex Core asset its Agent Identity: writes the EIP-8004 registration document (as a self-contained data: URI) onto the asset and creates its identity PDA, after which it appears on metaplex.com/agents. The signing wallet must be the asset authority (or the collection authority for collection-bound assets). Registration is one-time per asset and costs ~0.003 SOL; an already-registered asset returns already_registered without spending. Without confirm:true it returns a spend-nothing preview. To mint a NEW agent, use mint_onchain_agent or prepare_agent_mint instead.

NameTypeReqDescription
activeboolean–Registration active flag. Default true.
assetstringyesThe Core asset address to register.
collectionstring–The collection address, required for collection-bound assets.
confirmboolean–Must be true to broadcast. Anything else returns a preview.
descriptionstring–Agent description.
imagestring–Thumbnail image URL.
model_urlstring–3D model URL (GLB), written as model.uri.
namestringyesAgent name for the registration document.
networkstring–Cluster. Defaults to the configured network.
registration_uristring–Full override for the registration URI (https or data:).
registrationsarray–External registry entries. Defaults to the chain registry entry.
secretstring–Per-call signing key. Overrides SOLANA_SECRET_KEY.
servicesarray–Services the agent offers.
supported_trustarray–Default ['reputation'].
threews_agent_idstring–three.ws agent UUID for the Genesis-exact three.ws registration entry.
x402_supportboolean–Advertise x402 payment support. Default false.

No output schema declared.

No examples provided.

send_signed_transaction ~146

Broadcast one or more fully signed Solana transactions (base64) IN ORDER, polling each to confirmation before the next. Use it to complete the prepare_agent_mint flow: pass the wallet-signed txs_base64 array and the create/register sequencing (including the propagation race) is handled. Whatever the transactions do on-chain happens for real, so only send bytes you built and inspected.

NameTypeReqDescription
networkstring–Cluster to broadcast on. Defaults to the configured network.
tx_base64string–A single fully signed transaction, base64 encoded.
txs_base64array–Fully signed transactions to broadcast in order (e.g. create then register).

No output schema declared.

No examples provided.

three_status ~157

What the next on-chain deploy costs and why. Returns the deploy-fee schedule (a flat SOL fee on mainnet, free on devnet), the live $THREE balance of a wallet and the tier it earns (half price, then free), the wallet the fee is paid to, and the live $THREE market + buyback figures from the public three.ws ledger. Pass `wallet` to price a specific payer, or omit it to price the configured signer. Read-only: it moves nothing and needs no key.

NameTypeReqDescription
networkstring–Cluster. Defaults to the configured network. Devnet deploys are always free.
walletstring–Price the deploy fee for this wallet. Defaults to the configured signer.

No output schema declared.

No examples provided.

Install

How do I install the Metaplex Agent Registry MCP server?

Metaplex Agent Registry runs locally as an npm package, launched with npx -y @three-ws/metaplex-agent-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/metaplex-agent-mcp

# add to Claude Code
claude mcp add nirholas-metaplex-agent -- npx -y @three-ws/metaplex-agent-mcp
Common questions

What is the Metaplex Agent Registry MCP server?

Metaplex Agent Registry is an MCP server listed in the public MCP registry as io.github.nirholas/metaplex-agent. Deploy AI agents on-chain on Solana with an EIP-8004 identity. Deploy fee funds $THREE buybacks. This page covers its npm package (@three-ws/metaplex-agent-mcp).

Is the Metaplex Agent Registry MCP server safe to use?

Metaplex Agent Registry scores 77 out of 100 on VerifyMCP. We recorded 5 known advisories against it as of 5 November 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 Metaplex Agent Registry MCP server expose?

Metaplex Agent Registry exposes 9 tools: mint_onchain_agent, prepare_agent_mint, send_signed_transaction, register_agent_identity, get_onchain_agent, and 4 more. Their descriptions and schemas cost roughly 3,133 tokens of context every time the server is loaded.

Is the Metaplex Agent Registry MCP server still maintained?

Metaplex Agent Registry is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Metaplex Agent Registry MCP server under?

Metaplex Agent Registry declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.