updated 2026-09-26 06:32 UTC

FinStack MCP

finstacklabs/finstack-mcp

India-first MCP server for NSE/BSE, fundamentals, analytics, and daily research workflows.

MCP Servers Python Listed MIT

Is FinStack MCP safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 3.1 / 10
Provenance None
Signed commits 0%
Last push 170d ago
Compare FinStack MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: FinStack MCP scores 36.8/100 (Grade D), ranked #1215 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.1/10; recent commits are unsigned; last pushed 2026-04-09. Every point is earned from checkable signals — never paid placement. How scoring works →

How FinStack MCP compares in MCP Servers

  1. #723 Airflow MCP Server 37.2 +0.4
  2. #724 JustCall MCP Server 36.9 +0.1
  3. #725 FinStack MCP 36.8 this agent
  4. #726 Driflyte MCP Server 36.8 ±0
  5. #727 MCP Funnel 36.7 −0.1

Bars show each HVTrust score; the tick marks FinStack MCP’s 36.8.

Where the 36.8 comes from

HVTrust dimensions vs the MCP Servers average

36.8 / 100 · 100.0% confidence

FinStack MCP MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
3.9 / 25
6.4 below avg 10.3
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.6 below avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
11.1 / 17
1.1 below avg 12.2
Maintenance60% last-push freshness · 40% commit activity
0.7 / 20
11.4 below avg 12.1
AdoptionLog-scaled stars · package downloads
5.3 / 20
1.9 below avg 7.2

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank rose 69 spots (#1278 → #1209)
2026-09-23
HVTrust Changed
HVTrust up 22.9pts (14.1 → 37.0)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.1/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.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Refresh maintenance signals The repo was last pushed 170 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent Get email alerts for FinStack MCP View MCP Servers Report missing data
14.4
Activity sub-score · out of 100
#725
In MCP Servers

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 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-09-26 06:32 UTC · Repo last pushed 170 days ago

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars
16
Forks
15
Last Push
2026-04-09
170 days ago
Commits (4 wk)
0
Downloads (7d)
54
pypi
HN mentions (30d)
—
Open Issues
1
Rank Change
▲1
was #1216

Analysis

Activity Inputs

14.4 / 100
StarsRepository reach
7.4 / 30
FreshnessLast push recency
1.4 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
5.6 / 20

Supply Chain Trust

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

Common questions about FinStack MCP

Public trust evidence for FinStack MCP 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 FinStack MCP publish package provenance?
No published build provenance is currently detected for FinStack MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does FinStack MCP have an OpenSSF Scorecard?
FinStack MCP has an OpenSSF Scorecard score of 3.1/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 FinStack MCP actively maintained?
Slowing down. Last push was 170 days ago — keep an eye on whether activity resumes.
What license does FinStack MCP use?
FinStack MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are FinStack MCP's commits signed?
0% of the last 100 commits to FinStack MCP 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
medium confidence
Implemented
FinStack MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
low confidence
None detected
No clear third-party provider dependency detected.
Credential signal: API keys or service config markers documented.
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 FinStack 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.

2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain FinStack MCP?

For maintainers

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

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 21Listed 2HVTrust 2Scorecard 1Delisted 1MCP 1
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank rose 69 spots (#1278 → #1209)
2026-09-23
HVTrust Changed
HVTrust up 22.9pts (14.1 → 37.0)
2026-09-22
Newly Listed
First tracked at rank #1278
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-09
Rank Moved
Rank dropped 20 spots (#1169 → #1189)
2026-09-08
Rank Moved
Rank dropped 13 spots (#1156 → #1169)
2026-09-07
Rank Moved
Rank dropped 21 spots (#1135 → #1156)
2026-09-06
Rank Moved
Rank dropped 15 spots (#1120 → #1135)
2026-09-05
Rank Moved
Rank dropped 37 spots (#1083 → #1120)
2026-09-04
Rank Moved
Rank dropped 27 spots (#1056 → #1083)
2026-09-03
Rank Moved
Rank dropped 55 spots (#1001 → #1056)
2026-09-02
Rank Moved
Rank dropped 44 spots (#957 → #1001)
2026-09-01
Rank Moved
Rank dropped 38 spots (#919 → #957)
2026-08-31
Rank Moved
Rank dropped 29 spots (#890 → #919)
2026-08-30
Rank Moved
Rank dropped 41 spots (#849 → #890)
2026-08-29
Scorecard Added
OSSF Scorecard: 3.1/10
2026-08-29
Rank Moved
Rank rose 206 spots (#1055 → #849)
2026-08-29
HVTrust Changed
HVTrust up 15.5pts (23.3 → 38.8)
2026-08-28
Rank Moved
Rank dropped 32 spots (#1023 → #1055)
2026-08-27
Rank Moved
Rank dropped 21 spots (#1002 → #1023)
2026-08-26
Rank Moved
Rank dropped 93 spots (#909 → #1002)
2026-08-24
Rank Moved
Rank dropped 10 spots (#896 → #906)
2026-08-16
Rank Moved
Rank dropped 21 spots (#877 → #898)
2026-08-13
Rank Moved
Rank dropped 13 spots (#864 → #877)
2026-08-12
Rank Moved
Rank rose 14 spots (#878 → #864)
2026-08-10
Rank Moved
Rank dropped 51 spots (#820 → #871)
2026-08-08
Newly Listed
First tracked at rank #815
GitHub → PyPI: finstack-mcp

Embed Badge Badge guide for maintainers →

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

Other agents in MCP Servers

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