iDos Games SDK
NPM · @IDOSGAMES/MCP
Game modules, project scaffold and SDK skills for building web games on iDos Games.
Available components
Last scanned (3 hours ago)
Scores higher than 39% 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 Security98
- 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
- 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1086 tokens (~155/item across 7 items; 7 tools + 0 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 Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
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.
- 17 Oct 26 +1
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: unverified → 0.10 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.1.34 → 0.1.36 functional
- 14 Oct 26 69
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 17 Oct 2026 · Analysed npm/@idosgames/mcp@0.1.36
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 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 31 |
| 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_host_scaffold Get project scaffold ~117
Get the base every NEW project starts from — the host shell with sign-in and the lobby (index.html, main.tsx, src/app.config.ts, the wallet files, empty src/modules.ts, config; the lobby and sign-in come from @idosgames/app-shell). Write these to the project root, then add modules with get_module: the systems with inBase (profile, inventory, invite, friends, quests, mailbox), the game(s) with the modules each game 'uses', and any other system the app needs.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_manifest Get runtime package versions ~43
Get the @idosgames runtime packages and their exact versions (core, wallet, module-sdk, react, app-shell). Install these so a seeded host/module resolves its imports.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_module Get module source ~117
Get one module's full source (a map of files) plus install instructions. Write each file under src/modules/{id}/, install its dependencies, and register it in src/modules.ts. Requires a host scaffold in the project (see get_host_scaffold). Its module.ts declares 'sharedUi' (roles it draws for every mode or needs) and its module.meta.json declares 'events' (topics it emits with their payload shapes, and topics it listens to).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Module id, e.g. board-game |
No output schema declared.
No examples provided.
get_skill Get SDK skill ~51
Get one skill's full SKILL.md content and its reference files. Load the relevant skill before writing code against that part of the SDK.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Skill name, e.g. currency-system |
No output schema declared.
No examples provided.
list_modules List game modules ~304
List the composable iDosGames modules in the catalog. Each entry has id, name, type (template = a complete ready-to-run game to start FROM, e.g. voxelcraft; feature = a capability to add on top), engine, genre, a short summary, what it 'provides' (its features), tags, preview media, a live demo url, and its dependency count. Read 'provides' to reuse a ready module instead of building the feature from scratch, then get_module to pull its source. Entries may also carry 'sharedUi' ({provides, requires, drawsOwn}: shared chrome roles currency-bar | wallet | status | account | menu | modes — the project's base (sign-in + the lobby, see get_host_scaffold) provides currency-bar, wallet, account, menu and modes, and a game hides its own copies automatically) and 'inBase' (true: a system installed with the base in every new project — only profile, inventory, invite, friends and quests; its screen is a tab of the lobby; every other system is added only when the app needs it) and 'uses' (a game's modules: install them together with the game) and 'events' ({emits: [{topic, when, payload}], listens: [{topic, why}]}). To react to another module's event, copy its payload descriptor into your own defineTopic(topic, shape(payload)) — never import another module.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_skills List SDK skills ~43
List available skills (name + description). Skills are instructions for working with @idosgames/core services, the module contract, and composition. Use get_skill to load one.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search Search modules and skills ~99
Keyword search across modules and skills. Matches a module on its id, name, type, engine, genre, summary, description, what it 'provides', and tags — so you can find a ready module by the feature you need (e.g. 'dice board', 'idle income', 'voxel building') rather than by name. Skills match on name and description. Returns the matching catalog entries.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Free-text query |
No output schema declared.
No examples provided.
How do I install the iDos Games SDK MCP server?
iDos Games SDK runs locally as an npm package, launched with npx -y @idosgames/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 · @idosgames/mcp
claude mcp add com-idosgames-sdk -- npx -y @idosgames/mcp
What is the iDos Games SDK MCP server?
iDos Games SDK is an MCP server listed in the public MCP registry as com.idosgames/sdk. Game modules, project scaffold and SDK skills for building web games on iDos Games. This page covers its npm package (@idosgames/mcp).
Is the iDos Games SDK MCP server safe to use?
iDos Games SDK scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 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 iDos Games SDK MCP server expose?
iDos Games SDK exposes 7 tools: list_modules, get_module, list_skills, get_skill, get_host_scaffold, and 2 more. Their descriptions and schemas cost roughly 774 tokens of context every time the server is loaded.
Is the iDos Games SDK MCP server still maintained?
iDos Games SDK is still listed as active in the MCP registry. We last reached this channel on 17 October 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 iDos Games SDK MCP server under?
iDos Games SDK declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.