I

IOConnex Web Search

Pay-per-call web search and clean-text page fetching for AI agents, using USDC payments on Base through x402.

Install IOConnex Web Search

Pick your client, then add it in one click or paste the config.

Streamable HTTP (Remote)
Server URL
https://search.ioconnex.dev/mcp

Remote servers are added in the app, not the config file: Customize → Connectors → Add custom connector, then paste this URL.

Hosted endpointLive · 2d agoLive Remote EndpointOur automated health check connected to this remote MCP endpoint successfully.Last checked 2d ago · Nov 11, 2026, 21:00 UTC

Clients with native remote MCP support can connect directly to this URL.

Remote endpoint
https://search.ioconnex.dev/mcp

Overview

IOConnex Web Search provides AI agents with web search and clean-text page fetching through MCP. Calls use x402 for pay-per-use billing in USDC on Base, rather than an API key or subscription. Reach for it when an agent needs to discover web results or retrieve page content without maintaining a conventional search API plan.

Use cases

  • Search the web for sources relevant to an agent task
  • Fetch clean text from selected pages
  • Build pay-per-call research and extraction workflows

Key features

  • Web search for AI agents
  • Clean-text page fetching
  • x402 payments in USDC on Base
  • No API key or subscription required

Tools2

What IOConnex Web Search lets your agent do. Expand a tool for its parameters.

Verified live~143 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked

Recent health check succeeded.

6/6 checks healthy over the last 22d

What it can do

From the 2 tools this server returned when we ran it.

Makes network requests · 1Read-only tools · 2

Observed 2026-10-30 in an isolated sandbox. A description of reach, not a security audit.

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

Availability100%Our rolling endpoint + install checks that succeeded.
Tools exposed2Callable tools this server registers over MCP.
Directory activity3 viewsConfig copies, upvotes, and views on AllMCPs.

How IOConnex Web Search works

What IOConnex Web Search does

IOConnex Web Search gives AI agents two web-oriented capabilities: searching the web and fetching page content as clean text. It is intended for search and data extraction workflows where an agent needs to find relevant pages, then obtain readable content from those pages for further processing.

The service uses a pay-per-call model. Each request is paid for with USDC on Base through x402, so usage is tied to individual calls rather than a recurring subscription or an API-key arrangement.

How it works

An MCP-compatible agent connects to IOConnex Web Search and invokes its web search or page-fetching capability. Search helps locate relevant online information; clean-text fetching turns a selected page into text that an agent can use in a subsequent task.

Payment is handled through x402, with USDC on the Base network. The service is therefore suited to agents that can participate in this payment flow and maintain access to the required cryptocurrency network and funds. Calls are billed individually instead of through a prepaid subscription.

Tools and capabilities

  • Web search for discovering relevant online pages.
  • Clean-text page fetching for extracting readable content from web pages.
  • Per-call payment using USDC on Base through x402.
  • Access without an API key or subscription.

Limitations and notes

IOConnex Web Search is focused on web discovery and page-content retrieval. It does not represent a general-purpose browser, database, or site-specific integration. The pay-per-call design also means that using it requires handling USDC on Base through x402, rather than supplying a conventional API credential.

The lack of an API key and subscription can simplify credential management, but payment remains part of the request flow. Consider this server when usage-based payments fit the agent architecture; choose a different service if the workflow requires a fixed subscription, key-based billing, or capabilities beyond web search and clean-text fetching.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about IOConnex Web Search

IOConnex Web Search is an MCP server that connects AI agents to pay-per-call web search and clean-text page fetching. Its main tools help agents discover online pages and retrieve readable page content. Requests use x402 payments in USDC on Base, with no API key or recurring subscription required.

IOConnex Web Search charges per call through x402 using USDC on Base. It does not require a subscription or API key, so payment is tied to individual web search or page-fetching requests.

No, IOConnex Web Search does not require an API key. Access uses pay-per-call x402 payments in USDC on Base instead of conventional key-based access.

IOConnex Web Search can fetch page content as clean text. Agents can use this capability after finding a relevant page through the server's web search function.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewIOConnex Web Search AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/ioconnex-web-search?style=directory)](https://allmcps.com/mcp/ioconnex-web-search)
HTML Embed
<a href="https://allmcps.com/mcp/ioconnex-web-search"><img src="https://allmcps.com/api/badge/ioconnex-web-search?style=directory" alt="IOConnex Web Search on AllMCPs" /></a>