Skip to main content
Glama
enesjakozh
qubaomingg

@qubaomingg/stock-mcp

by qubaomingg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Servidor MCP Alpha Vantage Stock

Este es un servidor de Protocolo de Contexto de Modelo (MCP) que proporciona datos bursátiles desde la API de Alpha Vantage. Permite a Claude y a otros clientes de MCP acceder a datos bursátiles históricos y en tiempo real.

Características

  • Obtenga datos bursátiles intradiarios con intervalos personalizables

  • Obtenga datos bursátiles diarios

  • Generar alertas de stock basadas en movimientos de precios

  • Acceda a los datos bursátiles como recursos

Related MCP server: Stock Market MCP Server

Prerrequisitos

  • Node.js 16 o superior

  • Una clave API de Alpha Vantage (obtenga una gratis en Alpha Vantage )

Instalación

  1. Clonar este repositorio

  2. Instalar dependencias:

    npm install

  3. Cree un archivo .env en el directorio raíz y agregue su clave API de Alpha Vantage:

    ALPHA_VANTAGE_API_KEY=your_api_key_here

Construyendo y funcionando

Construya el código TypeScript:

npm run build

Ejecutar el servidor:

npm start

Para desarrollo con recarga automática:

npm run dev

Pruebe el cliente API:

npm test

Uso con Claude para escritorio

Para utilizar este servidor MCP con Claude for Desktop:

  1. Abrir Claude para escritorio

  2. Vaya a Configuración > Desarrollador > Editar configuración

  3. Agregue lo siguiente a su claude_desktop_config.json :

{
  "mcpServers": {
    "alpha-vantage": {
      "command": "node",
      "args": ["/absolute/path/to/dist/index.js"],
      "env": {
        "ALPHA_VANTAGE_API_KEY": "YOUR_API_KEY"
      } 
    }
  }
}

Reemplace /absolute/path/to/dist/index.js con la ruta absoluta al archivo index.js creado.

  1. Reiniciar Claude para escritorio

Herramientas disponibles

obtener datos de stock

Obtiene datos bursátiles intradiarios para un símbolo específico.

Parámetros:

  • symbol (obligatorio): Símbolo bursátil (p. ej., IBM, AAPL)

  • interval (opcional): Intervalo de tiempo entre puntos de datos (1 min, 5 min, 15 min, 30 min, 60 min). Valor predeterminado: 5 min.

  • outputsize (opcional): Cantidad de datos a devolver (compacto: últimos 100 puntos de datos, completo: hasta 20 años de datos). Predeterminado: compacto

obtener datos bursátiles diarios

Obtiene datos diarios de acciones para un símbolo específico.

Parámetros:

  • symbol (obligatorio): Símbolo bursátil (p. ej., IBM, AAPL)

  • outputsize (opcional): Cantidad de datos a devolver (compacto: últimos 100 puntos de datos, completo: hasta 20 años de datos). Predeterminado: compacto

obtener alertas de stock

Analiza datos bursátiles para generar alertas basadas en movimientos de precios.

Parámetros:

  • symbol (obligatorio): Símbolo bursátil (p. ej., IBM, AAPL)

  • threshold (opcional): Umbral porcentual para alertas de movimiento de precios. Valor predeterminado: 5

Recursos disponibles

datos bursátiles

Acceda a los datos de stock directamente como recurso.

Plantilla de URI: stock://{symbol}/{interval}

Parámetros:

  • symbol : Símbolo bursátil (por ejemplo, IBM, AAPL)

  • interval : Intervalo de tiempo (diario, 1 min, 5 min, 15 min, 30 min, 60 min). Predeterminado: diario

Ejemplo de uso en Claude:

  • ¿Puedes analizar estos datos bursátiles: stock://AAPL/daily?

  • ¿Qué opinas de estos datos: stock://MSFT/5min?

Licencia

ISC

Available Tools

3 tools
get-daily-stock-dataD
ParametersJSON Schema
NameRequiredDescriptionDefault
symbolYesStock symbol (e.g., IBM, AAPL)
outputsizeNoAmount of data to return (compact: latest 100 data points, full: up to 20 years of data)

TDQS

D1/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get-stock-alertsD
ParametersJSON Schema
NameRequiredDescriptionDefault
symbolYesStock symbol (e.g., IBM, AAPL)
thresholdNoPercentage threshold for price movement alerts (default: 5)

TDQS

D1/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get-stock-dataD
ParametersJSON Schema
NameRequiredDescriptionDefault
symbolYesStock symbol (e.g., IBM, AAPL)
intervalNoTime interval between data points (default: 5min)
outputsizeNoAmount of data to return (compact: latest 100 data points, full: up to 20 years of data)

TDQS

D1/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 3 tool updatesv1.0.0
    • Changedget-daily-stock-data2 fields changed
      • addedInput schema / $schema
        Added value: +"http://json-schema.org/draft-07/schema#"
      • addedInput schema / additionalProperties
        Added value: +false
    • Changedget-stock-alerts2 fields changed
      • addedInput schema / $schema
        Added value: +"http://json-schema.org/draft-07/schema#"
      • addedInput schema / additionalProperties
        Added value: +false
    • Changedget-stock-data2 fields changed
      • addedInput schema / $schema
        Added value: +"http://json-schema.org/draft-07/schema#"
      • addedInput schema / additionalProperties
        Added value: +false
  2. 3 tool updates
    • First observedget-daily-stock-data
    • First observedget-stock-alerts
    • First observedget-stock-data
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

D1.4/5.0

Scored across 3 tools

Disambiguation1/5

The tools are highly ambiguous and overlapping. 'get-daily-stock-data' and 'get-stock-data' appear to serve nearly identical purposes, with no description to clarify their differences. 'get-stock-alerts' might be distinct but lacks context, making the overall set confusing and prone to misselection.

Naming Consistency5/5

The naming is perfectly consistent, using a kebab-case pattern with a 'get-' prefix followed by a noun phrase. All three tools follow this exact convention, making them predictable and easy to parse.

Tool Count2/5

With only 3 tools, the set feels thin and under-scoped for a stock data server. It lacks essential operations like search, update, or delete, and the limited coverage suggests it may not support comprehensive agent workflows in this domain.

Completeness1/5

The tool surface is severely incomplete for a stock data domain. It only provides 'get' operations with no ability to set, modify, or manage data (e.g., no create, update, delete, or search tools). This will cause significant agent failures in handling stock-related tasks.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches