This server enables querying stock market data via the Investidor10 API. You can:
Fetch basic stock information using the get-acoes tool by providing an array of stock symbols
Query multiple stocks simultaneously by passing an array of symbols
Validate inputs through Zod and JSON schema validation
Integrate with Investidor10 API to retrieve stock market data
Use with MCP tools for configuration and management within VSCode
Provides input validation for MCP tools, ensuring data integrity when interacting with the Investidor10 API for stock market data.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Investidor10 MCP Server get current stock price for PETR4"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
This project is part of the Model Context Protocol (MCP) ecosystem and provides tools to interact with external APIs and manage specific domain models. It is designed to demonstrate how to build an MCP server with external API integration and data validation.
Related MCP server: Mercado Livre MCP Server
get-acoes: Fetch basic stock information.
Input validation using Zod.
Integration with the Investidor10 API using fetch (infrastructure layer).
The project follows a layered architecture inspired by Domain-Driven Design (DDD) patterns:
Domain (src/domain):
Defines interfaces and types that represent data structures (e.g., Investidor10).
Infrastructure (src/infrastructure):
Implements external services, such as Investidor10ApiService, responsible for making HTTP calls to the Investidor10 API.
Application (src/application):
Contains business logic in Investidor10Service, which processes and formats data from the infrastructure.
Interface (src/interface):
Includes controllers (Investidor10ToolsController) that register tools in the MCP server, define validation schemas, and return results.
Entry Point (src/main.ts):
Initializes the McpServer, configures the transport (StdioServerTransport), instantiates services and controllers, and starts listening on stdio.
The folder structure is as follows:
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 buildPress Ctrl+Shift+P and select "MCP: List Servers"
Select "stocks" and then "Start Server"
Press Ctrl+Shift+P and select "MCP: List Servers"
Select "stocks" and then "Show Output"
Pull requests are welcome! Feel free to open issues and discuss improvements.
This project is licensed under the MIT license - see the LICENSE file for details.
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.
Multi-tenant FastMCP server for Charles Schwab brokerage data, monetized via DPYC Tollbooth
The Mercado Pago MCP Server implements the Model Context Protocol to provide AI agents and LLMs with access to Mercado Pago's APIs and tools within compatible development environments. It acts as an intermediary that translates Mercado Pago resources into executable functions (tools) that AI applications can invoke to perform actions and automate flows. The server simplifies integration, enables using documentation to implement or improve code, and optimizes operations through natural language interactions without manual implementations.
