MaverickMCP
Stock market MCP server for Yahoo Finance data, technical analysis, portfolio tracking, and Python backtesting. Runs locally with no API key for core tools.
Is MaverickMCP safe? Promising trust profile, but some evidence still deserves review.
Compare MaverickMCP
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: MaverickMCP scores 61.1/100 (Grade C), ranked #668 of 1374 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 6.0/10; 99% of recent commits are signed; last pushed 2026-11-09. Every point is earned from checkable signals — never paid placement. How scoring works →
How MaverickMCP 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.
- Raise the OSSF Scorecard from 6.0 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Fuzzing 0 +6.3 → 67.4 B · #260 of 778
Chain of custody
Scanners check what the code says. This traces who ships MaverickMCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.
-
Source Signed
github.com/wshobson/maverick-mcp, MIT, last pushed 2026-11-09. 99% of the last 100 commits carry a verified signature, so changes trace to a verified account.
-
Review and release Mixed
OpenSSF Scorecard rates the repository's practices 6.0/10 (scanned Oct 23, 2026, refresh pending). The checks that decide who can get a change released:
- Code Review4
- Branch Protection0
- Signed Releasesn/a
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies5
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 0CI-Tests 8CII-Best-Practices 0Code-Review 4Contributors 6Dangerous-Workflow 10Dependency-Update-Tool 10Fuzzing 0License 10Maintained 10Packaging -1Pinned-Dependencies 5SAST 0Security-Policy 10Signed-Releases -1Token-Permissions 0Vulnerabilities 9 -
Published packages None
No registry package. MaverickMCP is used from its repository, so what you run is whatever you check out: pin a release tag or commit.
Changes to this chain
- 2026-08-31 OSSF Scorecard: 5.7/10
Evidence behind this score
Coverage C: 2 of 5 independent evidence types found.
- GitHub repository data
- Package downloads (missing)
- Supply-chain checks
- Public actions (missing)
- Community mentions (missing)
Verify this score yourself
Every build re-issues MaverickMCP’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.
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 MaverickMCP compares in MCP Servers
- #363 MCP Document Reader 61.3 +0.2
- #364 Laravel MCP Companion 61.1 ±0
- #365 MaverickMCP 61.1 this agent
- #366 MCP ZAP Server 60.9 −0.2
- #367 Webhook MCP Server 60.9 −0.2
Bars show each HVTrust score; the tick marks MaverickMCP’s 61.1.
Where the 61.1 comes from
HVTrust dimensions vs the MCP Servers average
61.1 / 100 · 100.0% confidenceMaverickMCP MCP Servers average (778 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 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 →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
69.1 / 100Common questions about MaverickMCP
Does MaverickMCP publish package provenance?
Does MaverickMCP have an OpenSSF Scorecard?
Is MaverickMCP actively maintained?
What license does MaverickMCP use?
Are MaverickMCP'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 →
- database
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to MaverickMCP'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 MaverickMCP?
For maintainers
HVTrust scores MaverickMCP 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/maverickmcp)
<a href="https://hvtracker.net/agents/maverickmcp"><img src="https://hvtracker.net/badge/maverickmcp.svg" alt="HVTrust"></a>
Other agents in MCP Servers
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON