Github

Created By
dre1144a year ago
Overview

What is MCP Finance Agent?

MCP Finance Agent is a Model Context Protocol agent designed for analyzing financial portfolios and generating recommendations.

How to use MCP Finance Agent?

To use the MCP Finance Agent, follow the installation steps to set up the environment, and then run the agent to access the API for portfolio analysis.

Key features of MCP Finance Agent?

  • Integration with Tinkoff Invest API
  • Portfolio and risk analysis
  • Generation of recommendations for portfolio optimization
  • Monitoring of market data
  • Calculation of performance metrics

Use cases of MCP Finance Agent?

  1. Analyzing investment portfolios for risk assessment.
  2. Providing recommendations for optimizing asset allocation.
  3. Monitoring real-time market data for informed decision-making.

FAQ from MCP Finance Agent?

  • What programming language is required to run MCP Finance Agent?

Python 3.11 or higher is required.

  • How do I install the MCP Finance Agent?

Follow the installation instructions provided in the documentation, including setting up Poetry and cloning the repository.

  • Can I run tests on the MCP Finance Agent?

Yes! You can run tests using pytest as described in the documentation.

Server Config

{
  "mcpServers": {
    "github": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "SUPABASE_URL",
        "-e",
        "SUPABASE_SERVICE_KEY",
        "-e",
        "ENCRYPTION_KEY",
        "-e",
        "MCP_API_KEY",
        "-e",
        "MCP_API_URL",
        "-e",
        "GITHUB_PERSONAL_ACCESS_TOKEN",
        "mcp/finance-portfolio-agent"
      ],
      "env": {
        "GITHUB_PERSONAL_ACCESS_TOKEN": "<YOUR_TOKEN>"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
dre1144
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

20 hours ago
Gpt Scrambler

2 days ago