FastMCP

🚀 The fast, Pythonic way to build MCP servers and clients.

Protocols & Tool Integration Python Grade D Listed Apache-2.0
49.4/100
Rank #447 of 1204
Compare FastMCP

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

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-08-08 · 1d ago
Recent change
Rank +1

Is FastMCP safe? FastMCP scores 49.4/100 (Grade D), ranked #447 of 1204 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.6/10; 100% of recent commits are signed; last pushed 2026-08-08. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Protocols & Tool Integration

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-08-08
Rank Moved
Rank dropped 111 spots (#333 → #444)
2026-08-07
Provider Added
Runtime surface grew — new detected provider dependency: Google Gemini
2026-07-15
Rank Moved
Rank dropped 22 spots (#286 → #308)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.6/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
92.1
Activity sub-score · out of 100
#28

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

Signals refreshed 2026-08-09 19:01 UTC · Repo last pushed yesterday

Activity & Reach

Stars
27.1k
Forks
2.2k
Last Push
2026-08-08
yesterday
Commits (4 wk)
255
Downloads (7d)
HN mentions (30d)
Open Issues
241
Rank Change
▼3
was #444

Analysis

HVTrust Dimensions vs Protocols & Tool Integration

49.4 / 100 · 67.0% confidence

FastMCP Protocols & Tool Integration average (44 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
12.0 / 25
1.8 above avg 10.2
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.0 below avg 11.8
Transparency50% declared license · 50% OSSF Scorecard
13.3 / 17
1.0 above avg 12.3
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
5.2 above avg 14.7
AdoptionLog-scaled stars · package downloads
10.6 / 20
in line with avg 10.6

Activity Inputs

92.1 / 100
StarsRepository reach
26.6 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
15.6 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
5.6 / 10
OpenSSF Scorecard · scanned Aug 9, 2026
Signed Commits
100%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 4
CI-Tests 9
CII-Best-Practices 0
Code-Review 6
Contributors 10
Dangerous-Workflow 0
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 10
Packaging -1
Pinned-Dependencies 0
SAST 7
Security-Policy 10
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 8

Is FastMCP safe?

Public trust evidence for FastMCP is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does FastMCP publish package provenance?
No published build provenance is currently detected for FastMCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does FastMCP have an OpenSSF Scorecard?
FastMCP has an OpenSSF Scorecard score of 5.6/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 FastMCP actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does FastMCP use?
FastMCP ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are FastMCP's commits signed?
100% of the last 100 commits to FastMCP 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
FastMCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
3 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
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
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 FastMCP'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-08-07
Provider Added
Runtime surface grew — new detected provider dependency: Google Gemini

Maintain FastMCP?

For maintainers

HVTrust scores FastMCP 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.

Reputation Timeline

Signal history
Rank 3Listed 1Surface 1
2026-08-08
Rank Moved
Rank dropped 111 spots (#333 → #444)
2026-08-07
Provider Added
Runtime surface grew — new detected provider dependency: Google Gemini
2026-07-15
Rank Moved
Rank dropped 22 spots (#286 → #308)
2026-07-14
Rank Moved
Rank dropped 13 spots (#273 → #286)
2026-07-13
Newly Listed
First tracked at rank #273

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 49.4 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/fastmcp.svg)](https://hvtracker.net/agents/fastmcp)
HTML:
<a href="https://hvtracker.net/agents/fastmcp"><img src="https://hvtracker.net/badge/fastmcp.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.2 · Raw JSON