HCT Coordination Signals Extension for MCP - Adds urgency, timing, and approval semantics
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":"hct-mcp-signals","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.
# HCT MCP Signals (Python) Python implementation of the Harmonic Coordination Theory (HCT) Signals extension for the Model Context Protocol (MCP). ## Installation ```bash pip install hct-mcp-signals ``` ## Usage ```python from hct_mcp_signals import cue, tacet # Create a CUE signal signal = cue("orchestrator", ["analyst", "verifier"]).build() # Embed in MCP params = {"id": "task-123", "data": "..."} params = embed_signal(params, signal) ``` See the [main repository](https://github.com/stefanwiest/hct-mcp-signals) for full documentation.
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.