Random Tables
NPM · @PIPEWORX/MCP-RANDOM-TABLES · 2 COMPONENTS
random-tables — Pipeworx original composable random tables for tabletop and narrative play…
Available components
Last scanned (10 hours ago)
Scores higher than 76% of npm servers
Category Entertainment and Games
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 & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-random-tables). View diagnostics → Pass
- 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 Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 817 tokens (~204/item across 4 items; 4 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 Management23
- Stability observed for 7 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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.
- 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.
- 4 Nov 26 +3
- 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
- Security disclosure: unverified → fail ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: unverified → 0.20 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.0 → 0.2.1 functional
- 3 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 79
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/@pipeworx/mcp-random-tables@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-random-tables |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-random-tables/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3691874451 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:a9a306725a73bde5a126b0188f49ffdba5199c89b31f8468c0f15fcbae627d1b64cf441e525c28d53e9a1e03e482897f8dda25f1d00bd10f94eb0e7f5 |
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_random_table ~102
Pipeworx original random tables: fetch one built-in table in full — its title, genre, description, and every raw entry (text + weight) — without rolling. Entry text may contain unresolved {{table:<id>}} references; roll_table resolves those at roll time.
| Name | Type | Req | Description |
|---|---|---|---|
| table | string | yes | Built-in table id, e.g. "loot", "npc_full", "encounters_fantasy". Call list_random_tables to see every id. |
No output schema declared.
No examples provided.
list_random_tables ~107
Pipeworx original random tables: list every built-in table id, title, genre and entry count, optionally filtered to one genre ("fantasy", "scifi" or "modern"). Genre-agnostic tables (loot, weather, npc_*, complication, plot_hook, rumour, settlement_quirk, npc_full) are included under every genre filter, since they apply regardless of setting.
| Name | Type | Req | Description |
|---|---|---|---|
| genre | string | – | Optional genre filter. Omit to list every table. |
No output schema declared.
No examples provided.
roll_custom_table ~209
Pipeworx original random tables: roll one or more entries from a table YOU supply — bring your own weighted list of { text, weight? } and get back a reproducible weighted draw. Entries may contain {{table:<id>}} references to Pipeworx's BUILT-IN random tables (e.g. "{{table:npc_personality}}"), resolved recursively (up to 6 levels deep). Optional seed makes the roll reproducible; the seed used is always returned. No session support for custom tables — use roll_table for session-tracked built-in tables.
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | How many entries to roll, 1-20 (default 1). |
| entries | array | yes | Your table: a non-empty array of { text: string, weight?: number > 0 (default 1) }. Up to 500 entries. |
| seed | string | – | Optional seed for a reproducible roll. Omit for fresh randomness; the seed actually used is always returned. |
No output schema declared.
No examples provided.
roll_table ~344
Pipeworx original random tables: roll one or more entries from a built-in table — encounters_fantasy, encounters_scifi, encounters_modern, loot, weather, complication, npc_personality, npc_secret, npc_occupation, plot_hook, tavern, rumour, settlement_quirk, npc_full. Entries may contain {{table:<id>}} references to OTHER built-in tables, resolved recursively (up to 6 levels deep) — the response gives both the raw entry text and the fully resolved text. Optional seed makes the roll reproducible (same seed + arguments = same result; the seed used is always returned). Optional session_id draws without replacement across repeated calls (hosted only, via the gateway's shared KV) — pass none to get an ordinary independent weighted roll every time, or pass any string to start tracking a no-repeat session (the response returns the real session_id to reuse). No text from any commercial RPG product — every table and entry is written for Pipeworx.
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | How many entries to roll, 1-20 (default 1). |
| seed | string | – | Optional seed for a reproducible roll. Omit for fresh randomness; the seed actually used is always returned. |
| session_id | string | – | Optional. Omit for an ordinary independent weighted roll. Pass a session_id (your own first time, or one returned by a previous call) to draw without replacement across calls — hosted only. |
| table | string | yes | Built-in table id, e.g. "loot", "npc_full", "encounters_fantasy". Call list_random_tables to see every id. |
No output schema declared.
No examples provided.
How do I install the Random Tables MCP server?
Random Tables runs locally as an npm package, launched with npx -y @pipeworx/mcp-random-tables. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-random-tables
claude mcp add pipeworx-io-random-tables -- npx -y @pipeworx/mcp-random-tables
What is the Random Tables MCP server?
Random Tables is an MCP server listed in the public MCP registry as io.github.pipeworx-io/random-tables. random-tables, Pipeworx original composable random tables for tabletop and narrative play… This page covers its npm package (@pipeworx/mcp-random-tables).
Is the Random Tables MCP server safe to use?
Random Tables scores 83 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. Its build provenance is signed and verified. 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 Random Tables MCP server expose?
Random Tables exposes 4 tools: roll_table, roll_custom_table, list_random_tables, get_random_table. Their descriptions and schemas cost roughly 762 tokens of context every time the server is loaded.
Is the Random Tables MCP server still maintained?
Random Tables 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 Random Tables MCP server under?
Random Tables declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.