Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.
JavaScript 3d-generationai-agentsanimationavatardigital-humangenerative-aiglbgltfimage-to-3dllmmcpmcp-servermodel-context-protocolsolanatext-to-3dthreejsweb-componentswebglwebxrx402
docs(solana-memo-media): write the full MCP guide, map the package, and announce the memo image tools
nirholas280bfeededbb
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex c70321c5c..020c13355 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -4,6 +4,10 @@Public history for [three.ws](https://three.ws), newest first. New pages come from `added` dates in data/pages.json; everything else is curated in data/changelog.json. Also available as [JSON](https://three.ws/changelog.json) and [RSS](https://three.ws/changelog.xml), live at [three.ws/changelog](https://three.ws/changelog).+## 2026-09-17++- **Ask your AI assistant to show the picture inside a Solana transaction**: Some Solana transactions carry a small image written straight into their memo, which explorers show as thousands of characters of unreadable text. A new free MCP server, @three-ws/solana-memo-media-mcp, lets Claude, Cursor or any other MCP client fetch a transaction by its signature and show you the image directly, alongside who signed it and a fingerprint of the exact bytes. It can also scan an account's recent history and pick out only the transactions that carry images. It needs no account, key or wallet, never writes anything, and only shows PNG, JPEG, WebP and GIF files whose contents match their label. The Onchain Viewer at /onchain was also fixed: it only recognised the newest memo program, so memos written through the standard Solana memo program were reported as missing. It now reads all three. (`/docs/mcp-solana-memo-media`) `[feature, fix]`+## 2026-09-16- **Docs · The /launch launchpad** (`/docs/launchpad`): How three.ws/launch launches a pump.fun coin for a 3D agent: agent-linked metadata, the 1% dev-buy fee, v0 lookup-table and Solana transaction v1 formats, claiming creator rewards on three.ws, and the API behind it.diff --git a/STRUCTURE.md b/STRUCTURE.mdindex fe2ee834a..dc327aba2 100644--- a/STRUCTURE.md+++ b/STRUCTURE.md@@ -460,6 +460,7 @@ array. Runbook: [docs/contributing.md](docs/contributing.md#publishing-packages-| `@three-ws/mocap` | [packages/mocap/](packages/mocap) | `api/mocap/` | Motion-capture clips → avatar animation || `@three-ws/strategies` | [packages/strategies/](packages/strategies) | `api/strategies.js`, `dca-strategies.js`, copy/mirror engines | Automated trading strategies (DCA, copy, mirror) || `@three-ws/home-mcp` | [packages/home-mcp/](packages/home-mcp) | `packages/home-bridge`, `scripts/home-test-instance.mjs` | An MCP server that runs a real Home Assistant house from any assistant: rooms and live state, the household's own scenes, and gated service calls. Over stdio the gate REFUSES anything that opens the house, because an MCP client has no person in it to confirm one; the only way through is `HOME_ALLOWED_ENTITIES`, set by hand by whoever starts the process. Imports the gate from `@three-ws/home-bridge` rather than keeping a second copy |+| `@three-ws/solana-memo-media-mcp` | [packages/solana-memo-media-mcp/](packages/solana-memo-media-mcp) | [public/onchain/index.html](public/onchain/index.html) `→ /onchain` | Keyless, read-only MCP server that returns image data URIs embedded in Solana Memo instructions (SPL Memo v1, v2, and the v1-transaction memo program) as validated inline images with signer and SHA-256; address scans pre-filter on the memo summary so 1,000 signatures cost a few RPC calls. Docs: [docs/mcp-solana-memo-media.md](docs/mcp-solana-memo-media.md) || `@three-ws/pumpfun-skills` | [packages/pumpfun-skills/](packages/pumpfun-skills) | [pump-fun-skills/](pump-fun-skills) | pump.fun create-coin / swap / fees skills (runtime mint) || `@three-ws/portal` | [packages/portal/](packages/portal) | `api/portal` | Any website as a walkable 3D world: pure layout, API client, CLI, MCP server || `@three-ws/home-bridge` | [packages/home-bridge/](packages/home-bridge) | `docs/smart-home.md` | The agent's connection to a real house. Live Home Assistant entity state and service calls over the first-party WebSocket API, the user's own curated tools over the `mcp_server` MCP endpoint, a floor/area/entity room graph with per-room lighting, climate and security rollups for the 3D scene, household macros resolved to the scenes the user already built, and a physical-action gate that never lets an unlock through without an explicit yes. Zero device code: Home Assistant owns Zigbee, Z-Wave, Matter, Thread and the other 1,500 integrations. Docs: [docs/smart-home.md](docs/smart-home.md) |diff --git a/data/changelog.json b/data/changelog.jsonindex 2397b99fa..4dbca3078 100644--- a/data/changelog.json+++ b/data/changelog.json@@ -1,6 +1,16 @@{"$comment": "Curated changelog entries for three.ws, the editorial layer of the public changelog. New PAGE launches are tracked automatically via the `added` field in data/pages.json; this file is for everything else holders care about: improvements, fixes, SDK releases, trading/payments capabilities, security work. scripts/build-page-index.mjs merges both sources into CHANGELOG.md, public/changelog.json, and public/changelog.xml. Newest first. Allowed tags: feature, improvement, fix, sdk, infra, docs, security. `link` is optional and must be a live three.ws path.","entries": [+ {+ "date": "2026-09-17",+ "title": "Ask your AI assistant to show the picture inside a Solana transaction",+ "summary": "Some Solana transactions carry a small image written straight into their memo, which explorers show as thousands of characters of unreadable text. A new free MCP server, @three-ws/solana-memo-media-mcp, lets Claude, Cursor or any other MCP client fetch a transaction by its signature and show you the image directly, alongside who signed it and a fingerprint of the exact bytes. It can also scan an account's recent history and pick out only the transactions that carry images. It needs no account, key or wallet, never writes anything, and only shows PNG, JPEG, WebP and GIF files whose contents match their label. The Onchain Viewer at /onchain was also fixed: it only recognised the newest memo program, so memos written through the standard Solana memo program were reported as missing. It now reads all three.",+ "tags": [+ "feature",+ "fix"+ ],+ "link": "/docs/mcp-solana-memo-media"+ },{"date": "2026-09-16","title": "A flat 1% fee on trades made through three.ws",diff --git a/docs/mcp-solana-memo-media.md b/docs/mcp-solana-memo-media.mdindex 822b95b09..a28df8b22 100644--- a/docs/mcp-solana-memo-media.md+++ b/docs/mcp-solana-memo-media.md@@ -1,5 +1,138 @@# Solana Memo Media MCP-`@three-ws/solana-memo-media-mcp` turns embedded image data URIs in Solana SPL Memo instructions into safe inline MCP images. It removes the copy-paste path through a data-URI converter while retaining the transaction signature, immutable digest, and validation result needed for provenance.+`@three-ws/solana-memo-media-mcp` lets an AI assistant show you the image embedded in a Solana transaction. Some Solana transactions carry a small image written straight into a Memo instruction as a `data:image/png;base64,...` string. Explorers such as Solscan display that as unreadable text, so seeing the picture used to mean copying a few thousand characters into an online converter. With this server installed you give your assistant a transaction signature and the image comes back inline, validated, with the signer and a SHA-256 digest beside it.-Install it with `claude mcp add solana-memo-media -- npx -y @three-ws/solana-memo-media-mcp`. See the package [README](../packages/solana-memo-media-mcp/README.md) for every tool, parameter, safety limit, and RPC configuration option.+It is keyless and read-only. It never signs, sends, uploads, or stores anything, and it decodes every payload locally inside the MCP process.++Prefer a browser? The [Onchain Viewer](/onchain) does the same thing for one transaction at a time, with a shareable `https://three.ws/onchain/?tx=<signature>` link.++## Who it is for++- **Developers** building on memo media: decode a payload before you write it, confirm the bytes and dimensions, and check what a client will actually render.+- **Traders and communities** following an account that posts images on-chain: scan its recent transactions and see only the ones that carry media.+- **Anyone** handed a signature and told "there's a picture in it": ask your assistant and look.++## Install++Claude Code:++```bash+claude mcp add solana-memo-media -- npx -y @three-ws/solana-memo-media-mcp+```++Claude Desktop, Cursor, or any other stdio MCP client:++```json+{+ "mcpServers": {+ "solana-memo-media": {+ "command": "npx",+ "args": ["-y", "@three-ws/solana-memo-media-mcp"]+ }+ }+}+```++Node.js 20 or newer is required. No account, API key, or wallet is needed.++## Tools++| Tool | Network | What it does |+| --- | --- | --- |+| `extract_solana_memo_media` | Solana RPC | Fetches one transaction and returns every supported image found in its Memo instructions. |+| `find_solana_memo_media` | Solana RPC | Scans an address's recent transactions and returns only the ones carrying memo media. |+| `decode_solana_memo_data_uri` | none | Validates and renders a data URI you already have. |+| `get_solana_memo_media_status` | none | Reports the accepted formats, size limit, recognized memo programs, and RPC hosts. |++### `extract_solana_memo_media`++| Argument | Type | Required | Meaning |+| --- | --- | --- | --- |+| `signature` | string | yes | Base58 transaction signature. |++Legacy, version 0, and version 1 transactions are all read (the request sets `maxSupportedTransactionVersion: 1`) at `confirmed` commitment. Both top-level and inner (CPI) Memo instructions are inspected. A response looks like this, followed by one MCP `image` content block per asset:++```json+{+ "ok": true,+ "signature": "4HV6mCx7KoPetuqZg9MrVDuRPCff26hdh1oaCsgQuhrb8EtuPeerehFuUdMG8S73Pmc4zremfpTs59y49z4cLSUT",+ "slot": 447178301,+ "block_time": 1789452675,+ "transaction_version": 1,+ "signer": "THREEZmp7v26VbpQ8B27bBaLNA2zMyaNHWpkQtJkrgd",+ "memo_count": 1,+ "assets": [+ {+ "mime_type": "image/png",+ "byte_length": 2852,+ "sha256": "7ab8feefae765acbbae463ab7d0cd66030a2918c22900f9bab33b7199cee1349",+ "dimensions": { "width": 42, "height": 48 },+ "source": "spl_memo"+ }+ ],+ "rejected": []+}+```++`signer` is the fee payer, the first signing account. A memo that looks like a data URI but fails validation appears in `rejected` with a code (`unsupported_media_type`, `media_too_large`, `media_signature_mismatch`, `invalid_data_uri`), and its bytes are never returned. The raw data URI is deliberately not echoed into the text output, so it does not flood the assistant's context.++### `find_solana_memo_media`++| Argument | Type | Required | Meaning |+| --- | --- | --- | --- |+| `address` | string | yes | Wallet, token account, or program address. |+| `limit` | integer, 1 to 1000 | no | Recent signatures to scan. Default 100. |+| `before` | string | no | Continue from the previous response's `next_before`. |++The scan is cheap by design. `getSignaturesForAddress` already returns a short summary of each transaction's memos, so only signatures whose summary contains a data URI are fetched in full. Scanning 1,000 recent signatures on a busy memo program measured two RPC calls, not 1,001. The response reports `scanned`, `candidates`, `match_count`, `matches` (each shaped like an `extract_solana_memo_media` result), per-signature `failures`, and `next_before` for paging back through history (`null` when there is nothing older).++Pass a memo program id as the address to watch every memo written through that program, for example `Memo4c2pN8afCj432Lb7RMVKi9PbQnnW7ewFFaV3oAH`.++### `decode_solana_memo_data_uri`++| Argument | Type | Required | Meaning |+| --- | --- | --- | --- |+| `dataUri` | string | yes | A complete `data:<mime>;base64,<payload>` string. |++Runs the same validation as the network tools with no RPC call. Use it to check a payload before you write it to a transaction.++## Recognized memo programs++| Program id | Program |+| --- | --- |+| `Memo1UhkJRfHyvLMcVLMbLJYfW2tfU8G8H4PqvV6v8` | SPL Memo v1 |+| `MemoSq4gqABAXKb96qnH8TysNcWxMyWCqXgDLGmfcHr` | SPL Memo v2 |+| `Memo4c2pN8afCj432Lb7RMVKi9PbQnnW7ewFFaV3oAH` | The newer memo program carried by version 1 transactions |++An instruction is read only when its program id is on this list or the RPC's parser labels it `spl-memo`. A program whose id merely resembles a memo program is ignored.++## Safety++A Memo is arbitrary text that anyone can sign. A data URI inside one is a convention, not a Solana media standard, and its presence proves only that those bytes appeared in that transaction.++- Only `image/png`, `image/jpeg`, `image/webp`, and `image/gif` are accepted. SVG, HTML, PDF, and every other active or document format are refused, because they can carry script.+- The base64 must be canonical and padded, and the decoded size is checked against the 262,144-byte cap before decoding.+- The declared MIME type must match the file signature (PNG header, JPEG start-of-image marker, `GIF87a`/`GIF89a`, or `RIFF....WEBP`). A PNG label on GIF bytes is rejected.+- Every asset carries a SHA-256 digest, so you can cite the exact bytes.+- Memo content is untrusted data. Treat instructions, links, or claims inside an image the way you would a stranger's post, and check the `signer` before believing who wrote it.++## RPC configuration++Endpoints are tried in order until one answers: every entry in `SOLANA_RPC_URLS`, then `SOLANA_RPC_URL`, then the public mainnet endpoints (`api.mainnet-beta.solana.com`, `solana-rpc.publicnode.com`, `rpc.ankr.com/solana`). Each request times out after 12 seconds before failing over.++| Variable | Required | Meaning |+| --- | --- | --- |+| `SOLANA_RPC_URLS` | no | Comma-separated ordered failover list. |+| `SOLANA_RPC_URL` | no | One primary endpoint. |++Public endpoints rate-limit heavy scans. For large sweeps, set your own RPC:++```bash+claude mcp add solana-memo-media -e SOLANA_RPC_URL=https://your-rpc.example -- npx -y @three-ws/solana-memo-media-mcp+```++## Related++- [Onchain Viewer](/onchain): the same decoding in a browser page, documented in [Solana on three.ws](./solana.md#viewing-files-written-in-a-transaction-memo).+- [MCP overview](./mcp.md): every three.ws MCP server.+- Package source and tests: [packages/solana-memo-media-mcp](../packages/solana-memo-media-mcp/README.md).diff --git a/public/changelog-recent.json b/public/changelog-recent.jsonindex cd5a59dde..6f2f3a9b0 100644--- a/public/changelog-recent.json+++ b/public/changelog-recent.json@@ -1,14 +1,25 @@{- "generated_at": "2026-09-16T21:09:38.691Z",+ "generated_at": "2026-09-17T01:21:37.042Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws","url": "https://three.ws"},- "total": 3688,+ "total": 3689,"complete": false,"full_feed": "/changelog.json","entries": [+ {+ "date": "2026-09-17",+ "type": "update",+ "title": "Ask your AI assistant to show the picture inside a Solana transaction",+ "summary": "Some Solana transactions carry a small image written straight into their memo, which explorers show as thousands of characters of unreadable text. A new free MCP server, @three-ws/solana-memo-media-mcp, lets Claude, Cursor or any other MCP client fetch a transaction by its signature and show you the image directly, alongside who signed it and a fingerprint of the exact bytes. It can also scan an account's recent history and pick out only the transactions that carry images. It needs no account, key or wallet, never writes anything, and only shows PNG, JPEG, WebP and GIF files whose contents match their label. The Onchain Viewer at /onchain was also fixed: it only recognised the newest memo program, so memos written through the standard Solana memo program were reported as missing. It now reads all three.",+ "link": "/docs/mcp-solana-memo-media",+ "tags": [+ "feature",+ "fix"+ ]+ },{"date": "2026-09-16","type": "launch",@@ -1609,16 +1620,6 @@"tags": ["launch"]- },- {- "date": "2026-09-07",- "type": "launch",- "title": "My Creations",- "summary": "Everything you have made on three.ws in one newest-first grid: the agents you built, the 3D avatars you saved, and every model you forged, including models forged in this browser before you had an account. Open, edit, or copy a link to any of them in one click.",- "link": "/mine",- "tags": [- "launch"- ]}]}diff --git a/public/changelog.json b/public/changelog.jsonindex 85ec38a46..4fa8cbf50 100644--- a/public/changelog.json+++ b/public/changelog.json@@ -1,11 +1,22 @@{- "generated_at": "2026-09-16T21:09:38.669Z",+ "generated_at": "2026-09-17T01:21:37.021Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws","url": "https://three.ws"},"entries": [+ {+ "date": "2026-09-17",+ "type": "update",+ "title": "Ask your AI assistant to show the picture inside a Solana transaction",+ "summary": "Some Solana transactions carry a small image written straight into their memo, which explorers show as thousands of characters of unreadable text. A new free MCP server, @three-ws/solana-memo-media-mcp, lets Claude, Cursor or any other MCP client fetch a transaction by its signature and show you the image directly, alongside who signed it and a fingerprint of the exact bytes. It can also scan an account's recent history and pick out only the transactions that carry images. It needs no account, key or wallet, never writes anything, and only shows PNG, JPEG, WebP and GIF files whose contents match their label. The Onchain Viewer at /onchain was also fixed: it only recognised the newest memo program, so memos written through the standard Solana memo program were reported as missing. It now reads all three.",+ "link": "/docs/mcp-solana-memo-media",+ "tags": [+ "feature",+ "fix"+ ]+ },{"date": "2026-09-16","type": "launch",diff --git a/public/changelog.xml b/public/changelog.xmlindex 77bdcd2cc..f96bdb5a6 100644--- a/public/changelog.xml+++ b/public/changelog.xml@@ -6,6 +6,14 @@<atom:link href="https://three.ws/changelog.xml" rel="self" type="application/rss+xml"/><description>What's new on three.ws: features, improvements, and releases, newest first.</description><language>en</language>+ <item>+ <title>Ask your AI assistant to show the picture inside a Solana transaction</title>+ <link>https://three.ws/docs/mcp-solana-memo-media</link>+ <guid isPermaLink="false">2026-09-17:Ask your AI assistant to show the picture inside a Solana transaction</guid>+ <pubDate>Thu, 17 Sep 2026 12:00:00 GMT</pubDate>+ <category>feature</category>+ <description>Some Solana transactions carry a small image written straight into their memo, which explorers show as thousands of characters of unreadable text. A new free MCP server, @three-ws/solana-memo-media-mcp, lets Claude, Cursor or any other MCP client fetch a transaction by its signature and show you the image directly, alongside who signed it and a fingerprint of the exact bytes. It can also scan an account's recent history and pick out only the transactions that carry images. It needs no account, key or wallet, never writes anything, and only shows PNG, JPEG, WebP and GIF files whose contents match their label. The Onchain Viewer at /onchain was also fixed: it only recognised the newest memo program, so memos written through the standard Solana memo program were reported as missing. It now reads all three.</description>+ </item><item><title>Docs · The /launch launchpad</title><link>https://three.ws/docs/launchpad</link>diff --git a/public/features.json b/public/features.jsonindex 7591c7ab8..a39b36645 100644--- a/public/features.json+++ b/public/features.json@@ -1,5 +1,5 @@{- "generated_at": "2026-09-16T21:09:38.654Z",+ "generated_at": "2026-09-17T01:21:37.004Z","generated_by": "scripts/build-page-index.mjs from data/pages.json","site": {"name": "three.ws",diff --git a/public/mcp-catalog.json b/public/mcp-catalog.jsonindex 60ee6379b..01789f1e0 100644--- a/public/mcp-catalog.json+++ b/public/mcp-catalog.json@@ -9647,7 +9647,7 @@{"name": "extract_solana_memo_media","title": "Extract media from a Solana transaction memo",- "description": "Fetch a finalized Solana transaction, inspect top-level and inner SPL Memo instructions, and render every supported embedded image data URI inline. The response always identifies the source signature and reports rejected media without returning unsafe bytes. This is chain data, not a claim of authorship or safety.",+ "description": "Fetch a confirmed Solana transaction (legacy, v0, or v1), inspect top-level and inner SPL Memo instructions, and render every supported embedded image data URI inline. The response identifies the source signature, fee payer, slot, and transaction version, and reports rejected media without returning unsafe bytes. This is chain data, not a claim of authorship or safety.","server": {"id": "solana-memo-media-mcp","title": "@three-ws/solana-memo-media-mcp",@@ -9659,7 +9659,7 @@"annotations": {"readOnlyHint": true,"destructiveHint": null,- "idempotentHint": false,+ "idempotentHint": true,"openWorldHint": true},"price": {@@ -9673,7 +9673,7 @@"type": "string","minLength": 32,"maxLength": 128,- "description": "Finalized Solana transaction signature in base58."+ "description": "Solana transaction signature in base58."}},"required": [@@ -9686,7 +9686,7 @@{"name": "find_solana_memo_media","title": "Find recent memo media for a Solana address",- "description": "Search a public Solana address’s recent finalized transactions and return only validated image data URIs carried by SPL Memo instructions. It is intentionally bounded to limit RPC load. Use the returned signatures to verify provenance in an explorer.",+ "description": "Scan a Solana address's recent confirmed transactions and return only validated image data URIs carried by SPL Memo instructions. Signatures whose memo summary holds no data URI are skipped without fetching the transaction, so a scan costs one RPC call plus one per candidate. Pass a memo program id as the address to watch every memo written to it. Use the returned signatures to verify provenance in an explorer.","server": {"id": "solana-memo-media-mcp","title": "@three-ws/solana-memo-media-mcp",@@ -9717,9 +9717,15 @@"limit": {"type": "integer","minimum": 1,- "maximum": 20,- "default": 10,- "description": "Recent finalized signatures to inspect, from 1 to 20 (default 10)."+ "maximum": 1000,+ "default": 100,+ "description": "Recent signatures to scan, from 1 to 1000 (default 100)."+ },+ "before": {+ "type": "string",+ "minLength": 32,+ "maxLength": 128,+ "description": "Continue the scan from signatures older than this one (the previous response's next_before)."}},"required": [@@ -9732,7 +9738,7 @@{"name": "get_solana_memo_media_status","title": "Solana memo media capability",- "description": "Report the local decoding policy and ordered Solana RPC failover hosts. No network call is made and no data is stored.",+ "description": "Report the local decoding policy, recognized memo programs, and ordered Solana RPC failover hosts. No network call is made and no data is stored.","server": {"id": "solana-memo-media-mcp","title": "@three-ws/solana-memo-media-mcp",