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(finish): close order 964 after re-verifying it already shipped
nirholase92cf7c855e5
diff --git a/prompts/finish/964-mcp-annotations-and-tool-count.md b/prompts/finish/964-mcp-annotations-and-tool-count.mddeleted file mode 100644index 2720e8b54..000000000--- a/prompts/finish/964-mcp-annotations-and-tool-count.md+++ /dev/null@@ -1,9 +0,0 @@-Our MCP surface is big and uneven. Estimated annotation coverage is high but not complete: api/_mcp-studio/catalog-tools.js has none, discovery and home tools are unmarked, and several tool files have partial readOnly and idempotent hints. api/_mcp/prompts.js names tools that are not registered (perps_markets, swap_quote and others), so some prompts point at nothing. There is no single published tool count; READMEs say 15 and 16 while the registry in api/_mcpall/registry.js mounts far more.--Make the surface trustworthy. Add a test that loads every MCP server, enumerates every tool, and fails unless each has all four hints set deliberately (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) and a description with a when-to-use line. Add a test that every tool, resource and prompt referenced by any prompt actually exists, and fix every dangling reference (register the tool if it belongs, or correct the prompt). Compute the real totals (tools, resources, prompts, per server) at build time and at request time and publish them on /mcp-tools and in tools.json with a how-it-is-calculated note; update every README and doc that quotes a number so none can drift, with a check that fails the build on a mismatch.--Add per-tool pages with schema, example call, price and a try-it for free read-only tools, search and filters by category, and a diff of tools added in each release for the changelog. Wire the checks into npm run gate.-------This brief is standalone. Assume no other brief has run, and keep working if others run at the same time: use names unique to this work for tables, routes and files, give migrations a fresh timestamp, append to shared files instead of rewriting them, and re-read a shared file before you edit it. CLAUDE.md governs everything, including its spend gate (anything that signs or moves funds shows recipient, amount, asset and chain and waits for an explicit yes; test with devnet, simulation or paper mode) and the rule that nothing naming another crypto project is committed without the owner's approval, so list any new third-party names you introduce in your report. Never name any competitor in a committed file. Finish it fully: wire it, document it, add the changelog entry, verify it for real, and report what you observed.