Kaggle (Seif-Sameh) MCP Server

mcp-server-kaggle PyPI v0.1.1

Published by seif-sameh — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

A Model Context Protocol (MCP) server for the Kaggle API

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 39

Each tool and what it can reach — statically extracted from the published source.

  • competition_download_fileingests untrusted input
  • competition_download_filesingests untrusted input
  • competition_leaderboard_downloadingests untrusted input
  • competition_list_filesreads sensitive data
  • dataset_download_fileingests untrusted input
  • dataset_download_filesingests untrusted input
  • dataset_list_filesreads sensitive data
  • dataset_metadataingests untrusted input
  • kernel_list_filesreads sensitive data
  • kernel_outputingests untrusted input
Show 29 more tools ↓
  • kernel_pullingests untrusted input
  • model_instance_version_downloadingests untrusted input
  • competition_leaderboard_viewno sensitive capability
  • competition_submissionsno sensitive capability
  • competition_submitno sensitive capability
  • competitions_listno sensitive capability
  • dataset_createno sensitive capability
  • dataset_create_versionno sensitive capability
  • dataset_initializeno sensitive capability
  • dataset_statusno sensitive capability
  • datasets_listno sensitive capability
  • kernel_initializeno sensitive capability
  • kernel_pushno sensitive capability
  • kernel_statusno sensitive capability
  • kernels_listno sensitive capability
  • model_createno sensitive capability
  • model_deleteno sensitive capability
  • model_getno sensitive capability
  • model_initializeno sensitive capability
  • model_instance_createno sensitive capability
  • model_instance_deleteno sensitive capability
  • model_instance_getno sensitive capability
  • model_instance_initializeno sensitive capability
  • model_instance_updateno sensitive capability
  • model_instance_version_createno sensitive capability
  • model_instance_version_deleteno sensitive capability
  • model_instance_version_filesno sensitive capability
  • model_updateno sensitive capability
  • models_listno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.1.1 latest A 96/100 0 1.13.0 2026-08-25

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/mcp-server-kaggle/badge.svg)](https://mcptrustchecker.com/registry/mcp-server-kaggle)
HTML
<a href="https://mcptrustchecker.com/registry/mcp-server-kaggle"><img src="https://mcptrustchecker.com/registry/mcp-server-kaggle/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/mcp-server-kaggle/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan mcp-server-kaggle --online --registry pypi

Use the free API → How scoring works

Other implementations of Kaggle 2

Independent packages implementing the same tool, scanned with the same engine. Compare all 3 side by side →

More in AI & Agents