このプロジェクトは、モデルコンテキストプロトコル（MCP）エコシステムの一部であり、外部APIとの連携や特定のドメインモデルの管理のためのツールを提供します。外部APIとの連携とデータ検証を備えたMCPサーバーの構築方法を示すことを目的としています。
Related MCP server: Mercado Livre MCP Server
get-acoes : 基本的な株価情報を取得します。
Zodを使用した入力検証。
fetch (インフラストラクチャ レイヤー) を使用した Investidor10 API との統合。
このプロジェクトは、ドメイン駆動設計(DDD) パターンにヒントを得た階層化アーキテクチャに従います。
ドメイン( src/domain ): データ構造を表すインターフェースと型を定義します (例: Investidor10 )。
インフラストラクチャ( src/infrastructure ): Investidor10 API への HTTP 呼び出しを担当するInvestidor10ApiServiceなどの外部サービスを実装します。
アプリケーション( src/application ): インフラストラクチャからのデータを処理およびフォーマットするInvestidor10Serviceのビジネス ロジックが含まれます。
インターフェイス( src/interface ): MCP サーバーにツールを登録し、検証スキーマを定義し、結果を返すコントローラー ( Investidor10ToolsController ) が含まれます。
エントリ ポイント( src/main.ts ): McpServerを初期化し、トランスポート ( StdioServerTransport ) を構成し、サービスとコントローラーをインスタンス化し、 stdioでリッスンを開始します。
フォルダ構造は次のとおりです。
src/
├── domain/
│ └── models/ # Domain interfaces
├── infrastructure/
│ └── services/ # External API implementations (Investidor10)
├── application/
│ └── services/ # Business logic and data formatting
├── interface/
│ └── controllers/ # MCP tool registration and validation
└── main.ts # Server entry point
build/ # Compiled JavaScript code
.vscode/ # Contains the mcp.json file, MCP Server configgit clone git@github.com:newerton/mcp-investidor10.git
cd mcp-investidor10
npm install
npm run buildCtrl+Shift+Pを押して「MCP: サーバーの一覧」を選択します。
「stocks」を選択し、「Start Server」を選択します
Ctrl+Shift+Pを押して「MCP: サーバーの一覧」を選択します。
「stocks」を選択し、「Show Output」を選択します
プルリクエストは大歓迎です！お気軽に問題を報告し、改善点について話し合ってください。
このプロジェクトは MIT ライセンスに基づいてライセンスされています - 詳細についてはLICENSEファイルを参照してください。
Buscar informações básicas de ações
| Name | Required | Description | Default |
|---|---|---|---|
| stocks | Yes | Array of stock symbols |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, and the description does not disclose behavioral traits such as data freshness, rate limits, authentication requirements, or what 'basic information' entails. The description lacks sufficient transparency for an agent to understand behavioral implications.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, concise phrase with no wasted words. It is efficient but lacks structured presentation (e.g., bullet points or front-loading of key info).
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the absence of output schema and annotations, the description should provide more context about what the tool returns or how it behaves. 'Basic information' is vague, and the simple one-line description is insufficient for complete understanding.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% coverage for the 'stocks' parameter, providing a description that it is an array of stock symbols. The tool description adds no additional semantics beyond the schema, so it meets the baseline but does not enhance understanding.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Buscar' and the resource 'informações básicas de ações', indicating it retrieves basic stock information. However, it does not differentiate from sibling tools that also retrieve stock-related data, such as get-acoes-datas-pagamento or get-indicadores.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, limitations, or when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
get-acoesScored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool has a distinct purpose focused on retrieving basic stock information.
A single tool inherently has consistent naming, as there are no other tools to compare against. The tool name 'get-acoes' follows a clear verb-noun pattern.
One tool is too few for a server named 'Investidor10 MCP Server', which suggests a broader financial or investment domain. This minimal set severely limits functionality and likely indicates significant gaps in coverage.
The server is severely incomplete for an investment domain. With only a tool to get basic stock information, it lacks essential operations like portfolio management, market analysis, transaction execution, or even updates/deletes for financial data.
brapi.dev MCP — Brazilian stock + crypto + ETF quotes.
Open-source MCP server for Zerodha Kite Connect. Portfolio, market data, backtesting, alerts.
Brazilian stock (B3) fundamentals: ratios, dividends, scores, REITs (FIIs), ETFs. Open methodology.
Financial data MCP server for Claude, ChatGPT, Cursor and Codex. Real-time stock quotes, financial statements, options flow, SEC filings, insider trades, 13F holdings, macro data and market news from gloom.sh, the open-source Bloomberg Terminal alternative.
