Stock Dividends (investing.com) avatar
Stock Dividends (investing.com)

Pricing

$5.99 / 1,000 results

Go to Store
Stock Dividends (investing.com)

Stock Dividends (investing.com)

Developed by

Pinto Studio

Pinto Studio

Maintained by Community

The Stock Dividends Data Actor retrieves comprehensive dividend information for publicly traded stocks from Investing.com.

0.0 (0)

Pricing

$5.99 / 1,000 results

0

Total users

1

Monthly users

1

Runs succeeded

>99%

Last modified

a day ago

You can access the Stock Dividends (investing.com) programmatically from your own applications by using the Apify API. You can also choose the language preference from below. To use the Apify API, you’ll need an Apify account and your API token, found in Integrations settings in Apify Console.

{
"mcpServers": {
"apify": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.apify.com/sse?actors=pintostudio/stock-dividends-investing-com",
"--header",
"Authorization: Bearer <YOUR_API_TOKEN>"
]
}
}
}

Configure MCP server with Stock Dividends (investing.com)

You have a few options for interacting with the MCP server:

  • Use mcp.apify.com via mcp-remote from your local machine to connect and authenticate using OAuth or an API token (as shown in the JSON configuration above).

  • Set up the connection directly in your MCP client UI by providing the URL https://mcp.apify.com/sse?actors=pintostudio/stock-dividends-investing-com along with an API token (or use OAuth).

  • Connect to mcp.apify.com via Server-Sent Events (SSE), as shown below:

{
"mcpServers": {
"apify": {
"type": "sse",
"url": "https://mcp.apify.com/sse?actors=pintostudio/stock-dividends-investing-com",
"headers": {
"Authorization": "Bearer <YOUR_API_TOKEN>"
}
}
}
}

You can connect to the Apify MCP Server using clients like Tester MCP Client, or any other MCP client of your choice.

If you want to learn more about our Apify MCP implementation, check out our MCP documentation. To learn more about the Model Context Protocol in general, refer to the official MCP documentation or read our blog post.