# MEV-Boost Relays Scraper (`parseforge/mevboost-relays-scraper`) Actor

Fetches the current list of active MEV-Boost relay endpoints and their status from the official monitor feed, returning each relay as a flat row for validator configuration or monitoring.

- **URL**: https://apify.com/parseforge/mevboost-relays-scraper.md
- **Developed by:** [ParseForge](https://apify.com/parseforge) (community)
- **Categories:** Automation, Integrations, Developer tools
- **Stats:** 2 total users, 1 monthly users, 89.7% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $7.50 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

[![ParseForge](https://raw.githubusercontent.com/ParseForge/apify-assets/main/banner.jpg)](https://apify.com/parseforge?fpr=vmoqkp)

### MEV-Boost Relays Scraper

**Scrape every active MEV-Boost relay URL and its latest status, up to one million per run.** No signup or API key. Export the list to CSV, JSON, Excel, or XML for validator monitoring or research.

Finding a reliable, up-to-date list of MEV-Boost relays means parsing block explorer pages or piecing together community lists that go stale. This reads the official public relay monitor feed directly and returns the active relays with their URLs and current operational status in one fixed schema. No manual curation, no dead links.

| Who uses it | What they scrape MEV-Boost Relays for |
|---|---|
| Blockchain infrastructure engineers | Checking which third-party relays are live before configuring a validator client |
| MEV researchers | Auditing the diversity and availability of relay endpoints over time |
| Data analysts at staking pools | Building a trusted relay allowlist for validator operations |

### What it does

This Actor collects the current list of active MEV-Boost relays and returns each relay's URL and status as a flat row.

- 🔌 **Relay URLs:** the full HTTPS endpoint for each active relay.
- 📡 **Live status check:** whether the relay is currently reachable and operational.
- 📊 **Structured output:** a flat array of relays, one object per row, with a fixed schema.

Results export to CSV, JSON, Excel, or XML, or straight from the API.

### What you can do with MEV-Boost Relays data

**🔎 Audit relay availability before a merge or hard fork.**

An infrastructure engineer fetches the live relay list to confirm which endpoints are reachable and to update the `--mev-boost-relays` flag in a Lighthouse or Prysm configuration.

**📋 Build a relay health dashboard.**

A data analyst runs the actor periodically to record the relay URLs and their status, feeding a monitoring dashboard that alerts on relay outages.

**🗂️ Populate a validator relay allowlist.**

A staking pool operator scrapes the list to seed the allowlist used across thousands of validators, ensuring only active, known relays are permitted.

### Why choose this scraper

| | What you get |
|---|---|
| **Current relay list** | Every run polls the canonical relay monitor to return only the active relays at that moment |
| **No stale data** | You always get the live snapshot, never a cached or hand-maintained list |
| **Validator ready** | The output maps directly to the relay URLs your consensus-layer client expects |

### How it compares

No other Store actor targets MEV-Boost Relays the same way, so the honest comparison is with the alternatives teams actually weigh.

| | MEV-Boost Relays Scraper | Build it in-house | By hand |
|---|---|---|---|
| Setup | Run it now, zero config | Days of engineering | None, but hours per pull |
| When MEV-Boost Relays changes | Maintained for you | You fix it | You re-learn the page |
| Proxies, retries, anti-bot | Built in | Your problem | Browser only |
| Output | Fixed JSON schema, CSV/Excel export | Whatever you build | Copy-paste |
| Cost | Pay per result | Engineering time | Analyst hours |

### Configure the run

Set a limit on the maximum number of relays to collect per run; the actor stops once that count is reached. The Input tab lists every parameter.

A first run with the defaults:

```json
{
 "maxItems": 10
}
```

A larger pull:

```json
{
 "maxItems": 200
}
```

### Pricing

Pay-per-result: **$0.0085 per result** collected. You pay only for the results written to your dataset.

| Results collected | Approximate cost |
|---|---|
| 100 results | $0.85 |
| 1,000 results | $8.50 |
| 10,000 results | $85.00 |

New Apify accounts start with $5 in free credit.

### Free users

Free-plan runs return up to 10 results as a preview. [Upgrade your Apify plan](https://console.apify.com/sign-up?fpr=vmoqkp) to collect up to 1,000,000 results per run.

### Run it

1. [Create a free Apify account with $5 in credit](https://console.apify.com/sign-up?fpr=vmoqkp).
2. Open the [MEV-Boost Relays Scraper](https://apify.com/parseforge/mevboost-relays-scraper?fpr=vmoqkp).
3. Set your inputs and any filters, then click **Start**.
4. Export the results as CSV, Excel, JSON, or XML from the **Dataset** tab.

Run it programmatically through the [Apify API](https://docs.apify.com/api/v2) (`run-sync-get-dataset-items`) or the [ApifyClient](https://docs.apify.com/api/client/js) for JavaScript and Python.

### Use with AI agents (MCP)

Give an AI agent live access to MEV-Boost Relays through the Model Context Protocol. Add the Actor to Claude, Cursor, or any MCP client:

```bash
claude mcp add --transport http apify "https://mcp.apify.com/?tools=parseforge/mevboost-relays-scraper"
```

Then prompt it in plain language to run the scraper and read back the results.

### Troubleshooting

**Why am I getting no results?**

The monitor feed may be unreachable or may have reported zero active relays at that moment. Check the actor log for HTTP errors and retry after a few minutes.

**The list has fewer relays than I expected.**

The actor returns only relays the monitor currently considers active. Some relays may be undergoing maintenance or have been delisted; check the monitor UI for historical data.

**Can I get historical relay status?**

Each run captures a single snapshot. To build a history, schedule the actor and store the output in a key-value store or a time-series database.

**The run takes too long.**

The actor makes one HTTP request and completes quickly. Delays are usually due to network latency to the monitor endpoint or a slow Apify platform startup.

### FAQ

| Question | Answer |
|---|---|
| Where does the relay data come from? | It reads from the public MEV-Boost relay monitor endpoint that tracks the status of relays in the Ethereum ecosystem. |
| Does this actor need an API key or Ethereum node? | No. It fetches the public relay monitor feed directly and does not require any node connection, wallet, or API registration. |
| How often should I run this? | Relay lists change infrequently, but running it daily or before validator key restarts ensures your client uses only active endpoints. |
| What output format does the actor produce? | It returns a dataset you can download as CSV, JSON, Excel, XML, or push directly to an Apify table. |
| Can I get more than the default number of relays? | Yes, set the `maxItems` input to any number up to one million; the actor stops early if fewer relays are active. |
| Does this scrape relay payload bids or block data? | No, it only collects relay endpoint URLs and their current operational status from the monitor feed. |
| Is the relay list filtered by network? | The public monitor feed is Ethereum mainnet by default; the actor returns whatever relays that feed currently reports as active. |
| Can I export the list for Lighthouse or Teku? | Yes, export the relay URLs as a CSV or text file and reference it in your validator client configuration. |

### Related actors

Browse the full [ParseForge collection](https://apify.com/parseforge?fpr=vmoqkp) for more scrapers.

🆘 **Need help?** Email parseforge@protonmail.com with your run ID, your input, and what you expected.

⚠️ **Disclaimer.** This Actor is unofficial and is not affiliated with, endorsed by, or sponsored by the respective relay operators. It collects only publicly available data. You are responsible for using the collected data in compliance with the source's terms of service and applicable data-protection laws, including GDPR, CCPA, and PIPL. Do not use it to collect personal data unlawfully.

# Actor input Schema

## `maxItems` (type: `integer`):

How many relays to collect per run.

## Actor input object example

```json
{
  "maxItems": 10
}
```

# Actor output Schema

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

No description

# 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 = {
    "maxItems": 10
};

// Run the Actor and wait for it to finish
const run = await client.actor("parseforge/mevboost-relays-scraper").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 = { "maxItems": 10 }

# Run the Actor and wait for it to finish
run = client.actor("parseforge/mevboost-relays-scraper").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 '{
  "maxItems": 10
}' |
apify call parseforge/mevboost-relays-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,parseforge/mevboost-relays-scraper"
        }
    }
}

```

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/56jJ1ZpNp7ifS0mq6/builds/owcPoptQbKynMeCnI/openapi.json