Relace MCP server
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":"relace-mcp-server","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.
# relace-mcp-server [](https://pypi.org/project/relace-mcp-server/) Official Relace MCP server. Currently supports [Fast Agentic Search](https://www.relace.ai/blog/fast-agentic-search) via the `relace_search` tool. ## Installation See [Relace MCP Installation docs](https://docs.relace.ai/docs/fast-agentic-search/mcp-installation) for detailed instructions. ## Releasing 1. [Create a new release](https://github.com/squack-io/relace-mcp-server/releases/new) 2. Enter a new tag (e.g., `v0.1.4`) 3. Publish the release The workflow will automatically build and publish to PyPI, with the package version derived from the git tag.
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.