# Shelem Scorekeeping (pypi · shelem-scorekeeping-mcp)

Scores Shelem (شلم) card game hands: bids, Mak, Shelem, the 1000-point rule and the 1165 win.

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

## Components

- pypi · `shelem-scorekeeping-mcp`: 70/100 (this document), [markdown](https://verifymcp.io/servers/khaleghika-shelem-scorekeeping/shelem-scorekeeping-mcp.md), [page](https://verifymcp.io/servers/khaleghika-shelem-scorekeeping/shelem-scorekeeping-mcp)

## Channel facts

- Registry: `pypi`
- Package: `shelem-scorekeeping-mcp`
- Version: `0.1.0`
- 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-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 1 of 28 dependencies flagged as unhealthy.
- **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 5 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 57/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 604 tokens (~604/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Shelem Scorekeeping MCP server?

Shelem Scorekeeping runs locally as a PyPI package, launched with uvx shelem-scorekeeping-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 khaleghika-shelem-scorekeeping -- uvx shelem-scorekeeping-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "khaleghika-shelem-scorekeeping": {
      "command": "uvx",
      "args": [
        "shelem-scorekeeping-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "khaleghika-shelem-scorekeeping": {
      "command": "uvx",
      "args": [
        "shelem-scorekeeping-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add khaleghika-shelem-scorekeeping -- uvx shelem-scorekeeping-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "khaleghika-shelem-scorekeeping": {
      "type": "local",
      "command": [
        "uvx",
        "shelem-scorekeeping-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add khaleghika-shelem-scorekeeping --command uvx --arg shelem-scorekeeping-mcp
```

### Hermes

```yaml
mcp_servers:
  khaleghika-shelem-scorekeeping:
    command: "uvx"
    args: ["shelem-scorekeeping-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "khaleghika-shelem-scorekeeping": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "shelem-scorekeeping-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add khaleghika-shelem-scorekeeping -t stdio -c uvx -a shelem-scorekeeping-mcp
```

### Other

```json
{
  "mcpServers": {
    "khaleghika-shelem-scorekeeping": {
      "command": "uvx",
      "args": [
        "shelem-scorekeeping-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-04 (score 70, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-03 (score 54, −15)

- [security regression] Malware scan: pass → unverified

### 2026-11-02 (score 69, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-01 (score 53, +1)

- [functional improvement] Stability: unverified → 0.07

### 2026-10-30 (score 52)

First indexed and scored.

## MCP tools (1)

### `calculate_shelem_score` (~425 tokens)

Calculate Shelem score

Score one completed Shelem hand and return both teams' new totals.

Pass the cumulative scores from before the hand, the declaring team, the bid, and how many points were captured (defending_points, declarer_points, or outcome "mak"/"sweep"). The engine applies the doubled sweep award, failed and heavily failed bids, Shelem/sar-shelem (+330/-330/-660), the 1000-point rule for a defending team, and the 1165 winning threshold. All arithmetic is integer and deterministic.

Invalid or contradictory input returns an error and no score.

Input parameters:

- `bid` (integer, required): The winning bid: 100, 105, ..., 165. Expand spoken abbreviations first ("20" is 120).
- `bid_successful`: Optional cross-check. The captured points decide success; if this flag disagrees the hand is rejected. Mak is successful.
- `bidding_team`: Team that won the bidding: 1 or 2. Must equal hakem_team when both are given. At least one of the two is required.
- `contract`: Omit below 165. Required when bid is 165: "shelem", "sare-shelem" or "normal" (scored differently on failure).
- `declarer_points`: Points captured by the declaring team: 0-165, multiple of 5. Must sum to 165 with defending_points when both are given.
- `defending_points`: Points captured by the defending team: 0-165, multiple of 5.
- `hakem_team`: Team of the Hakem (the declarer): 1 or 2.
- `outcome`: "mak": the declarer captured exactly the bid. "sweep": the defenders captured nothing. Use instead of, or consistently with, the point fields.
- `team1_score` (integer, required): Team 1 cumulative score before this hand. May be negative.
- `team2_score` (integer, required): Team 2 cumulative score before this hand. May be negative.

Output parameters:

- `explanation` (string): Plain-English account of how the hand was scored.
- `game_finished` (boolean): True when exactly one team reached 1165 or more.
- `hand`
- `score_changes`
- `updated_team1_score` (integer): Team 1 total after the hand.
- `updated_team2_score` (integer): Team 2 total after the hand.
- `winner`: 1 or 2 when the game is finished, otherwise null.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/khaleghika-shelem-scorekeeping/shelem-scorekeeping-mcp#diagnostics

## Score history

- 2026-11-05: 70
- 2026-11-04: 70
- 2026-11-03: 54
- 2026-11-02: 69
- 2026-11-01: 53
- 2026-10-31: 52
- 2026-10-30: 52

## Common questions

### What is the Shelem Scorekeeping MCP server?

Shelem Scorekeeping is an MCP server listed in the public MCP registry as io.github.khaleghika/shelem-scorekeeping. Scores Shelem (شلم) card game hands: bids, Mak, Shelem, the 1000-point rule and the 1165 win. This page covers its PyPI package (shelem-scorekeeping-mcp).

### Is the Shelem Scorekeeping MCP server safe to use?

Shelem Scorekeeping scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. 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 Shelem Scorekeeping MCP server expose?

Shelem Scorekeeping exposes 1 tool: calculate_shelem_score. Their descriptions and schemas cost roughly 425 tokens of context every time the server is loaded.

### Is the Shelem Scorekeeping MCP server still maintained?

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

Shelem Scorekeeping declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- PyPI project: https://pypi.org/project/shelem-scorekeeping-mcp/
- Socket report: https://socket.dev/pypi/package/shelem-scorekeeping-mcp
- Repository: https://github.com/khaleghika/shelem-mcp
- Changelog RSS feed: https://verifymcp.io/servers/khaleghika-shelem-scorekeeping/shelem-scorekeeping-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/khaleghika-shelem-scorekeeping/shelem-scorekeeping-mcp.json
- HTML version of this page: https://verifymcp.io/servers/khaleghika-shelem-scorekeeping/shelem-scorekeeping-mcp