@three-ws/metaplex-agent-mcp

MCPcommunity
v0.2.0io.github.nirholasUnknownUpdated 1mo agonpmGitHub

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

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
1mo agoLast update
Package
Authorio.github.nirholas
LicenseUnknown
Version0.2.0
Sourcenpm+mcp-registry
npm@three-ws/metaplex-agent-mcp
GitHubnirholas/three.ws
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface10 tools · none privileged
Security scan✓ Cleanv0.2.0 · 1mo agoHow well does this scan work?
EvalsNone
IndexedAug 19, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

10 tools · none privileged
Statically extracted from the published packagev0.2.0 · 1mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

agent_walletShow a wallet address and its live SOL balance. Pass `asset` to derive an on-chain agent's built-in wallet

Show a wallet address and its live SOL balance. Pass `asset` to derive an on-chain agent's built-in wallet

No input schema was published for this tool.

build_registrationBuild the Genesis-style EIP-8004 registration-v1 JSON document and its self-contained

Build the Genesis-style EIP-8004 registration-v1 JSON document and its self-contained

No input schema was published for this tool.

get_onchain_agentFetch a Metaplex Agent Registry agent by its Core asset address: name, owner, update authority, plugins

Fetch a Metaplex Agent Registry agent by its Core asset address: name, owner, update authority, plugins

No input schema was published for this tool.

metaplex-agent-mcpNo description published

This tool published no description. Forge does not invent one.

list_onchain_agentsThe latest agents to land on-chain in the Metaplex Agent Registry, newest first, from the live three.ws

The latest agents to land on-chain in the Metaplex Agent Registry, newest first, from the live three.ws

No input schema was published for this tool.

mint_onchain_agentDeploy an AI agent on-chain, Genesis-333 style: mints a Metaplex Core asset (data: URI metadata, verified

Deploy an AI agent on-chain, Genesis-333 style: mints a Metaplex Core asset (data: URI metadata, verified

No input schema was published for this tool.

prepare_agent_mintBuild the exact Genesis-style mint+register flow (Metaplex Core asset + Agent Identity) for an EXTERNAL

Build the exact Genesis-style mint+register flow (Metaplex Core asset + Agent Identity) for an EXTERNAL

No input schema was published for this tool.

register_agent_identityGive an ALREADY-MINTED Metaplex Core asset its Agent Identity: writes the EIP-8004 registration document

Give an ALREADY-MINTED Metaplex Core asset its Agent Identity: writes the EIP-8004 registration document

No input schema was published for this tool.

send_signed_transactionBroadcast one or more fully signed Solana transactions (base64) IN ORDER, polling each to confirmation

Broadcast one or more fully signed Solana transactions (base64) IN ORDER, polling each to confirmation

No input schema was published for this tool.

three_statusWhat the next on-chain deploy costs and why. Returns the deploy-fee schedule (a flat SOL fee on mainnet,

What the next on-chain deploy costs and why. Returns the deploy-fee schedule (a flat SOL fee on mainnet,

No input schema was published for this tool.

9 of 10 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

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

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

10 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-01 — observed resolution, not a publisher declaration.

60 packages resolved · 8 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

60 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+48 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.