Shelem Scorekeeping
PYPI · SHELEM-SCOREKEEPING-MCP
Scores Shelem (شلم) card game hands: bids, Mak, Shelem, the 1000-point rule and the 1165 win.
Available components
Last scanned (7 hours ago)
Scores higher than 66% of PyPI 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
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 28 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability57
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (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.
- 4 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 3 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 2 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 1 Nov 26 +1
- Stability: unverified → 0.07 ▲ functional
- 30 Oct 26 52
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 pypi/shelem-scorekeeping-mcp@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 28 packages
| Packages resolved | 28 |
|---|---|
| No linked repository | 1 |
| 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 →
calculate_shelem_score Calculate Shelem score ~425
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.
| Name | Type | Req | Description |
|---|---|---|---|
| bid | integer | yes | 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 | yes | Team 1 cumulative score before this hand. May be negative. |
| team2_score | integer | yes | Team 2 cumulative score before this hand. May be negative. |
| Name | Type | Req | Description |
|---|---|---|---|
| explanation | string | yes | Plain-English account of how the hand was scored. |
| game_finished | boolean | yes | True when exactly one team reached 1165 or more. |
| hand | – | yes | – |
| score_changes | – | yes | – |
| updated_team1_score | integer | yes | Team 1 total after the hand. |
| updated_team2_score | integer | yes | Team 2 total after the hand. |
| winner | – | yes | 1 or 2 when the game is finished, otherwise null. |
No examples provided.
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.
pypi · shelem-scorekeeping-mcp
claude mcp add khaleghika-shelem-scorekeeping -- uvx shelem-scorekeeping-mcp
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.