# neme.world (npm · neme-world)

Publish a web game to neme.world: upload a preview, go live, roll back, read its play numbers.

- Trust score: 72/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- npm · `neme-world`: 72/100 (this document), [markdown](https://verifymcp.io/servers/coderneme-neme-world/neme-world.md), [page](https://verifymcp.io/servers/coderneme-neme-world/neme-world)

## Channel facts

- Registry: `npm`
- Package: `neme-world`
- Version: `0.7.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1631 tokens (~203/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the neme.world MCP server?

neme.world runs locally as an npm package, launched with npx -y neme-world mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add coderneme-neme-world -- npx -y neme-world mcp
```

### Cursor

```json
{
  "mcpServers": {
    "coderneme-neme-world": {
      "command": "npx",
      "args": [
        "-y",
        "neme-world",
        "mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "coderneme-neme-world": {
      "command": "npx",
      "args": [
        "-y",
        "neme-world",
        "mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add coderneme-neme-world -- npx -y neme-world mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "coderneme-neme-world": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "neme-world",
        "mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add coderneme-neme-world --command npx --arg -y --arg neme-world --arg mcp
```

### Hermes

```yaml
mcp_servers:
  coderneme-neme-world:
    command: "npx"
    args: ["-y", "neme-world", "mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "coderneme-neme-world": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "neme-world",
        "mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add coderneme-neme-world -t stdio -c npx -a -y neme-world mcp
```

### Other

```json
{
  "mcpServers": {
    "coderneme-neme-world": {
      "command": "npx",
      "args": [
        "-y",
        "neme-world",
        "mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 72, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-20 (score 57, −14)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 0.7.0 → 0.7.1

### 2026-11-19 (score 71, +15)

- [security regression] Stability: 0.07 → unverified
- [security regression] Tool safety: pass → unverified
- [security improvement] Malware scan: unverified → pass
- [functional regression] Schema quality: 1267 → 1579
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.6.1 → 0.7.0

### 2026-11-18 (score 56, −11)

- [security regression] Malware scan: pass → unverified
- [functional regression] Schema quality: pass → fail
- [functional improvement] Tool coverage: 56% → 100%
- [functional] Schema quality: good → excellent
- [functional] Destructive annotations: All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
- [functional] Package version: 0.6.0 → 0.6.1

### 2026-11-17 (score 67, 0)

- [functional regression] Schema quality: 63 → 77
- [functional] Package version: 0.5.2 → 0.6.0

### 2026-11-16 (score 67)

First indexed and scored.

## MCP tools (8)

### `neme_guide` (~86 tokens)

Read the neme.world guide

Fetch the guide to making and publishing a game on neme.world: the neme.json fields, the rules a build must meet, the SDK (scores, leaderboards, sharing, clips). Call it first, before neme_init or neme_publish. Changes nothing and needs no token. Returns the whole guide as Markdown, a few pages long, always the current one.

### `neme_init` (~146 tokens)

Create neme.json

Create neme.json in a project folder, filled in from the folder's name (slug, title, empty description and tags, and dir: "dist" if that folder exists, otherwise "."). Use it once, for a project that has no neme.json; then edit the file and call neme_publish. Writes that one file and nothing else: no network, no token. Never overwrites: if neme.json is already there it fails and changes nothing. Returns one line naming the file it wrote.

Input parameters:

- `dir` (string): The folder to create neme.json in. Absolute, or relative to the folder this server was started in. Default: that folder.

### `neme_publish` (~289 tokens)

Publish a game

Upload the game described by dir/neme.json to neme.world as a new numbered version. With preview true it stays private and players see no change; without it the new version becomes the one players get, so do that only when the developer says so. Earlier versions are kept: neme_promote goes back to one, and makes an approved preview live without uploading again. Uses NEME_TOKEN; with none, the game goes online for a day at a temporary, unlisted address (preview true then fails, uploading nothing) and the result ends with a claim link to give the developer, who keeps the game by opening it and signing up. Returns text: the version number, its download size, the link to play or try it, and once live a README badge line (Markdown) to offer the developer. Fails, changing nothing players see, if neme.json is missing or the build breaks a rule in neme_guide.

Input parameters:

- `dir` (string): The project folder: the one holding neme.json. Absolute, or relative to the folder this server was started in. Default: that folder.
- `preview` (boolean): true: upload as a private preview, leaving what players get unchanged. Needs NEME_TOKEN: with no token there are no private previews, and it fails without uploading anything. false or left out: make…

### `neme_promote` (~195 tokens)

Make a version live

Make a version that is already uploaded the one players get: a preview the developer has approved, or an earlier version to roll back to. It uploads nothing (neme_publish does that) and leaves the title, cover and other details as they are. Players move to that version at once; the version they were on is kept, so calling this again with its number undoes it. Find numbers with neme_versions. Uses the same token as neme_publish. Returns the version now live, the game's link and a README badge line to offer the developer. Fails, changing nothing, if there is no such version.

Input parameters:

- `dir` (string): The project folder: the one holding neme.json. Absolute, or relative to the folder this server was started in. Default: that folder.
- `version` (integer, required): The version's number, as neme_versions lists it (v3 is 3).

### `neme_versions` (~162 tokens)

List a game's versions

List the versions of the game in dir/neme.json, newest first: each one's number, date, file count and size, and which one players are on. Changes nothing. Use it to find the number neme_promote or neme_delete_version needs. A game keeps a limited number of versions: when neme_publish is refused for that, list them here and delete old ones with neme_delete_version. Uses the same token as neme_publish. Returns plain text, one line per version. Fails if neme.json is missing or the game has never been published.

Input parameters:

- `dir` (string): The project folder: the one holding neme.json. Absolute, or relative to the folder this server was started in. Default: that folder.

### `neme_delete_version` (~176 tokens)

Delete a version

Delete one version of a game for good, giving its storage back. It cannot be undone and asks for no confirmation, so call it only when the developer has said which version to delete; neme_versions shows the candidates. The version players are on is refused: to remove it, first make another live with neme_promote. Other versions and the game itself are untouched. Uses the same token as neme_publish. Returns the version deleted and the storage freed. Fails, changing nothing, if there is no such version.

Input parameters:

- `dir` (string): The project folder: the one holding neme.json. Absolute, or relative to the folder this server was started in. Default: that folder.
- `version` (integer, required): The version's number, as neme_versions lists it (v3 is 3).

### `neme_metrics` (~169 tokens)

Read a game's numbers

Read how the game in dir/neme.json did over the last 30 days. Changes nothing. Use it when the developer asks how a game is doing; for which build players are on, use neme_versions. Uses the same token as neme_publish, and only the game's own developer can read them. Returns one JSON object of totals: views, visitors, plays, players, playSeconds, shares, playRate (plays per view, 0 to 1), avgPlaySeconds, medianLoadMs, sharedViews, sharedPlays, platformPlays. Fails if the game has never been published.

Input parameters:

- `dir` (string): The project folder: the one holding neme.json. Absolute, or relative to the folder this server was started in. Default: that folder.

### `neme_playtest` (~286 tokens)

Read a game's playtest report

Read what happened when people played each version of the game in dir/neme.json: the evidence for deciding what to change next. Changes nothing. Use it before changing a game that has been played, and again after the next version has been played, to see whether the change helped; for totals by day use neme_metrics. Uses the same token as neme_publish, and only the game's own developer can read it. Returns one JSON object: live (the version players are on), since (first day read), versions (newest first; each with opened, pressedPlay, loaded, ready, stayed30s, stayed2m, stayed5m, players, medianSeconds, medianLoadMs, broughtBy, checkpoints the game marked with how many reached each and how many stopped after it, counts of notes players wrote, and readings: what the numbers plainly say) and compared (the newest version beside the one before). Every count is a sitting, one visit to the game's page; the developer's own plays are left out. readings and compared are empty when too few people played: then say so rather than drawing conclusions from the counts. Fails if the game has never been published.

Input parameters:

- `dir` (string): The project folder: the one holding neme.json. Absolute, or relative to the folder this server was started in. Default: that folder.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/coderneme-neme-world/neme-world#diagnostics

## Score history

- 2026-11-21: 72
- 2026-11-20: 57
- 2026-11-19: 71
- 2026-11-18: 56
- 2026-11-17: 67
- 2026-11-16: 67

## Common questions

### What is the neme.world MCP server?

neme.world is an MCP server listed in the public MCP registry as io.github.coderneme/neme-world. Publish a web game to neme.world: upload a preview, go live, roll back, read its play numbers. This page covers its npm package (neme-world).

### Is the neme.world MCP server safe to use?

neme.world scores 72 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 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 neme.world MCP server expose?

neme.world exposes 8 tools: neme_guide, neme_init, neme_publish, neme_promote, neme_versions, and 3 more. Their descriptions and schemas cost roughly 1,509 tokens of context every time the server is loaded.

### Is the neme.world MCP server still maintained?

neme.world is still listed as active in the MCP registry. We last reached this channel on 21 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 neme.world MCP server under?

neme.world 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 neme.world MCP server?

VerifyMCP ran 16 checks on neme.world, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. 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.

## Links

- npm package: https://www.npmjs.com/package/neme-world
- Socket report: https://socket.dev/npm/package/neme-world
- Repository: https://github.com/coderneme/neme-cli
- Website: https://neme.world/developers
- Changelog RSS feed: https://verifymcp.io/servers/coderneme-neme-world/neme-world.xml
- Changelog JSON feed: https://verifymcp.io/servers/coderneme-neme-world/neme-world/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/coderneme-neme-world/neme-world.json
- HTML version of this page: https://verifymcp.io/servers/coderneme-neme-world/neme-world
