FastAPI-MCP
Expose your FastAPI endpoints as Model Context Protocol (MCP) tools, with Auth!
Is FastAPI-MCP safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare FastAPI-MCP
How does it stack up against its Protocols & Tool Integration neighbours?
Pick any agent to compare →In detail: FastAPI-MCP scores 51.7/100 (Grade C), ranked #894 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.3/10; 34% of recent commits are signed; last pushed 2025-11-24. Every point is earned from checkable signals — never paid placement. How scoring works →
How FastAPI-MCP compares in Protocols & Tool Integration
- #43 golf 53.9 +2.2
- #44 Figma Context MCP 53.6 +1.9
- #45 FastAPI-MCP 51.7 this agent
- #46 MCP Bundles 50.9 −0.8
- #47 Unla 48.7 −3.0
Bars show each HVTrust score; the tick marks FastAPI-MCP’s 51.7.
Where the 51.7 comes from
HVTrust dimensions vs the Protocols & Tool Integration average
51.7 / 100 · 100.0% confidenceFastAPI-MCP Protocols & Tool Integration average (61 agents)
Quick Trust Read
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
Activity & Reach
Analysis
Activity Inputs
38.4 / 100Supply Chain Trust
Common questions about FastAPI-MCP
Does FastAPI-MCP publish package provenance?
Does FastAPI-MCP have an OpenSSF Scorecard?
Is FastAPI-MCP actively maintained?
What license does FastAPI-MCP use?
Are FastAPI-MCP's commits signed?
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
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to FastAPI-MCP'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.
Maintain FastAPI-MCP?
For maintainers
HVTrust scores FastAPI-MCP 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
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/fastapi-mcp)
<a href="https://hvtracker.net/agents/fastapi-mcp"><img src="https://hvtracker.net/badge/fastapi-mcp.svg" alt="HVTrust"></a>
Other agents in Protocols & Tool Integration
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