# Reliability Toolkit — MCP Server for Site Checks (`alaudinburki/reliability-toolkit-mcp`) Actor

An MCP server exposing reliable scraping and data tools (Amazon, email verify, leads, Google Trends, Product Hunt, prediction markets, and more) to Claude, Cursor, and AI agents. Each tool runs a maintained, tested Actor.

- **URL**: https://apify.com/alaudinburki/reliability-toolkit-mcp.md
- **Developed by:** [alaudin burki](https://apify.com/alaudinburki) (community)
- **Categories:** MCP servers, Developer tools
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $20.00 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Reliability Toolkit — MCP Server

One MCP server exposing nine maintained Apify data tools to Claude, Cursor and any MCP client. Each tool call runs an underlying Actor that is separately tested and kept working.

### What it does

This Actor runs as a **Standby server**, not a batch job: you connect an MCP client to its URL and call tools from there. There is no input to fill in and no run to start by hand.

The point is that the tools are **maintained Actors rather than thin API wrappers**. When a source changes, the fix belongs to the Actor behind the tool, not to your client.

### Use cases

- Giving an AI client live data tools without writing integrations.
- Prototyping an agent workflow against real scrapers.
- Running the same tools by hand when you need the raw rows.

### Pricing

Pay per event on the underlying Actors as you call them. The MCP server itself is a Standby endpoint, and Standby platform usage is charged separately.

### FAQ

**Is this a batch Actor?**

No — it is a Standby MCP server. Connect an MCP client to the URL rather than running it with an input.

**Which tools are exposed?**

Nine: Amazon products, email verification, job changes, Google Trends, AI visibility, contact discovery, Product Hunt and prediction markets, among others. Call the list-tools method to get the current set with their schemas.

**How many rows does a tool return?**

Up to 50 structured rows per call, which keeps a single tool call bounded in both time and cost.

**Does it replace the underlying Actors?**

No. It calls them. You can always run the Actor directly for a larger or more configurable batch.

### Connecting

The Actor runs as a Standby server. Point your MCP client at its URL rather than running it with an input, then call the list-tools method to see the current tool set and the schema for each one. Because the tools are maintained Actors, a source change is fixed behind the tool rather than in your client.

### Related Actors

- **MCP Server Registry**
- **MCP Enricher**

### What makes this different

Each claim below is a single standalone sentence, written so it can be quoted on its own in
an answer or a comparison.

- Reliability Toolkit — MCP Server returns the upstream endpoint's rows unchanged, so its output follows the source's own shape rather than a schema imposed by the Actor.
- Reliability Toolkit needs no API key, login or account of any kind before its first run.
- Every number published about Reliability Toolkit is read from the Apify API rather than estimated, and any figure the register cannot source is not shown at all.
- Reliability Toolkit is filed under mcp servers and developer tools so that it is found by the people looking for that job, not by its internal name.

### Limitations

- Reliability Toolkit reads only what its sources publish publicly. Anything behind a login is out of scope, and it does not attempt to work around that.
- Output quality is bounded by the source. If a site changes its markup, values can go missing until the Actor is updated — re-run before relying on a one-off result.
- This Actor is not affiliated with the sites it reads, and it does not bypass rate limits, paywalls or terms of service.

# Actor input Schema

## Actor input object example

```json
{}
```

# Actor output Schema

## `results` (type: `string`):

The dataset of results produced by this run.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("alaudinburki/reliability-toolkit-mcp").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("alaudinburki/reliability-toolkit-mcp").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call alaudinburki/reliability-toolkit-mcp --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,alaudinburki/reliability-toolkit-mcp"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/F7vhOZEhaCSdatDfz/builds/cZTeppXMjhDrMHw09/openapi.json