Other · Remote MCP server
SignalPipe
Buying-intent judgement for AI agents: a three-judge panel scores any text as buyer or not.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.AbYousef739/signalpipe- Version
- 2.1.3
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-09-29
- Updated
- 2026-09-29
- Publisher
- AbYousef739 (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/AbYousef739) · how
- Website
- signalpipe.io
- Repository
- github.com/AbYousef739/signalpipe
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://api.signalpipe.io/mcp | 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
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect SignalPipe
SignalPipe is a remote MCP server: there is nothing to install. Its endpoint is https://api.signalpipe.io/mcp, 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
More other servers
| Server | Runs |
|---|---|
| Signal BureauSigB (Signal Bureau): maintained, source-traced record of entities and events in your named domain. | Remote · HTTPLive check: ✓ handshake |
| Signal-One by EMETZORVerified external-state intelligence for agents with corroborated evidence and ANSWER or WAIT. | Remote · HTTPLive check: ✗ no handshake |
| SignalBrainVerifiable receipts for governed process changes; emit, validate, and gate trust. | Local · stdio |
| Signallabs MCPCompetitive Intelligence MCP: generate AI battlecards, track competitors, monitor market signals. | Local · stdio |
| SignalRavenLinkedIn buying-intent signals, intelligence reports and delivery settings for your workspace. | Remote · HTTPLive check: sign-in required |
| SignalsDeduplicated, entity-resolved funding rounds, acquisitions, and exec moves as MCP tools. | Remote · HTTPLive check: ✓ handshake |
| SignalsGB & IRE horse racing signals: AI scores, fair prices, draw bias, and a frozen public tips ledger. | Remote · HTTPLive check: ✓ handshake |
| SIGNALS Loyalty Agent Platform63 MCP tools for loyalty programs, rewards, and member operations with HITL approval. | Remote · HTTPLive check: sign-in required |