DexScan New Pairs Scraper avatar
DexScan New Pairs Scraper

Pricing

Pay per event

Go to Store
DexScan New Pairs Scraper

DexScan New Pairs Scraper

Developed by

Muhammet Akkurt

Muhammet Akkurt

Maintained by Community

DexScan New Pairs Scraper monitors newly created cryptocurrency token pairs across Solana, Ethereum, BNB Smart Chain, Base, Blast. This Apify actor lets you filter pairs by age, liquidity, volume, and security metrics—enabling crypto investors to discover early-stage tokens with detailed market data

5.0 (2)

Pricing

Pay per event

3

Total users

44

Monthly users

29

Runs succeeded

>99%

Last modified

2 months ago

You can access the DexScan New Pairs Scraper 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",
"muhammetakkurtt/dexscan-new-pairs-scraper"
],
"env": {
"APIFY_TOKEN": "<YOUR_API_TOKEN>"
}
}
}
}

Configure MCP server with DexScan New Pairs Scraper

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=muhammetakkurtt/dexscan-new-pairs-scraper",
"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.