IDLE Protocol

com.earnidlePublished by earnidle.comv1.0.5Updated Oct 25, 2026

Web scraping, inference, DNS, monitoring from residential IPs — pay per request in USDC

Overview

AI-generated overview

A local MCP server that lets an assistant run web scraping, inference, DNS and monitoring tasks from residential IPs, paid per request in USDC.

What you can do
Run web scraping tasks through residential IPs, billed per request in USDC, according to the registry description. Perform inference and DNS lookups through the same per-request paid service. Carry out monitoring tasks from residential IPs. No tool list is published, so the exact operations and their parameters are not documented here.
When to use it
Consider it when a task needs requests or lookups to originate from residential IP addresses, or when you want usage billed per request in USDC rather than through a subscription. It is a poor fit if you need a documented tool list or cannot pay in USDC.
Requirements
Runs as a local process on the user's machine, started with npx from the npm package @idleprotocol/mcp over stdio. Desktop only; not executable on the web. No authentication, environment variables or headers are declared, but paying per request in USDC implies a funded wallet or account arrangement that is not described.
Before you install
Requests are billed in USDC, so usage spends real money; set limits before running anything at scale. The payment mechanism and any wallet or key it needs are not documented, and no credentials are declared. Scraping and monitoring from residential IPs may violate target sites' terms and carries legal or reputational risk. No tool list or README is available to review what data is sent where.

Installation

In SourceWeft

  1. Open IDLE Protocol in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.5LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.