Other · Remote MCP server
402Signal
Check paid API offers before your agent spends. Qualifying routes: $0.003 USDC. Normal misses: free.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.402signalhq/402signal- Version
- 0.3.2
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-09-09
- Updated
- 2026-09-09
- Publisher
- 402signalhq (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/402signalhq) · how
- Website
- 402signal.com
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://402signal.com/mcp/v0.3.1 | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- No - TLS handshake failed
- Handshake
- -
- Checked on
- 2026-10-05
How to connect 402Signal
402Signal is a remote MCP server: there is nothing to install. Its endpoint is https://402signal.com/mcp/v0.3.1, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
Site checks
The website's own root, 402signal.com, was checked for the files that tell AI systems about a site.
| File | Result |
|---|---|
/llms.txt | No real file found |
/.well-known/mcp.json | No real file found |
/.well-known/ai-plugin.json | No real file found |
/agents.json | No real file found |
More other servers
| Server | Runs |
|---|---|
| 3LT Letter MailGive AI assistants hands: send real USPS letters via MCP. | Remote · HTTPLive check: ✓ handshake |
| 402 MCPAI agents discover, pay for, and consume any Lightning-gated API autonomously. | Local · stdio |
| 402oracleSigned verification attestations for agent decisions: business, price, freshness, claim checks. | Remote · HTTPLive check: ✓ handshake |
| 402postPaid classifieds for AI agents: post a listing over MCP, pay with x402. No account. | Remote · HTTPLive check: ✓ handshake |
| 404.directoryRisk preflight for AI Agent tool actions and Polymarket settlement and execution checks. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| 409acost.com409A Cost: the site's own MCP server - calculator, enquiry (enquiry = a human handoff, not a... | Remote · HTTPLive check: ✓ handshake |
| 4botsHuman-written daily modules your chief of staff adds to the morning brief. No key, no signup. | Remote · HTTPLive check: ✓ handshake |
| 4fetchFetch a URL and get clean Markdown with metadata. No API key required; rate-limited per IP. | Remote · HTTPLive check: ✗ no handshake |