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.

Giveaway & Raffle Winner Picker (provably fair)

NPM · PROVABLY-FAIR-MCP · SCANNED AUG 18

Pick giveaway and raffle winners nobody can rig — verifiable by anyone, no API key.

Available components

−2 this week 69 Trust /100
Trust breakdown (6 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 →

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
  • 30 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
  • Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
  • 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 9 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability79
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 299 tokens (~99/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
  • Stability observed for 10 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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · provably-fair-mcp

# add to Claude Code
claude mcp add app-promptcoin-giveaway-raffle-winner-picker -- npx -y provably-fair-mcp
# add to Codex CLI
codex mcp add app-promptcoin-giveaway-raffle-winner-picker -- npx -y provably-fair-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-promptcoin-giveaway-raffle-winner-picker": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "provably-fair-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add app-promptcoin-giveaway-raffle-winner-picker --command npx --arg -y --arg provably-fair-mcp
# ~/.hermes/config.yaml
mcp_servers:
  app-promptcoin-giveaway-raffle-winner-picker:
    command: "npx"
    args: ["-y", "provably-fair-mcp"]
// mcp.json
{
  "mcpServers": {
    "app-promptcoin-giveaway-raffle-winner-picker": {
      "command": "npx",
      "args": [
        "-y",
        "provably-fair-mcp"
      ]
    }
  }
}
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.

  • 17 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Aug 26 −5
    • Source repository: pass → fail security
    • Security disclosure: fail → unverified functional
  • 11 Aug 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 10 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Aug 26 0
    • Source repository: pass → fail security
    • Stability: unverified → 0.03 functional
    • Package version: 1.0.3 → 1.0.4 functional
  • 8 Aug 26 69

    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 18 Aug 2026 · Analysed npm/provably-fair-mcp@1.0.4

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm
Dependencies 96 packages
Packages resolved 96
Stale 30
Tree resolution Complete
MCP tools · 3 exposed · ~299 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.

Tool Tokens
create_scheduled_draw ~141

Create a provably-fair draw that reveals its winner at a FUTURE time. The randomness round is committed the instant you create it — before it exists — so no one (not even the operator) can predict or rig the outcome. Returns a public, shareable proof page. Ideal when entries are still open or you want a verifiable, scheduled reveal.

NameTypeReqDescription
delay_secintegerSeconds until the draw (min 120, default 600).
entrantsarrayyesList of entrants.
titlestringyesName of the draw/giveaway.
winnersintegerNumber of winners (default 1).

No output schema declared.

No examples provided.

pick_winner_now ~115

Instantly pick a provably-fair random winner (or winners) from a list of entrants. The randomness comes from the public drand beacon, so the result is verifiable and cannot be rigged. Use for giveaways, raffles, fair selection, tie-breaks, or any 'pick one at random, provably' need.

NameTypeReqDescription
entrantsarrayyesList of entrants (names, @handles, wallet addresses, anything).
winnersintegerHow many winners to pick (default 1).

No output schema declared.

No examples provided.

verify_draw ~43

Fetch the current state and verifiable result of a provably-fair draw by its id (from create_scheduled_draw).

NameTypeReqDescription
idstringyesThe draw id.

No output schema declared.

No examples provided.