Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Finance MCP

PYPI · HITL-FINANCE-MCP · SCANNED SEP 14

Market data, SEC filings and risk tools for Webull, Saxo and IBKR. Only you can send an order.

Available components

−15 this week 19 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security41
  • Malware scan not yet available for this package.Unverified
  • CVE check failed: a known high-severity CVE affects cryptography 41.0.7, reached via webull-openapi-python-sdk > cryptography. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 5 of 52 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency35
Schema Quality & AI Usability0
  • Schema quality not yet verified: this package could not be installed in a clean environment, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this package could not be installed in a clean environment, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this package could not be installed in a clean environment, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: this package could not be installed in a clean environment, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: this package could not be installed in a clean environment, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Install

How do I install the Finance MCP server?

Finance MCP runs locally as a PyPI package, launched with uvx hitl-finance-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · hitl-finance-mcp

# add to Claude Code
claude mcp add blahaj-gif-hitl-finance-mcp -- uvx hitl-finance-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "blahaj-gif-hitl-finance-mcp": {
      "command": "uvx",
      "args": [
        "hitl-finance-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "blahaj-gif-hitl-finance-mcp": {
      "command": "uvx",
      "args": [
        "hitl-finance-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add blahaj-gif-hitl-finance-mcp -- uvx hitl-finance-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "blahaj-gif-hitl-finance-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "hitl-finance-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add blahaj-gif-hitl-finance-mcp --command uvx --arg hitl-finance-mcp
# ~/.hermes/config.yaml
mcp_servers:
  blahaj-gif-hitl-finance-mcp:
    command: "uvx"
    args: ["hitl-finance-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "blahaj-gif-hitl-finance-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "hitl-finance-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add blahaj-gif-hitl-finance-mcp -t stdio -c uvx -a hitl-finance-mcp
// mcp.json
{
  "mcpServers": {
    "blahaj-gif-hitl-finance-mcp": {
      "command": "uvx",
      "args": [
        "hitl-finance-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 14 Sept 26 −15
    • Malware scan: pass → unverified security
  • 3 Sept 26 0
    • CVE-2023-50782 affects this package: high security
    • CVE-2024-12797 affects this package: high security
    • CVE-2026-69248 affects this package: high security
    • GHSA-537c-gmf6-5ccf affects this package: high security
    • GHSA-h4gh-qq45-vh27 affects this package: high security
    • CVE-2026-69249 affects this package: high security
    • CVE-2026-34073 affects this package: high security
    • CVE-2024-0727 affects this package: high security
    • CVE-2024-26130 affects this package: high security
    • CVE-2026-0994 affects this package: high security
    • CVE-2026-26007 affects this package: high security
  • 2 Sept 26 0
    • CVE-2023-50782 affects this package: high security
    • CVE-2024-12797 affects this package: high security
    • CVE-2026-69248 affects this package: high security
    • GHSA-537c-gmf6-5ccf affects this package: high security
    • GHSA-h4gh-qq45-vh27 affects this package: high security
    • CVE-2026-69249 affects this package: high security
    • CVE-2026-34073 affects this package: high security
    • CVE-2024-0727 affects this package: high security
    • CVE-2024-26130 affects this package: high security
    • CVE-2026-0994 affects this package: high security
    • CVE-2026-26007 affects this package: high security
  • 1 Sept 26 0
    • CVE-2023-50782 affects this package: high security
    • CVE-2024-12797 affects this package: high security
    • CVE-2026-69248 affects this package: high security
    • GHSA-537c-gmf6-5ccf affects this package: high security
    • GHSA-h4gh-qq45-vh27 affects this package: high security
    • CVE-2026-69249 affects this package: high security
    • CVE-2026-34073 affects this package: high security
    • CVE-2024-0727 affects this package: high security
    • CVE-2024-26130 affects this package: high security
    • CVE-2026-0994 affects this package: high security
    • CVE-2026-26007 affects this package: high security
  • 31 Aug 26 0
    • CVE-2023-50782 affects this package: high security
    • CVE-2024-12797 affects this package: high security
    • CVE-2026-69248 affects this package: high security
    • GHSA-537c-gmf6-5ccf affects this package: high security
    • GHSA-h4gh-qq45-vh27 affects this package: high security
    • CVE-2026-69249 affects this package: high security
    • CVE-2026-34073 affects this package: high security
    • CVE-2024-0727 affects this package: high security
    • CVE-2024-26130 affects this package: high security
    • CVE-2026-0994 affects this package: high security
    • CVE-2026-26007 affects this package: high security
  • 30 Aug 26 0
    • CVE-2023-50782 affects this package: high security
    • CVE-2024-12797 affects this package: high security
    • CVE-2026-69248 affects this package: high security
    • GHSA-537c-gmf6-5ccf affects this package: high security
    • GHSA-h4gh-qq45-vh27 affects this package: high security
    • CVE-2026-69249 affects this package: high security
    • CVE-2026-34073 affects this package: high security
    • CVE-2024-0727 affects this package: high security
    • CVE-2024-26130 affects this package: high security
    • CVE-2026-0994 affects this package: high security
    • CVE-2026-26007 affects this package: high security
  • 29 Aug 26 0
    • CVE-2023-50782 affects this package: high security
    • CVE-2024-12797 affects this package: high security
    • CVE-2026-69248 affects this package: high security
    • GHSA-537c-gmf6-5ccf affects this package: high security
    • GHSA-h4gh-qq45-vh27 affects this package: high security
    • CVE-2026-69249 affects this package: high security
    • CVE-2026-34073 affects this package: high security
    • CVE-2024-0727 affects this package: high security
    • CVE-2024-26130 affects this package: high security
    • CVE-2026-0994 affects this package: high security
    • CVE-2026-26007 affects this package: high security
  • 28 Aug 26 0
    • CVE-2023-50782 affects this package: high security
    • CVE-2024-12797 affects this package: high security
    • CVE-2026-69248 affects this package: high security
    • GHSA-537c-gmf6-5ccf affects this package: high security
    • GHSA-h4gh-qq45-vh27 affects this package: high security
    • CVE-2026-69249 affects this package: high security
    • CVE-2026-34073 affects this package: high security
    • CVE-2024-0727 affects this package: high security
    • CVE-2024-26130 affects this package: high security
    • CVE-2026-0994 affects this package: high security
    • CVE-2026-26007 affects this package: high security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 14 Sept 2026 · Analysed pypi/hitl-finance-mcp@0.3.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi

Background: How many MCP packages publish verified provenance →

Vulnerabilities 19 findings
ID CVE Severity Vector Fix available
GHSA-3ww4-gg4f-jr7f CVE-2023-50782 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N yes
GHSA-537c-gmf6-5ccf high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-6vqw-3v5j-54x4 CVE-2024-26130 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-9v9h-cgj8-h64p CVE-2024-0727 medium CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H yes
GHSA-h4gh-qq45-vh27 medium yes
GHSA-m959-cc7f-wv43 CVE-2026-34073 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-r6ph-v2qm-q3c2 CVE-2026-26007 high yes
PYSEC-2024-225 CVE-2024-26130 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-1283 CVE-2023-50782 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N yes
PYSEC-2026-1285 CVE-2024-0727 medium CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H yes
PYSEC-2026-2141 CVE-2026-26007 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N yes
PYSEC-2026-35 CVE-2026-34073 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N yes
PYSEC-2026-3553 CVE-2026-69249 none yes
PYSEC-2026-3554 CVE-2026-69248 none yes
GHSA-79v4-65xg-pq4g CVE-2024-12797 low yes
GHSA-jwv3-5hgf-82ww CVE-2026-69249 high yes
PYSEC-2026-1284 CVE-2024-12797 none yes
GHSA-7gcm-g887-7qv7 CVE-2026-0994 high yes
PYSEC-2026-1805 CVE-2026-0994 none yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 52 packages
Packages resolved 52
Stale 4
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

Common questions

What is the Finance MCP server?

Finance MCP is listed in the public MCP registry as io.github.Blahaj-gif/hitl-finance-mcp. Market data, SEC filings and risk tools for Webull, Saxo and IBKR. Only you can send an order. This page covers its PyPI package (hitl-finance-mcp).

Is the Finance MCP server safe to use?

Finance MCP scores 19 out of 100 on VerifyMCP. We recorded 19 known advisories against it as of 14 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

Is the Finance MCP server still maintained?

Finance MCP is still listed as active in the MCP registry. We last reached this channel on 14 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.