MCP server for optional SSOT pull-worker control-plane coordination.
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":"ssot-mcp","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.
<div align="center"> <h1>ssot-mcp</h1> <p><strong>Optional MCP server for SSOT registry coordination and pull-worker campaigns.</strong></p> </div> <div align="center"> <a href="https://pypi.org/project/ssot-mcp/"><img src="https://img.shields.io/pypi/v/ssot-mcp?label=PyPI%20version" alt="PyPI version" /></a> <a href="https://pypi.org/project/ssot-mcp/"><img src="https://img.shields.io/pypi/pyversions/ssot-mcp?label=Python" alt="Supported Python versions" /></a> <a href="https://pepy.tech/project/ssot-mcp"><img src="https://static.pepy.tech/badge/ssot-mcp" alt="Downloads" /></a> <a href="https://hits.sh/github.com/groupsum/ssot-registry/"><img src="https://hits.sh/github.com/groupsum/ssot-registry.svg?style=flat-square" alt="Repository hits" /></a> <a href="https://discord.gg/mAjzxwSwRp"><img src="https://img.shields.io/badge/Discord-join%20chat-5865F2?logo=discord&logoColor=white" alt="Discord" /></a> <!-- ssot-schema-badges:start --> <img src="https://img.shields.io/badge/schema_version-0.8.0-blue" alt="schema_version 0.8.0" /> <img src="https://img.shields.io/badge/migration%20coverage-14%2F14-brightgreen" alt="Migration coverage 14/14" /> <!-- ssot-schema-badges:end --> </div> `ssot-mcp` is the optional Model Context Protocol server for SSOT. It lets MCP-capable clients coordinate registry mutations, pull-worker campaigns, leases, worker events, and campaign state through tools backed by [ssot-core](https://pypi.org/project/ssot-core/). The ordinary `.ssot/registry.json`, Python API, and [ssot-cli](https://pypi.org/project/ssot-cli/) workflows do not require this package. - GitHub: https://github.com/groupsum/ssot-registry ## What this package owns - The `ssot-mcp` console entry point - MCP tools, resources, and prompts for optional SSOT control-plane workflows - Registry entity CRUD and linking tools for MCP clients - Pull-worker campaign tools for claiming slices, renewing leases, completing slices, abandoning slices, and reading worke…
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.