Universal switchboard for the Context-Pipe Protocol (CPP)
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"mcp-context-pipe","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# ⛓️ Context-Pipe **The Universal Standard for Context Engineering.** [](https://github.com/luismichio/context-pipe/actions/workflows/ci.yml) [](tests/) [](https://pypi.org/project/mcp-context-pipe/) [](LICENSE.md) [](https://opensource.org/licenses/Apache-2.0) `context-pipe` is a high-performance orchestration layer directly inspired by Unix terminal piping — the same philosophy that made `cmd1 | cmd2 | cmd3` the most durable composition primitive in computing. Just as the terminal chains processes through `stdin`/`stdout` byte streams, Context-Pipe chains AI tool calls through context streams: each node does one thing, passes its output to the next, and the LLM only sees the final, refined signal. This is not a metaphor — it is a literal extension. Context-Pipe supports both **MCP piping** (chaining MCP tool calls through the orchestrator) and **terminal piping** (any binary, shell command, or script that reads `stdin` and writes `stdout` is a valid node). The two modes compose freely in a single pipe definition. And through the `mcp-pipe` CLI, it extends the terminal itself: the `mcp-pipe tool` subcommand makes any MCP server — context-mode, serena, GitHub, Firecrawl, or any server registered in `pipes.json` — directly pipeable from the shell, loading on demand, with no wrapper scripts and no IDE required: ```bash cat error.log | mcp-pipe tool semantic-sift sift_logs | rg "CRITICAL" curl -s https://example.com | mcp-pipe tool firecrawl scrape | mcp-pipe run semantic-refinery ``` Today, `mcp-pipe run <pipe>` already gives the terminal first-class access to any named pipe defined in `pipes.json`, composing terminal bin…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.