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.

BlockHand

NPM · @GJLMOTEA/BLOCKHAND-MCP

Minecraft Education Edition MCP server: Agent robot, 24 build shapes, events. No add-on needed.

+3 this week 82 Trust /100

Last scanned (9 hours ago)

Scores higher than 72% of npm servers

Category Entertainment and Games

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
  • 30 of 94 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to gjlmotea/blockhand-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 16 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
  • 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
  • Context-footprint check failed: tool/resource definitions use about 6018 tokens (~130/item across 46 items; 44 tools + 2 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 Management57
  • Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage84
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 43% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.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 46 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.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 24 Oct 26 −5
    • CVE-2023-54404 affects this package: high ▼ security
    • Known CVEs: pass → fail ▼ security
  • 22 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

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/@gjlmotea/blockhand-mcp@0.1.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo gjlmotea/blockhand-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/gjlmotea/blockhand-mcp/.github/workflows/release.yml@refs/tags/v0.1.1
Rekor log index 3319762071
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:b5d19f71b5a64b22f476db48cd322b27e77e977e64654a91716ffd5d5848b4acd1829c7a1bad7912ee92bd6eeafec1a2d1123e43cc839c096752c1ee3

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
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 94 packages
Packages resolved 94
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 44 exposed · ~5,083 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
mc_undo_control ~177

Note: automatic Undo is off by default. On Education 1.26.x, once it is on, the native check before the first build makes the game command channel stop responding for good (the player's typing gets no response either) until Minecraft is restarted; configure enabled=true only when the user explicitly asks for it. action=status only reads the automatic Undo state and timings; configure turns it on or off and sets the block budget (default 4096, max 32768); same-material ranges are saved as whole regions and compared with native region checks. clear releases this server's backups. Backups live only in game memory, with no disk backup and no Redo. Turning automatic backup off clears the old history.

NameTypeReqDescription
actionstring––
enabledboolean––
maxBlocksinteger––
NameTypeReqDescription
availablebooleanyes–
backupMsnumberyes–
busybooleanyes–
checkMsnumberyes–
enabledbooleanyes–
maxBlocksintegeryes–
maxRegionsintegeryes–
operationIdstring|nullyes–
reasonstring|nullyes–
restoreMsnumberyes–
restoredRegionsintegeryes–
snapshotCountintegeryes–
statestringyes–
storedBlocksintegeryes–

No examples provided.

mc_verify_reading ~194

Block reading relies on the testforblock **failure message** revealing the block name, and that message format has no official stability guarantee. When a game update changes the wording, or the game language is not Traditional Chinese, Simplified Chinese or English, parsing breaks, and it breaks **silently**. This probe actively checks whether the reading path still works; **run it once before class** to know whether mc_read_block results can be trusted. It does not need to know what is at the spot: if it is air, it asks about bedrock (a guaranteed mismatch) to force a failure message; if something is there, the first question already produced a message. At most two commands, and it never writes to the world. parseable=false means the protocol has drifted, and mc_read_block results cannot be trusted at all.

NameTypeReqDescription
positionobjectyesAny coordinate works, empty or not
NameTypeReqDescription
branchstringyes–
commandsIssuednumberyes–
parseablebooleanyesfalse means the protocol has drifted and block reading cannot be trusted
parsedNamestring|nullyes–
rawstring|nullyes–

No examples provided.

mc_world_settings ~99

Change one world setting at a time: time sets the time (day/night/noon/midnight or a tick count), weather the weather, gamerule a game rule, difficulty the difficulty.

NameTypeReqDescription
durationSeconds–––
rulestring–Rule name when setting="gamerule"
settingstringyes–
valuestringyestime: day | weather: clear | difficulty: peaceful | the gamerule value
NameTypeReqDescription
commandLinestringyes–
data–yes–
elapsedMsnumberyes–
okbooleanyes–
statusCodenumber|nullyes–
statusMessagestring|nullyes–
undoobject––

No examples provided.

Install

How do I install the BlockHand MCP server?

BlockHand runs locally as an npm package, launched with npx -y @gjlmotea/blockhand-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 · @gjlmotea/blockhand-mcp

# add to Claude Code
claude mcp add gjlmotea-blockhand-for-minecraft-education-mcp -- npx -y @gjlmotea/blockhand-mcp
Common questions

What is the BlockHand MCP server?

BlockHand is an MCP server listed in the public MCP registry as io.github.gjlmotea/blockhand-for-minecraft-education-mcp. Minecraft Education Edition MCP server: Agent robot, 24 build shapes, events. No add-on needed. This page covers its npm package (@gjlmotea/blockhand-mcp).

Is the BlockHand MCP server safe to use?

BlockHand scores 82 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 BlockHand MCP server expose?

BlockHand exposes 44 tools: mc_undo_control, mc_undo, mc_status, mc_await_connection, mc_run_command, and 39 more. Their descriptions and schemas cost roughly 5,083 tokens of context every time the server is loaded.

Is the BlockHand MCP server still maintained?

BlockHand 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 BlockHand MCP server under?

BlockHand declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.