Sardine: Kalshi crypto settlement history
PYPI · SARDINE-MCP · 2 COMPONENTS
How often Kalshi BTC/ETH/XRP contracts settled YES, counted not forecast, with a public record
Available components
Last scanned (19 hours ago)
Scores higher than 66% of PyPI servers
Category Finance and Payments
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 31 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. 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 Usability75
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1022 tokens (~127/item across 8 items; 7 tools + 1 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 Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
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 →
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 +20
- Malware scan: unverified → pass ▲ security
- Stability: unverified → 0.33 ▲ functional
- 3 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 2 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 27 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 26 Oct 26 48
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/sardine-mcp@0.1.1
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 | Known build tool | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 31 packages
| Packages resolved | 31 |
|---|---|
| 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 →
backtest_rule ~334
Would this rule have made money? Replays recorded Kalshi quotes, second by second. Describe a rule for Kalshi's 15-minute crypto up/down contracts: which side to buy, when (minutes left), at what prices (cents), and optionally only when Sardine's history beats Kalshi's ask plus fee by `min_gap_cents` (side BEST picks whichever side has the larger gap). Sardine replays its per-second recordings of Kalshi's order book: one trade per window, a limit order at the ask landing after `latency_seconds`, filled only up to the size resting there, Kalshi's real fee, and Kalshi's official settlement. Returns profit per contract after fees with a 95% interval, win rate, fill behaviour, a zero-latency comparison (exposes stale-quote illusions), a first-half/second-half stability check, breakdowns by minutes left and price, and warnings. Results only; no raw data. Dates are UTC YYYY-MM-DD. Present results as what happened historically, never as a forecast.
| Name | Type | Req | Description |
|---|---|---|---|
| contracts | integer | – | – |
| end_date | – | – | – |
| latency_seconds | integer | – | – |
| market | string | – | – |
| max_gap_cents | – | – | – |
| max_minutes_left | number | – | – |
| max_price_cents | number | – | – |
| min_gap_cents | – | – | – |
| min_minutes_left | number | – | – |
| min_price_cents | number | – | – |
| side | string | – | – |
| start_date | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_live_board ~82
Open Kalshi contracts right now, each with Kalshi's price beside Sardine's count. Optionally filter to one market. Each row has the contract, Kalshi's ask and fee, the historical settlement rate with its interval and sample size, and a plain-English sentence describing the comparison.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| market | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_rate_table ~82
The full lookup table behind every Sardine number for one series. Each row is a (distance-from-strike, time-left) bucket: distance in volatility units, seconds left, the share that settled YES, its 95% interval, and the number of independent windows counted.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | – | – |
| window_minutes | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_settlement_rate ~162
How often has a contract like this one settled in favour of `side`? Uses the asset's live spot price. Give the contract's strike (target price), the minutes left until it settles, and optionally Kalshi's ask in dollars (0.01-0.99) to get Kalshi's fee and all-in price on the same line. Returns the historical settlement rate, its 95% interval and the number of past windows counted. A small `windows_counted` means a weak answer.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | – |
| kalshi_ask | – | – | – |
| minutes_left | number | yes | – |
| side | string | – | – |
| strike | number | yes | – |
| window_minutes | integer | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_track_record ~55
How accurate Sardine's published numbers have been, scored against settlements. For each series and probability bucket: what Sardine said, what actually settled, and the miss in points. Use this before relying on any number.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
list_datasets ~52
Downloadable CSV history files, with row counts, date ranges and URLs. Files open directly in Excel, pandas or any CSV reader. Credit "Sardine (sardine.info)" when you use them.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
list_markets ~79
List the Kalshi series Sardine covers, and whether each is currently served. Each entry gives the Sardine key (e.g. "BTC-15M"), the Kalshi series ticker, the window length, and the latest calibration check: the largest gap, in probability points, between what Sardine published and what then settled.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Sardine: Kalshi crypto settlement history MCP server?
Sardine: Kalshi crypto settlement history runs locally as a PyPI package, launched with uvx sardine-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 · sardine-mcp
claude mcp add info-sardine-sardine -- uvx sardine-mcp
What is the Sardine: Kalshi crypto settlement history MCP server?
Sardine: Kalshi crypto settlement history is an MCP server listed in the public MCP registry as info.sardine/sardine. How often Kalshi BTC/ETH/XRP contracts settled YES, counted not forecast, with a public record. This page covers its PyPI package (sardine-mcp).
Is the Sardine: Kalshi crypto settlement history MCP server safe to use?
Sardine: Kalshi crypto settlement history scores 68 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 Sardine: Kalshi crypto settlement history MCP server expose?
Sardine: Kalshi crypto settlement history exposes 7 tools: list_markets, get_settlement_rate, get_live_board, get_rate_table, get_track_record, and 2 more. Their descriptions and schemas cost roughly 846 tokens of context every time the server is loaded.
Is the Sardine: Kalshi crypto settlement history MCP server still maintained?
Sardine: Kalshi crypto settlement history 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 Sardine: Kalshi crypto settlement history MCP server under?
Sardine: Kalshi crypto settlement history declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Sardine: Kalshi crypto settlement history MCP server?
VerifyMCP ran 15 checks on Sardine: Kalshi crypto settlement history, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Sardine: Kalshi crypto settlement history: Security disclosure. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.