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.

Joinable

NPM · GETJOINABLE

Make any game joinable: pick the pattern, get the snippet, run a two-player self-test.

Available components

+3 this week 74 Trust /100

Last scanned (22 hours ago)

Scores higher than 49% of npm servers

Category Developer Tools

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
  • 0 of 1 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency35
  • 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
  • License check failed: the license (UNLICENSED) isn't a recognized OSI-approved license. See how to fix → Fail
  • Actively maintained (last published 12 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 679 tokens (~135/item across 5 items; 5 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 Management54
  • Stability check failed: the tool surface changed between 0.2.0 and 0.2.4: 0 tool removals, 1 breaking changes, 1 additions. See how to fix → Fail
Tool Coverage94
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 83% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 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
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.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 48 to 51.

  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 41 to 44.

  • 16 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 34 to 38.

  • 13 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 24 to 28.

  • 11 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 18 to 21.

  • 9 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
  • 8 Nov 26 0
    • Malware scan: unverified → pass ▲ security
    • Package version: 0.2.2 → 0.2.4 functional
    • Package version: 0.2.2 → 0.2.3 functional
  • 7 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
    • Stability: 0.17 → fail ▼ security
    • Schema quality: 511 → 679 ▼ functional
    • Security disclosure: fail → unverified ▼ functional
    • Security disclosure: fail → pass ▲ functional
    • Package version: 0.2.1 → 0.2.2 functional
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/getjoinable@0.2.4

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 1 package
Packages resolved 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~599 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
joinable_choose_pattern ~157

Picks how to make this web game multiplayer with Joinable, from its genre: full rounds ("race" or "score"), lockstep (RTS and strategy), Pattern A (shared world), B (avatars), C (turns), or not supported yet (fighting, shooters).

NameTypeReqDescription
genrestringyese.g. racing, arcade, puzzle, board, card, clicker, builder, platformer, top-down, party, turn-based, rts, fighting, shooter
has_score_or_timeboolean–Each round ends with a score or a time
held_key_avatarsboolean–Players move a character with held keys or a joystick
turn_basedboolean––

No output schema declared.

No examples provided.

joinable_desyncs ~131

When a lockstep game's players went out of sync, Joinable keeps a report: the first tick where the devices' simulations differed, each device's fingerprint, the browsers and builds, and the orders around that tick. Fetch the latest reports for a game by its public key (or, for keyless local play, its page origin), then fix what isn't deterministic in the simulation.

NameTypeReqDescription
keystring–The game's public key, pk_…
originstring–For keyless play on a local site: the page origin, e.g. http://localhost:5173

No output schema declared.

No examples provided.

joinable_kit ~84

Make a web game multiplayer with Joinable: returns the agent kit (how to pick a pattern for the game's genre, what to change, the API that exists today, how to test). Read it before changing a game. Joinable provides hosted rooms, invites, quick match, waiting room, countdown, results and rematch: never write server or WebSocket code.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

joinable_selftest ~126

Opens two headless players on the game's local page and checks the full-rounds contract (same seed on both, players see each other, one result, rematch). Every failure says what to fix. Run until it passes. Needs playwright-core's Chromium.

NameTypeReqDescription
channelstring–Use the installed Chrome (with the GPU), for heavy 3D games
roundinteger–Seconds to wait for a round to finish (default 60)
urlstringyesThe game page, served locally, e.g. http://localhost:5173/

No output schema declared.

No examples provided.

joinable_snippet ~101

Returns the exact script tag and setup code for a Joinable pattern, with the relay and the project key filled in.

NameTypeReqDescription
keystring–The project's public key, pk_…, for a real site. Leave it out while the game runs on localhost: no key is needed there.
patternstringyes–
statestring–Name of the game's state object, for patterns A, B and C (default "game")

No output schema declared.

No examples provided.

Install

How do I install the Joinable MCP server?

Joinable runs locally as an npm package, launched with npx -y getjoinable 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 · getjoinable

# add to Claude Code
claude mcp add com-getjoinable-joinable -- npx -y getjoinable mcp
Common questions

What is the Joinable MCP server?

Joinable is an MCP server listed in the public MCP registry as com.getjoinable/joinable. Make any game joinable: pick the pattern, get the snippet, run a two-player self-test. This page covers its npm package (getjoinable).

Is the Joinable MCP server safe to use?

Joinable scores 74 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 Joinable MCP server expose?

Joinable exposes 5 tools: joinable_kit, joinable_choose_pattern, joinable_snippet, joinable_selftest, joinable_desyncs. Their descriptions and schemas cost roughly 599 tokens of context every time the server is loaded.

Is the Joinable MCP server still maintained?

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

Joinable declares the UNLICENSED licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.

What did VerifyMCP test on the Joinable MCP server?

VerifyMCP ran 16 checks on Joinable, 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.