A local MCP profiles your projects. A hosted registry lets someone else ask whether anyone is already building the thing they were about to start.
The case it exists for: a project that is 70% built and has not been touched in 14 months.
Runs on your machine over stdio. Reads source and git history. No network, on the Docker install.
It extracts facts, then hands them to your own model to write the description. It holds no API key, and never sends file contents anywhere.
Everything starts private. Publishing names one project at a time.
Hosted, over HTTP. Holds facets and hashes. Never source.
Three tools: search_projects, overlap_report, request_introduction.
Invite only. Every call needs a token, search included.
No sign-up, no password, no identity provider. Your machine makes a keypair and that key is your identity. The registry stores only the public half.
Redeeming an invite returns a token. The token authenticates every call. The key signs what you publish, so a stolen token can read but cannot publish.
Have an invite? Start here.
The local half runs on your machine. Two ways to install it, and they are not equivalent — the difference is stated below rather than left for you to find out.
A bundle for Claude Desktop. Download it, open it, pick the folders to profile. Nothing to install first.
Reduced isolation. The scanner and publisher stay separate processes, but not separate containers — so the scanner runs with your privileges rather than in a sandbox with no network. Point it at material you already trust.
It also does not carry git, cloc or universal-ctags, which are not Python. Document archives profile fully without them; code projects come back thinner and say which signals are missing.
Docker. The scanner gets three read-only mounts and no network at all; the publisher gets a network and no filesystem. Neither one alone can send your work anywhere.
This is the install every security claim on this page is written about.
git clone https://github.com/caerjar/mcp.cyborg.support && cd mcp.cyborg.support && cp .env.example .env && make build upAdd the registry, once you have a token
claude mcp add --transport http cyborg https://mcp.cyborg.support/mcp --header "Authorization: Bearer $CYBORG_TOKEN"Maturity infers that something looks finished, never that it works. The scanner cannot run anything.
Markdown, text and HTML are opened. Nothing else is. Archives report how much was legible.
Lowering a tier is not deletion. Copies already fetched cannot be recalled.
You learn that the owner accepts contact. The rest is their decision.
The scanner is hardened, not sandboxed. On Docker it parses source in a container that shares the host kernel. In the one-click bundle there is no container at all and it runs with your privileges. Point it at source you trust.