Foragex402

io.github.mapizarro1Published by GitHub account mapizarro1v1.0.0Updated Oct 25, 2026

Meta-search MCP for x402 agent-payable services -- find paid APIs across every registry.

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

A remote MCP meta-search server that lets an assistant find x402 agent-payable services and paid APIs across registries.

What you can do
Search across registries for x402 agent-payable services and paid APIs, per the registry description. The manifest lists no individual tools, so the exact search, filtering and result-detail operations are not documented. It is reached as a hosted remote endpoint rather than a local package.
When to use it
Useful when an assistant needs to discover paid APIs or x402-payable services offered across multiple registries, for example when planning which paid service to call for a task.
Requirements
A remote MCP client that can connect to the hosted streamable HTTP endpoint. No packages, environment variables, headers or authentication are declared.
Before you install
The server is about services that agents pay for; the manifest declares no payment handling, credentials or spending limits, so confirm how payments would be authorized before relying on results. No tools or documentation are published, so behavior and data sent to the remote host are unverified.

Installation

In SourceWeft

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

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.mapizarro1%2Fforagex402/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "foragex402": {
      "type": "http",
      "url": "https://foragex402.tablint.dev/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 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 daysRequired25 pts

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

  • Auth declaredRequired10 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.