402Signal

io.github.402signalhqPublished by GitHub account 402signalhqv0.3.2Updated Oct 11, 2026

Check paid API offers before your agent spends. Qualifying routes: $0.003 USDC. Normal misses: free.

VerifiedStreamable HTTPWeb executableFinanceBusiness & Commerce

Overview

AI-generated overview

A remote MCP endpoint that lets an assistant check paid API offers before an agent spends money on them.

What you can do
Check paid API offers before an agent spends on them, according to the registry description. Qualifying routes are described as costing $0.003 USDC, while normal misses are described as free. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Consider it when an agent is about to call paid APIs and you want a pre-spend check of the offers involved. It is not aimed at general search, data retrieval or development tasks.
Requirements
A remote MCP endpoint at the provider's site, connected over streamable HTTP. No authentication, environment variables or headers are declared. Network access to the endpoint is required.
Before you install
The service involves payments: qualifying routes are stated to cost $0.003 USDC, so using it may spend funds, and a wallet or payment arrangement is implied though not documented. No tools, authentication or data-handling details are published, so verify costs and what is sent to the provider before relying on it.

Installation

In SourceWeft

  1. Open 402Signal 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.402signalhq%2F402signal/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": {
    "402signal": {
      "type": "http",
      "url": "https://402signal.com/mcp/v0.3.1"
    }
  }
}

Tools

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

Version history

1
  1. v0.3.2LatestSep 16, 2026

Score

28% 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.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.