Skip to content

Alpha Vantage

Updated View as Markdown

Search ticker symbols, read one standard Global Quote or inspect market session status using your Alpha Vantage API key. Prices preserve provider decimal strings and metadata; no realtime/delayed entitlement is requested. This subset does not trade, bulk-download history, run technical indicators, stream updates or make investment recommendations.

What you can do (3)

What you can do

Available commands: 3 (3 read, 0 write). Enable only the commands your application needs.

Command Effect
Search Alpha Vantage ticker symbols — alphavantage.symbols.search Read
Read an Alpha Vantage quote — alphavantage.quotes.get Read
Read global market session status — alphavantage.markets.status Read

Connect and use

Connect and use

Open the integration's connection form to check the available credential source. The source has not been resolved for this documentation export. The instructions below apply when using your own provider account.

Get your provider credentials

Follow these steps for Alpha Vantage, then enter the issued values in the connection form below.

  1. Open Alpha Vantage Support → Claim your Free API Key. Complete the provider’s role, organization and email form and copy the issued key, or use a key from your paid account. Enter it in Alpha Vantage API key here. Select symbols.search, quotes.get or markets.status, save and create an Tooluse.net API key scoped to those reads for your client. Use symbols.search to discover a ticker before quotes.get. Standard quote freshness and daily/rate allowances follow your provider key; this adapter does not request a realtime or delayed entitlement, upgrade your plan or retry quota failures. Replace a lost/revoked key through Alpha Vantage and update this connection. No managed OAuth, automatic renewal or background polling is provided.

Official credential setup

Where to enter credentials

In the integration page, sign in, choose your workspace and open Connect. If a Credentials choice is shown, select Use my credentials. Fill the following connection fields and save. Provider credentials belong in this form, never in an MCP configuration or tool input.

Connection field Requirement
Alpha Vantage API key Required

Open API keys and create a Tooluse.net key for the enabled commands.

Set TOOLUSE_API_KEY in your client and use the shared MCP configuration.

Configure Claude Code, Codex or Cursor once

Permissions and results

If you have more than one workspace, check the selected workspace in the connection or API-key dialog before saving. Roles, enabled commands, expiry and revocation use Tooluse.net's existing permissions. Disabling a connection or revoking a key immediately prevents new calls.

Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.

Your connection's daily allowance and key permissions also apply. Adding a connection does not make a provider request.

Calls return the shared execution receipt and a Claude tool_result. Provider output varies by operation; consult the provider documentation for its response fields. Unconfirmed calls should be checked before retrying.

Call from your client

Use the shared MCP configuration. Refresh your client's tool list after saving the connection or changing key permissions, then call the returned tool name with the example input below.

Configure Claude Code, Codex or Cursor once

Discover your enabled tools

List permitted tools in Claude format. Read every page using page and size (maximum 100) until all results have been received. Use the returned name, not a catalog capability identifier, in the tool_use block.

curl 'https://api.tooluse.net/v1/tools' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY"

Find this command in the tool list permitted by your key. Replace svc_FROM_YOUR_TOOL_LIST with its returned name. Use a new Idempotency-Key for each new call and retain it when retrying that same call.

HTTP call

curl 'https://api.tooluse.net/v1/tool-calls' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY" \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: replace-with-a-new-call-id' \
  --data '{
  "type": "tool_use",
  "id": "toolu_example",
  "name": "svc_FROM_YOUR_TOOL_LIST",
  "input": {
    "query": {
      "keywords": "IBM"
    }
  }
}'

Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.

Commands

Read an Alpha Vantage quote — alphavantage.quotes.get

Read one supported ticker’s Global Quote, preserving the provider’s numbered field names and decimal strings. No realtime/delayed entitlement is requested; data freshness follows your key’s standard endpoint access. Not an order/trade action, bulk quote, historical time series or investment recommendation.

This is a read operation. Provider rate limits and data access rules still apply.

Connect and use

Parameters

Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.

Parameter Type Required in parent Description Constraints
query object Required additionalProperties: false
query.symbol string Required One ticker from symbols.search, for example IBM or TSCO.LON. pattern: "^[A-Z0-9][A-Z0-9._:-]{0,39}$"

Full JSON Schema

Full JSON Schema

Example input

{
  "query": {
    "symbol": "IBM"
  }
}

At most 1 provider requests per invocation; timeout: 30 seconds.

Read global market session status — alphavantage.markets.status

Read provider market/session metadata: region, exchange names, local opening/closing times, current status and notes. This is the provider’s current session status, not a streaming feed or an exchange calendar export.

This is a read operation. Provider rate limits and data access rules still apply.

Connect and use

Parameters

Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.

This tool has no input parameters.

Full JSON Schema

Full JSON Schema

Example input

{}

At most 1 provider requests per invocation; timeout: 30 seconds.

Errors

Check the key's expiry, revocation, workspace and allowed operations.

Reuse the same idempotency key only for the same request.

The connection or provider limit has been reached. Check the receipt before retrying.

Test the connection

Open the integration's commands below to inspect parameters and examples. Start with a read command for an account or resource you can access. Refresh your client's tool list, use the returned tool name, and check the execution result and usage. Provider charges and permissions still apply. Never test a write against production data without reviewing it.

Official provider documentation

Type to search…

↑↓ navigate↵ selectEsc close