Monitoring Checker Run Status avatar
Monitoring Checker Run Status

Pricing

Pay per usage

Go to Store
Monitoring Checker Run Status

Monitoring Checker Run Status

Developed by

Apify

Apify

Maintained by Apify

The monitoring checker run status is a part of the Apify Monitoring Suite (apify/monitoring). See its readme for more information and how to use this.

4.8 (4)

Pricing

Pay per usage

11

Total users

83

Monthly users

22

Runs succeeded

>99%

Last modified

a year ago

You can access the Monitoring Checker Run Status 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": {
"local-actors-mcp-server": {
"command": "npx",
"args": [
"-y",
"@apify/actors-mcp-server",
"--actors",
"apify/monitoring-checker-run-status"
],
"env": {
"APIFY_TOKEN": "<YOUR_API_TOKEN>"
}
}
}
}

Configure MCP server with Monitoring Checker Run Status

You can interact with the MCP server via standard input/output - stdio (as shown above), which is ideal for local integrations and command-line tools such as the Claude desktop client, or you can interact with the server through Server-Sent Events (SSE) to send messages and receive responses, which looks as follows:

{
"mcpServers": {
"remote-actors-mcp-server": {
"type": "sse",
"url": "https://mcp.apify.com/sse?actors=apify/monitoring-checker-run-status",
"headers": {
"Authorization": "Bearer <YOUR_API_TOKEN>"
}
}
}
}

You can connect to the Apify MCP Server using clients like Tester MCP Client, or any other supported 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.