ChainList EVM RPC Endpoints Scraper

ChainList EVM RPC Endpoints Scraper

Scrape EVM RPC endpoints from ChainList, filtered by chain ID, name, or faucet availability. Every endpoint comes with its chain name, chain ID, native currency, and RPC URL list. No API key required. Export to CSV, JSON, Excel, or XML.

Finding reliable RPC endpoints across dozens of EVM chains means manually clicking through ChainList pages and copying URLs one by one. This Actor reads the public ChainList directory directly, letting you filter by chain ID, name substring, or faucet support, and returns every matching endpoint in a single structured dataset.

Who uses it	What they scrape ChainList for
Web3 developers	Populate their dApp's RPC fallback list with verified endpoints for a specific chain.
Infrastructure engineers	Audit RPC endpoint availability and chain metadata across multiple EVM networks.
Blockchain data analysts	Build a reference table of chain IDs, native currencies, and active RPC nodes.

What it does

This Actor collects EVM RPC endpoints from ChainList by chain ID, name filter, or faucet availability, and returns each one as a flat row with its chain metadata and RPC URLs.

• ⛓️ Chain ID filter: restrict results to a single EVM chain by its numeric chain ID.
• 🔍 Name search: case-insensitive substring match on chain name to find networks quickly.
• 🚰 Faucet filter: return only chains that have at least one listed faucet.
• 📦 Bulk export: collect up to a million endpoints per run and export as CSV, JSON, Excel, or XML.

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

What you can do with ChainList data

🛠️ Seed a dApp's RPC provider list.

A Web3 developer scrapes all RPC endpoints for chain ID 1, exports them as JSON, and feeds the URLs into their wallet's network configuration.

📊 Monitor RPC endpoint health across chains.

An infrastructure engineer runs the Actor daily for multiple chain IDs, collects the endpoint lists, and pipes them into a latency checker to flag slow nodes.

🔎 Discover new EVM chains by name.

A researcher filters by nameContains 'zksync' to pull every matching chain and its RPC details, then compares native currency symbols and faucet availability.

🚰 Find chains with active faucets.

A testnet user sets hasFaucets to true, scrapes all matching endpoints, and picks a chain with a working faucet for development.

Why choose this scraper

	What you get
No API key	Reads the public ChainList directory with zero authentication.
Flat schema	Every endpoint is a single row with chain name, chain ID, currency, and RPC URLs.
Selective output	Filters by chain ID, name, or faucet presence before data lands in your dataset.
High volume	Collect up to 1,000,000 endpoints in a single run.

How it compares

No other Store actor targets ChainList the same way, so the honest comparison is with the alternatives teams actually weigh.

	ChainList EVM RPC Endpoints Scraper	Build it in-house	By hand
Setup	Run it now, zero config	Days of engineering	None, but hours per pull
When ChainList 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

Drive the Actor with an optional chain ID, a name substring, or a faucet-only toggle, and filters run as each endpoint is read so only matches reach your dataset. The Input tab lists every parameter.

A first run with the defaults:

{
  "maxItems": 10
}

A larger pull:

{
  "maxItems": 200
}

Free users

Free-plan runs return up to 10 results as a preview. Upgrade your Apify plan to collect up to 1,000,000 results per run.

Run it

1. Create a free Apify account with $5 in credit.
2. Open the ChainList EVM RPC Endpoints Scraper.
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 (run-sync-get-dataset-items) or the ApifyClient for JavaScript and Python.

Use with AI agents (MCP)

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

claude mcp add --transport http apify "https://mcp.apify.com?tools=parseforge/chainlist-rpcs-scraper"

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

Troubleshooting

Why am I getting zero results?

Check your filters. A chainId that does not exist, a nameContains substring that matches nothing, or setting hasFaucets to true when no listed chain has a faucet will all return empty. Try removing all filters and running with a small maxItems to verify connectivity.

The run is taking too long.

Lower the maxItems value or apply a chainId filter to narrow the scope. Scraping the full directory with a high maxItems will take longer.

Some RPC URLs in the output are not working.

ChainList lists endpoints submitted by the community. The Actor faithfully returns what is published. Combine this Actor with an RPC health checker to validate URLs after scraping.

I need data for a chain that is not appearing.

Ensure your filters are not excluding it. If the chain is genuinely missing from ChainList's public directory, the Actor cannot return it. ChainList's catalog is community-maintained.

FAQ

Question	Answer
Do I need an API key or login to scrape ChainList?	No. This Actor reads the public ChainList directory directly and requires no authentication, API key, or account registration.
What data does each scraped endpoint row contain?	Each row includes the chain name, chain ID, native currency symbol, a list of RPC URLs, and whether faucets are available. The exact field list is shown in the sample output on the Actor's page.
Can I filter by a specific blockchain network?	Yes. Use the chainId input to restrict results to a single EVM chain, or use nameContains for a case-insensitive substring match on the chain name.
How many endpoints can I collect in one run?	You can set maxItems up to 1,000,000. The Actor will stop once it reaches that count or exhausts the matching endpoints.
Does this Actor return testnet endpoints?	Yes. ChainList includes both mainnet and testnet chains. You can use the nameContains filter to search for 'testnet' or specific testnet chain names.
What export formats are supported?	The dataset can be exported to CSV, JSON, Excel, or XML directly from your Apify run.
Can I schedule this Actor to run periodically?	Yes. Apify's scheduler lets you run it on a recurring interval, so you always have a fresh list of RPC endpoints.
Is the data real-time or cached?	The Actor scrapes ChainList live on each run, so you get the current state of the directory at that moment.

🆘 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 ChainList. 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.