New Connector: Alpha Vantage

[gabriel1l]

Connector Name

Alpha Vantage

Publisher

Alpha Vantage Inc. (Verified Publisher)

Description

Access 200+ financial market data functions through Model Context Protocol (MCP). Provides real-time and historical data for stocks, forex, cryptocurrencies, technical indicators, fundamental analysis, and economic indicators.

Publisher Information

• Company: Alpha Vantage Inc.
• Contact Email: [email protected] | [email protected]
• Website: https://www.alphavantage.co | https://mcp.alphavantage.co/
• Publisher Type: Verified Publisher (we own the underlying service)

Testing

• ✅ Connector tested locally with paconn CLI
• ✅ Successfully connects to MCP server at mcp.alphavantage.co/mcp
• ✅ tools/list returns 200+ available functions
• ✅ API key policy (setqueryparameter) correctly adds authentication to requests
• ✅ Content-Type header properly set via swagger consumes declaration
• ✅ Validated with paconn validate - no errors
• ✅ All Microsoft certification rules passed

Test Credentials

Instructions for obtaining a free API key are provided in the README.md file.

Technical Details

• Uses Model Context Protocol (MCP) for dynamic tool discovery
• APIM policy (setqueryparameter) adds API key to query string automatically
• Swagger declares consumes: ["application/json"] for Content-Type header
• Single operation (ExecuteMCPRequest) provides access to all 200+ functions via JSON-RPC
• Security definition: API Key authentication in query parameter

Categories

Finance;Data

---

When submitting a connector, please make sure that you follow the requirements below, otherwise your PR might be rejected. We want to make you have a well-built connector, a smooth certification experience, and your users are happy :)

If this is your first time submitting to GitHub and you need some help, please sign up for this session.

• I attest that the connector doesn't exist on the Power Platform today. I've verified by checking the pull requests in GitHub and by searching for the connector on the platform or in the documentation.
• I attest that the connector works and I verified by deploying and testing all the operations.
• I attest that I have added detailed descriptions for all operations and parameters in the swagger file.
• I attest that I have added response schemas to my actions, unless the response schema is dynamic.
• I validated the swagger file, apiDefinition.swagger.json, by running paconn validate command.
• If this is a certified connector, I confirm that apiProperties.json has a valid brand color and doesn't use an invalid brand color, #007ee5 or #ffffff. If this is an independent publisher connector, I confirm that I am not submitting a connector icon.

If you are an Independent Publisher, you must also attest to the following to ensure a smooth publishing process:

• I have named this PR after the pattern of "Connector Name (Independent Publisher)" ex: HubSpot Marketing (Independent Publisher)
• Within this PR markdown file, I have pasted screenshots that show: 3 unique operations (actions/triggers) working within a Flow. This can be in one flow or part of multiple flows. For each one of those flows, I have pasted in screenshots of the Flow succeeding.
• Within this PR markdown file, I have pasted in a screenshot from the Test operations section within the Custom Connector UI.
• If the connector uses OAuth, I have provided detailed steps on how to create an app in the readme.md.

[gabriel1l]

@microsoft-github-policy-service agree company="Alpha Vantage Inc."