GrowBlocks Dev Kit
NPM · GROWBLOCKS
Build, play-test with screenshots, and ship three.js browser games on GrowBlocks.
Available components
Last scanned (15 hours ago)
Scores higher than 38% of npm servers
Category Entertainment and Games
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency32
- 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
- Licence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.Unverified
- Actively maintained (last published 7 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1486 tokens (~82/item across 18 items; 16 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage85
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 54% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 16 Oct 26 66
First indexed and scored.
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 24 Oct 2026 · Analysed npm/growblocks@1.2.0
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 →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
growblocks_add_block Add a block to the game ~128
Add a block to the game: copies its files into blocks/<slug>/ and records it in growblocks.json. Then import it from ./blocks/<slug>/<entry> and read its code for how to use it. Do not edit the block files: GrowBlocks recognises the block by them and its author earns from the game (paid by GrowBlocks; the game keeps its 70%). To change one, publish a fork.
| Name | Type | Req | Description |
|---|---|---|---|
| block | string | yes | slug or slug@version |
| dir | string | – | The game folder (default: the folder the assistant runs in). |
No output schema declared.
No examples provided.
growblocks_block_info Block details ~62
One block: what it does, its versions (and what it forked), its entry file and which live games use it.
| Name | Type | Req | Description |
|---|---|---|---|
| block | string | yes | – |
| dir | string | – | The game folder (default: the folder the assistant runs in). |
No output schema declared.
No examples provided.
growblocks_blocks Search blocks ~86
Search the GrowBlocks blocks: parts of games other developers published (vehicles, game modes, enemy brains, level kits) that a game can add instead of writing them. Look here before building something common. Pass words to search names, descriptions and tags.
| Name | Type | Req | Description |
|---|---|---|---|
| dir | string | – | The game folder (default: the folder the assistant runs in). |
| query | string | – | – |
No output schema declared.
No examples provided.
growblocks_check Check and play the game ~110
Run the Dev Kit checker on the game folder. play=false: static checks (syntax, unknown gb.* calls, blocked browser APIs, imports, file limits). play=true: also plays the game headless inside GrowBlocks for some seconds, reports every runtime error and returns a screenshot. Run it after every change; fix everything it reports.
| Name | Type | Req | Description |
|---|---|---|---|
| dir | string | – | The game folder (default: the folder the assistant runs in). |
| play | boolean | – | – |
| seconds | number | – | – |
No output schema declared.
No examples provided.
growblocks_create_game Create a game on GrowBlocks ~152
Create a new game on GrowBlocks and link the folder to it. address: 3-32 lowercase letters, numbers and dashes (its URL, game.html?g=<address>). Ask the human for the name and address first. A logo (WebP, under 22 KB) and a description are needed before submitting.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| description | string | – | – |
| dir | string | – | The game folder (default: the folder the assistant runs in). |
| logo | string | – | Path to a WebP logo. |
| name | string | yes | – |
| players | number | – | Players per room, 1-16. |
| tagline | string | – | – |
No output schema declared.
No examples provided.
growblocks_docs Read the Dev Kit API ~92
The GrowBlocks Dev Kit API for writing game.js (llms.txt): the contract, every gb.* call, patterns and pitfalls. Read it before writing game code. Pass topic (e.g. "gb.physics", "gb.net", "Pitfalls") to get one section.
| Name | Type | Req | Description |
|---|---|---|---|
| dir | string | – | The game folder (default: the folder the assistant runs in). |
| topic | string | – | – |
No output schema declared.
No examples provided.
growblocks_games List my games ~62
The signed-in developer's games: status (draft, in review, live, changes needed), test and live builds with their links, and GrowBlocks' review note.
| Name | Type | Req | Description |
|---|---|---|---|
| dir | string | – | The game folder (default: the folder the assistant runs in). |
No output schema declared.
No examples provided.
growblocks_link_game Link folder to a game ~51
Link the folder to one of your existing games (writes growblocks.json).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| dir | string | – | The game folder (default: the folder the assistant runs in). |
No output schema declared.
No examples provided.
growblocks_login Sign in to GrowBlocks ~82
Start signing in to GrowBlocks. Returns a link and a code: give both to the human, who opens the link, checks the code, signs in with Google and presses Allow. The sign-in finishes in the background; check it with growblocks_whoami.
| Name | Type | Req | Description |
|---|---|---|---|
| dir | string | – | The game folder (default: the folder the assistant runs in). |
No output schema declared.
No examples provided.
growblocks_new_game New game folder ~65
Create a new game folder from the latest starter kit (game.js, play.html, check.mjs, llms.txt, gb.d.ts, this CLI and .mcp.json). Then pass that folder as dir to the other tools.
| Name | Type | Req | Description |
|---|---|---|---|
| folder | string | yes | – |
No output schema declared.
No examples provided.
growblocks_publish_block Publish a block publicly ~85
Publish the folder as a block. It needs block.json (slug, name, description, entry, tags, and forkOf if it started from another block). Others can then add it, and its author earns from every live game that ships it. Only when the human asks.
| Name | Type | Req | Description |
|---|---|---|---|
| dir | string | – | The game folder (default: the folder the assistant runs in). |
No output schema declared.
No examples provided.
growblocks_push Upload a test build ~83
Run the static checks, then upload the folder as a new test build of the linked game. Returns the unlisted test link to play and share. Does not make anything public. At most 20 uploads per game a day, so push when a change is worth testing.
| Name | Type | Req | Description |
|---|---|---|---|
| dir | string | – | The game folder (default: the folder the assistant runs in). |
No output schema declared.
No examples provided.
growblocks_status Game status and review note ~58
The status of the game this folder is linked to (growblocks.json): builds, links, review state and note, and what to do next.
| Name | Type | Req | Description |
|---|---|---|---|
| dir | string | – | The game folder (default: the folder the assistant runs in). |
No output schema declared.
No examples provided.
growblocks_submit Submit for review ~66
Submit the latest test build to GrowBlocks for review (needs a logo and a description). Only do this when the human asks: GrowBlocks plays it and approves it or sends a note.
| Name | Type | Req | Description |
|---|---|---|---|
| dir | string | – | The game folder (default: the folder the assistant runs in). |
No output schema declared.
No examples provided.
growblocks_update_game Change game details ~110
Change the linked game's name, tagline, description, studio (the name shown after "by"; empty = the developer's account name), players per room or logo.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| dir | string | – | The game folder (default: the folder the assistant runs in). |
| logo | string | – | Path to a WebP logo. |
| name | string | – | – |
| players | number | – | – |
| studio | string | – | – |
| tagline | string | – | – |
No output schema declared.
No examples provided.
growblocks_whoami Who is signed in ~60
Who the GrowBlocks CLI is signed in as, and how many games they have. Fails with "Not signed in" if login is needed.
| Name | Type | Req | Description |
|---|---|---|---|
| dir | string | – | The game folder (default: the folder the assistant runs in). |
No output schema declared.
No examples provided.
How do I install the GrowBlocks Dev Kit MCP server?
GrowBlocks Dev Kit runs locally as an npm package, launched with npx -y growblocks. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · growblocks
claude mcp add xyz-growblocks-growblocks -- npx -y growblocks
What is the GrowBlocks Dev Kit MCP server?
GrowBlocks Dev Kit is an MCP server listed in the public MCP registry as xyz.growblocks/growblocks. Build, play-test with screenshots, and ship three.js browser games on GrowBlocks. This page covers its npm package (growblocks).
Is the GrowBlocks Dev Kit MCP server safe to use?
GrowBlocks Dev Kit scores 66 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 October 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 GrowBlocks Dev Kit MCP server expose?
GrowBlocks Dev Kit exposes 16 tools: growblocks_docs, growblocks_check, growblocks_whoami, growblocks_login, growblocks_games, and 11 more. Their descriptions and schemas cost roughly 1,352 tokens of context every time the server is loaded.
Is the GrowBlocks Dev Kit MCP server still maintained?
GrowBlocks Dev Kit is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.