updated 2026-11-05 12:09 UTC

MCP Python SDK

Repository Website by modelcontextprotocol

The official Python SDK for Model Context Protocol servers and clients

Protocols & Tool Integration Python Listed MIT

Is MCP Python SDK safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 7.7 / 10
Provenance Attested
Signed commits 100%
Last push today
Advisories None known
Compare MCP Python SDK

How does it stack up against its Protocols & Tool Integration neighbours?

Pick any agent to compare →
Suggest a correction

In detail: MCP Python SDK scores 94.0/100 (Grade A), ranked #3 of 1374 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 7.7/10; 100% of recent commits are signed; no published advisory affects its latest release (mcp); last pushed 2026-11-05. Every point is earned from checkable signals — never paid placement. How scoring works →

How MCP Python SDK could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships MCP Python SDK and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Signed

    github.com/modelcontextprotocol/python-sdk, MIT, last pushed 2026-11-05. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Strong

    OpenSSF Scorecard rates the repository's practices 7.7/10 (scanned Nov 5, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection2
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions9
    • Pinned Dependencies9
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 2
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 0
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 9
    SAST 10
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions 9
    Vulnerabilities 10

  3. Published packages Linked and attested

    • PyPI mcp Source link points back to this repo Build provenance attested

  4. What you install today No known advisories

    Latest release checked: mcp 2.3.0. No published advisory affects it (OSV, checked 2026-11-04).

Changes to this chain

  • 2026-10-08 Package provenance attestation detected

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues MCP Python SDK’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How MCP Python SDK compares in Protocols & Tool Integration

  1. #1 MCP Python SDK 94.0 this agent
  2. #2 MCP TypeScript SDK 93.3 −0.7
  3. #3 MCP Inspector 91.7 −2.3
  4. #4 Composio 89.5 −4.5
  5. #5 A2A / Agent2Agent Protocol 89.5 −4.5

Bars show each HVTrust score; the tick marks MCP Python SDK’s 94.0.

Where the 94.0 comes from

HVTrust dimensions vs the Protocols & Tool Integration average

94.0 / 100 · 100.0% confidence

MCP Python SDK Protocols & Tool Integration average (63 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
22.1 / 25
11.0 above avg 11.1
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
5.9 above avg 12.1
Transparency50% declared license · 50% OSSF Scorecard
15.0 / 17
2.0 above avg 13.0
Maintenance60% last-push freshness · 40% commit activity
17.2 / 20
2.7 above avg 14.5
AdoptionLog-scaled stars · package downloads
20.0 / 20
8.9 above avg 11.1

Quick Trust Read

What Would Improve It
Improve maintenance to lift the weakest part of the trust profile.
Recent Changes
2026-10-08
Provenance Added
Package provenance attestation detected
2026-10-08
Grade Changed
Trust grade B → A
2026-10-08
Rank Moved
Rank rose 361 spots (#367 → #6)
Maintainer Checklist
Keep signals current Trust posture is already in a healthy range. The main job is to keep provenance, maintenance, and public evidence fresh.
Compare with MCP TypeScript SDK
View Protocols & Tool Integration Report missing data
84.4
Activity sub-score · out of 100
#1
In Protocols & Tool Integration

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A 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 →

Signals refreshed 2026-11-05 12:09 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-11-05

Activity & Reach

Stars
24.8k
Forks
4.1k
Last Push
2026-11-05
today
Commits (4 wk)
19
Downloads (7d)
71,072,297
pypi
HN mentions (30d)
—
Open Issues
285
Rank Change
=
was #3

Analysis

Activity Inputs

84.4 / 100
StarsRepository reach
26.4 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
16.2 / 25
CommunityFork signal
16.8 / 20

Common questions about MCP Python SDK

Public supply-chain signals for MCP Python SDK are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but MCP Python SDK carries less obvious unverified-evidence risk than projects with thin signals.
Does MCP Python SDK publish package provenance?
Yes. MCP Python SDK's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does MCP Python SDK have an OpenSSF Scorecard?
MCP Python SDK has an OpenSSF Scorecard score of 7.7/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 Python SDK actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does MCP Python SDK use?
MCP Python SDK ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are MCP Python SDK's commits signed?
100% of the last 100 commits to MCP Python SDK 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.

Compare MCP Python SDK head-to-head

MCP Python SDK vs MCP TypeScript SDK → MCP Python SDK vs MCP Inspector → MCP Python SDK vs Composio →

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 Python SDK appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
medium confidence
Extensions
Extension based plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
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 Python SDK'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-10-08
Provenance Added
Package provenance attestation detected

Maintain MCP Python SDK?

For maintainers

HVTrust scores MCP Python SDK 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
Rank 17HVTrust 1Grade 1Provenance 1
2026-10-08
Provenance Added
Package provenance attestation detected
2026-10-08
Grade Changed
Trust grade B → A
2026-10-08
Rank Moved
Rank rose 361 spots (#367 → #6)
2026-10-08
HVTrust Changed
HVTrust up 24.7pts (69.0 → 93.7)
2026-10-07
Rank Moved
Rank dropped 12 spots (#355 → #367)
2026-10-02
Rank Moved
Rank rose 26 spots (#369 → #343)
2026-09-23
Rank Moved
Rank dropped 225 spots (#137 → #362)
2026-09-21
Rank Moved
Rank rose 215 spots (#351 → #136)
2026-09-07
Rank Moved
Rank dropped 12 spots (#297 → #309)
2026-09-05
Rank Moved
Rank dropped 59 spots (#236 → #295)
2026-09-03
Rank Moved
Rank dropped 12 spots (#222 → #234)
2026-08-31
Rank Moved
Rank dropped 24 spots (#195 → #219)
2026-08-29
Rank Moved
Rank dropped 10 spots (#188 → #198)
2026-08-27
Rank Moved
Rank dropped 15 spots (#170 → #185)
2026-08-26
Rank Moved
Rank dropped 20 spots (#150 → #170)
2026-08-22
Rank Moved
Rank rose 10 spots (#150 → #140)
2026-08-17
Rank Moved
Rank rose 11 spots (#149 → #138)
2026-08-13
Rank Moved
Rank dropped 10 spots (#136 → #146)
2026-08-12
Rank Moved
Rank rose 10 spots (#146 → #136)
2026-08-08
Rank Moved
Rank dropped 14 spots (#119 → #133)
GitHub → Website → PyPI: mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 94.0 Grade A
Markdown:
[![HVTrust](https://hvtracker.net/badge/mcp-python-sdk.svg)](https://hvtracker.net/agents/mcp-python-sdk)
HTML:
<a href="https://hvtracker.net/agents/mcp-python-sdk"><img src="https://hvtracker.net/badge/mcp-python-sdk.svg" alt="HVTrust"></a>

Other agents in Protocols & Tool Integration

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.4 · Raw JSON