contribute-fingerprint

Runs elicit_doctor with a live elicitation probe and — with your consent — contributes the resulting capability report to the public Elicitation Support Matrix. Hosts that support MCP prompts list it in their own UI; in Claude Code it appears as a slash command.

Claude Desktop / claude.ai

Find the prompt behind the + button in the message box: Connectors → Add from your connector’s name → Contribute a fingerprint. Use Cowork mode — in our testing (Claude for Mac 1.34493, 2026-08), Chat mode’s tool calls failed with a generic error before the probe could run, while Cowork ran the flow to completion. If no dialog appears, expect the probed call to take ~40 seconds — the probe’s bound on the hosted server — and still contribute, with the timeout recorded as the verdict.

What the flow does

1. Asks you for what the report can’t see. The doctor only sees the embedded MCP client (e.g. claude-code 2.1.228), not the product around it — so the prompt collects the host product’s name and version, plus anything unusual about the setup (OS, flags, enterprise policy) as notes. All optional.
2. Asks for consent. What gets stored: the doctor report — handshake echo, capability booleans, probe verdicts; no elicitation payloads, no conversation content — plus whatever details you volunteered.
3. Runs the probed doctor call. A small elicitation dialog may appear — that is the probe; answer it. If the call times out or errors instead (some hosts advertise elicitation but never deliver the dialog), that failure is itself the finding: the flow re-runs the doctor without the probe and contributes the report with the timeout recorded in notes.
4. Shows you the report verbatim and confirms whether it was shared.

Decline to share and the same diagnostic still runs — you just see the report locally and can contribute it manually later.

Where contributions go

Shared reports land in a review queue, tied to your authenticated account — the matrix stays curated, so a contribution is evidence for review, never an automatic edit. The first prompt-driven contribution is what flipped the Claude Code remote-HTTP row (see the changelog, 2026-08-19).

Editions

• Pro (hosted) — available now. The report is contributed directly via elicit_doctor’s share: true; nothing to copy.
• Free (stdio) — available from elicitly 0.5.0. The local server has no backend to share through, so the same prompt instead assembles a pre-filled GitHub issue with your report embedded — one click to submit, zero copy-paste, and nothing is ever sent automatically. Same name, same outcome, different last hop.

No prompt support in your host?

Ask in plain words — this is the equivalent request:

Run elicit_doctor with probeElicitation true and share true. First ask me for this app’s product name and version and anything unusual about my setup, pass those along, and show me the raw JSON it returns.