Self-hosted MCP server that turns agent output into private (signed, expiring, revocable) or public links.
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-vitrine","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.
# vitrine [](https://github.com/edgar971/vitrine/actions/workflows/ci.yml)   **Shareable links for what your AI agent makes.** vitrine is a small, self-hosted MCP server. Your agent publishes an HTML report, a chart, a PDF, a folder of files or a single React component, and gets back a link that opens in any browser. - **Private by default.** Links are signed, expire and can be revoked. An artifact becomes public only after you approve it. - **One link per artifact.** When the agent revises it, the link stays the same. - **Know what happened to a link.** A link can carry a passcode, be revoked on its own and count its views, anonymously. A public artifact can go private again on a date. - **Any MCP client.** Claude Code, Hermes Agent, or anything that speaks MCP over HTTP. - **Easy to run.** One process, one port, one folder of files. No database. ## Install With [`uv`](https://docs.astral.sh/uv/) (it fetches Python 3.15 for you): ```bash uvx mcp-vitrine --version # run without installing uv tool install mcp-vitrine # or install the `mcp-vitrine` command ``` Or with Docker. `stable` is the newest release; for a deployment, pin a version from the [releases](https://github.com/edgar971/vitrine/releases) instead: ```bash docker pull ghcr.io/edgar971/vitrine:stable ``` **Upgrading from `0.1.x`?** `0.2.0` moves `meta.json` to schema 2, so run `uvx mcp-vitrine migrate` once against your `data_dir` before starting the new version — `serve` refuses to start on old data until you do. See [operations § 4](https://github.com/edgar971/vitrine/blob/main/docs/operations.md#4-upgrades-and-migrations). ## Run it vitrine needs a secret, to sign links, and one token per client: ```bash export VITRINE_SECRET="$(uvx mcp-vitrine secret new)" uvx mcp-vitrine token …
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.