mcp-server-yahoo-finance MCP server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is mcp-server-yahoo-finance?

The mcp-server-yahoo-finance is a server implementation designed to provide a simple note storage system specifically for managing notes related to Yahoo Finance.

how to use mcp-server-yahoo-finance?

To start using the mcp-server-yahoo-finance, you need to install it and set up the necessary configurations to connect with your note management system. Follow the installation steps for your operating system and configure the server as needed.

key features of mcp-server-yahoo-finance?

  • Custom note:// URI scheme for accessing individual notes.
  • Summarization prompt for creating summaries of all stored notes, with varying detail levels.
  • Tool for adding new notes with essential metadata like name and content.

use cases of mcp-server-yahoo-finance?

  1. Storing and managing financial notes effectively for individual or team use.
  2. Summarizing long-form notes to quickly glean insights from financial information.
  3. Adding and categorizing notes for enhanced organization related to market trends and financial data.

FAQ from mcp-server-yahoo-finance?

  • What types of notes can be stored?

The server can store various notes related to financial data, including summaries, analyses, and research notes.

  • Is there a limit to the number of notes I can store?

No specific limits are mentioned, but usability may vary based on the server's performance and storage capacity.

  • How do I summarize my stored notes?

Use the 'summarize-notes' prompt, and specify your preferred detail level for the summary.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
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)

a day ago