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.

neme.world

NPM · NEME-WORLD

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

Available components

72 Trust /100

Last scanned (16 hours ago)

Scores higher than 44% 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 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 & Transparency45
Schema Quality & AI Usability71
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability observed for 5 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
  • All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 9 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

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 →

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.

  • 21 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 20 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
    • Package version: 0.7.0 → 0.7.1 functional
  • 19 Nov 26 +15
    • Stability: 0.07 → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Malware scan: unverified → pass ▲ security
    • Schema quality: 1267 → 1579 ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
    • Package version: 0.6.1 → 0.7.0 functional
  • 18 Nov 26 −11
    • Malware scan: pass → unverified ▼ security
    • Schema quality: pass → fail ▼ functional
    • 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 functional
  • 17 Nov 26 0
    • Schema quality: 63 → 77 ▼ functional
    • Package version: 0.5.2 → 0.6.0 functional
  • 16 Nov 26 67

    First indexed and scored.

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 21 Nov 2026 · Analysed npm/neme-world@0.7.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 →

MCP tools · 8 exposed · ~1,509 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
neme_delete_version ~176

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.

NameTypeReqDescription
dirstring–The project folder: the one holding neme.json. Absolute, or relative to the folder this server was started in. Default: that folder.
versionintegeryesThe version's number, as neme_versions lists it (v3 is 3).

No output schema declared.

No examples provided.

neme_guide ~86

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

neme_init ~146

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.

NameTypeReqDescription
dirstring–The folder to create neme.json in. Absolute, or relative to the folder this server was started in. Default: that folder.

No output schema declared.

No examples provided.

neme_metrics ~169

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.

NameTypeReqDescription
dirstring–The project folder: the one holding neme.json. Absolute, or relative to the folder this server was started in. Default: that folder.

No output schema declared.

No examples provided.

neme_playtest ~286

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.

NameTypeReqDescription
dirstring–The project folder: the one holding neme.json. Absolute, or relative to the folder this server was started in. Default: that folder.

No output schema declared.

No examples provided.

neme_promote ~195

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.

NameTypeReqDescription
dirstring–The project folder: the one holding neme.json. Absolute, or relative to the folder this server was started in. Default: that folder.
versionintegeryesThe version's number, as neme_versions lists it (v3 is 3).

No output schema declared.

No examples provided.

neme_publish ~289

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.

NameTypeReqDescription
dirstring–The project folder: the one holding neme.json. Absolute, or relative to the folder this server was started in. Default: that folder.
previewboolean–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…

No output schema declared.

No examples provided.

neme_versions ~162

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.

NameTypeReqDescription
dirstring–The project folder: the one holding neme.json. Absolute, or relative to the folder this server was started in. Default: that folder.

No output schema declared.

No examples provided.

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.

npm · neme-world

# add to Claude Code
claude mcp add coderneme-neme-world -- npx -y neme-world mcp
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.