Is MCP Server Kalshi safe to use?

MCP Server Kalshi has an HVTrust score of 63.1/100 (Grade C), ranked #533 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for MCP Server Kalshi?

MCP Server Kalshi scores 63.1/100 on HVTracker's evidence-weighted HVTrust scale. It has 28 GitHub stars and is categorized under MCP Servers.

MCP Server Kalshi

9crusher/mcp-server-kalshi

A MCP server to interact with Kalshi prediction markets

MCP Servers Python Listed MIT

Is MCP Server Kalshi safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 3.8 / 10

Provenance Attested

Signed commits 21%

Last push 7d ago

Compare MCP Server Kalshi

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: MCP Server Kalshi scores 63.1/100 (Grade C), ranked #533 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 3.8/10; 21% of recent commits are signed; last pushed 2026-09-19. Every point is earned from checkable signals — never paid placement. How scoring works →

How MCP Server Kalshi compares in MCP Servers

Bars show each HVTrust score; the tick marks MCP Server Kalshi’s 63.1.

Where the 63.1 comes from

HVTrust dimensions vs the MCP Servers average

63.1 / 100 · 100.0% confidence

MCP Server Kalshi MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

13.3 / 25

3.0 above avg 10.3

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.6 above avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

11.7 / 17

0.5 below avg 12.2

Maintenance60% last-push freshness · 40% commit activity

12.9 / 20

0.8 above avg 12.1

AdoptionLog-scaled stars · package downloads

6.2 / 20

1.0 below avg 7.2

Quick Trust Read

What Would Improve It

Increase the share of verified signed commits for clearer maintainer identity.

Recent Changes

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → C

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 3.8/10. Tighten the weakest checks to improve public safety evidence.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Compare with another agent Get email alerts for MCP Server Kalshi View MCP Servers Report missing data

46.9

Activity sub-score · out of 100

#302

In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

Forks

Last Push

2026-09-19

7 days ago

Commits (4 wk)

Downloads (7d)

108

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▼1

was #532

Analysis

Activity Inputs

46.9 / 100

StarsRepository reach

8.8 / 30

FreshnessLast push recency

24.0 / 25

ActivityRecent commits

8.7 / 25

CommunityFork signal

5.2 / 20

Supply Chain Trust

Package Provenance

Verified

pypi attestation

OSSF Scorecard

3.8 / 10

OpenSSF Scorecard · scanned Sep 26, 2026

Signed Commits

21%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 8

CII-Best-Practices 0

Code-Review 1

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Common questions about MCP Server Kalshi

MCP Server Kalshi has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does MCP Server Kalshi publish package provenance?

Yes. MCP Server Kalshi's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does MCP Server Kalshi have an OpenSSF Scorecard?

MCP Server Kalshi has an OpenSSF Scorecard score of 3.8/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is MCP Server Kalshi actively maintained?

Actively maintained. The repository was pushed to within the last 7 day(s).

What license does MCP Server Kalshi use?

MCP Server Kalshi ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are MCP Server Kalshi's commits signed?

20% of the last 100 commits to MCP Server Kalshi are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support

high confidence

Implemented

MCP Server Kalshi appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

low confidence

None detected

No clear third-party provider dependency detected.

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

None detected

No clear plugin system or broad tool surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

low confidence

Unknown

Package source metadata is missing or inconclusive

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

How this surface has changed

Detected changes to MCP Server Kalshi's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

Maintain MCP Server Kalshi?

For maintainers

HVTrust scores MCP Server Kalshi from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → C

2026-09-23

Rank Moved

Rank rose 454 spots (#981 → #527)

2026-09-23

HVTrust Changed

HVTrust up 37.9pts (25.3 → 63.2)

2026-09-22

Newly Listed

First tracked at rank #981

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-19

Rank Moved

Rank rose 16 spots (#514 → #498)

2026-09-19

Activity Score Changed

Activity score up 7pts (44 → 51)

2026-09-14

Rank Moved

Rank rose 15 spots (#513 → #498)

2026-09-11

Rank Moved

Rank dropped 12 spots (#489 → #501)

2026-09-08

Rank Moved

Rank dropped 12 spots (#471 → #483)

2026-09-07

Rank Moved

Rank dropped 31 spots (#440 → #471)

2026-09-05

Rank Moved

Rank dropped 69 spots (#365 → #434)

2026-09-04

Rank Moved

Rank dropped 16 spots (#349 → #365)

2026-09-03

Rank Moved

Rank dropped 17 spots (#332 → #349)

2026-09-02

Grade Changed

Trust grade B → C

2026-09-02

Rank Moved

Rank dropped 45 spots (#287 → #332)

2026-08-31

Grade Changed

Trust grade C → B

2026-08-29

Scorecard Added

OSSF Scorecard: 4.1/10

2026-08-29

Rank Moved

Rank rose 191 spots (#469 → #278)

2026-08-29

HVTrust Changed

HVTrust up 8.6pts (56.0 → 64.6)

2026-08-27

Rank Moved

Rank dropped 19 spots (#445 → #464)

2026-08-26

Rank Moved

Rank dropped 46 spots (#399 → #445)

2026-08-24

Rank Moved

Rank dropped 15 spots (#385 → #400)

2026-08-23

Rank Moved

Rank rose 32 spots (#417 → #385)

2026-08-23

Activity Score Changed

Activity score up 8pts (41 → 49)

2026-08-22

Rank Moved

Rank rose 16 spots (#433 → #417)

2026-08-19

Rank Moved

Rank dropped 12 spots (#417 → #429)

2026-08-17

Rank Moved

Rank rose 12 spots (#426 → #414)

2026-08-16

Rank Moved

Rank dropped 10 spots (#416 → #426)

2026-08-13

Rank Moved

Rank dropped 14 spots (#400 → #414)

2026-08-12

Rank Moved

Rank rose 11 spots (#411 → #400)

2026-08-10

Rank Moved

Rank dropped 19 spots (#393 → #412)

2026-08-08

Newly Listed

First tracked at rank #391

GitHub → PyPI: mcp-server-kalshi

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/mcp-server-kalshi.svg)](https://hvtracker.net/agents/mcp-server-kalshi)
            
HTML:
            <a href="https://hvtracker.net/agents/mcp-server-kalshi"><img src="https://hvtracker.net/badge/mcp-server-kalshi.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON