Miniant Games
NPM · MINIANTGAMES-MCP
Build games for Miniant Games: developer guide, checklists, build validator, starter game.
Available components
Last scanned (10 hours ago)
Scores higher than 34% of npm servers
Category Developer Tools
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 & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 5 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 489 tokens (~81/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 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.
- 31 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- Stability: unverified → 0.03 ▲ functional
- Package version: 0.1.0 → 0.1.1 functional
- 29 Oct 26 62
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 5 Nov 2026 · Analysed npm/miniantgames-mcp@0.1.1
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 →
get_checklist ~85
Get the requirement checklist (id, text, verify, page) for one guide page (slug) or for a whole task recipe (recipe id from list_guide, pages in recipe order). Pass exactly one of slug or recipe. verify is either manual or validator:<rule>, the rule validate_build checks.
| Name | Type | Req | Description |
|---|---|---|---|
| recipe | string | – | – |
| slug | string | – | – |
No output schema declared.
No examples provided.
list_guide ~50
List every page of the Miniant Games developer guide (slug, title, section, one-line agentSummary) and the task recipes. Call this first, then read_guide for the pages you need.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
read_guide ~68
Read one developer guide page as markdown, with its checklist. Use slug "agent-entry" for the agent entry document (platform rules, things never to build, and the recipes). Slugs come from list_guide; the intro page is "introduction".
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
No output schema declared.
No examples provided.
scaffold_game ~148
Create a plain-JavaScript starter game (miniant.json, index.html, main.js with the Miniant SDK init, ready and reportResult skeleton) in a new or empty directory, resolved against the server's working directory. Refuses a non-empty directory. For Phaser, Unity, Godot or other engines read_guide sdk/engines instead. This is the only tool that writes files. modes are mode ids (solo, vs_ai, local_multiplayer, online_friends, online_random), default [solo]; non-solo modes need extra work that validate_build will list.
| Name | Type | Req | Description |
|---|---|---|---|
| dir | string | yes | – |
| modes | array | – | – |
| title | string | yes | – |
No output schema declared.
No examples provided.
search_guide ~64
Case-insensitive substring search over guide titles, headings, summaries and bodies. Returns up to 10 pages (slug, title, matching snippet), title and heading matches first. Use it to find which page documents an SDK call or rule.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
No output schema declared.
No examples provided.
validate_build ~74
Validate a game's build output folder (the one containing miniant.json and the entry HTML) with the same validator the Miniant publishing pipeline runs. dir is resolved against the server's current working directory. Returns { ok, errors, warnings, checks, highlightsManual }; fix every error before publishing.
| Name | Type | Req | Description |
|---|---|---|---|
| dir | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Miniant Games MCP server?
Miniant Games runs locally as an npm package, launched with npx -y miniantgames-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 · miniantgames-mcp
claude mcp add games-miniant-miniantgames-mcp -- npx -y miniantgames-mcp
What is the Miniant Games MCP server?
Miniant Games is an MCP server listed in the public MCP registry as games.miniant/miniantgames-mcp. Build games for Miniant Games: developer guide, checklists, build validator, starter game. This page covers its npm package (miniantgames-mcp).
Is the Miniant Games MCP server safe to use?
Miniant Games scores 66 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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 Miniant Games MCP server expose?
Miniant Games exposes 6 tools: list_guide, read_guide, search_guide, get_checklist, validate_build, scaffold_game. Their descriptions and schemas cost roughly 489 tokens of context every time the server is loaded.
Is the Miniant Games MCP server still maintained?
Miniant Games 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 Miniant Games MCP server under?
Miniant Games declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Miniant Games MCP server?
VerifyMCP ran 15 checks on Miniant Games, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Miniant Games: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.