MCP Hub Builder v2

# MCP Hub Builder v2

Built by Dead Brands (deadbrands.co). Outside helper on the original draft: Eva.

Build a public MCP hub surface without leaking private ops: overlay deploys, a dynamic-layer QA checklist, and deploy receipts.

## Purpose

Help an outside team ship an MCP-compatible hub (tools, skills list, docs) that stays secure, verifiable, and free of internal-only details. This is not the published MCP Hub Builder (that skill covers standing up rooms, instant keys, trust tiers, and a public modlog). Different job: this v2 is the overlay-deploy + dynamic-layer QA + failure-receipt playbook for an already-public hub surface. Do not overwrite the published mcp-hub-builder slug.

## When to use

- You are publishing or updating a public MCP hub or docs portal.
- A deploy might overwrite a newer tree with a stale full restore.
- You need a checklist so animations, scripts, and links still work after publish.

## Limits

- Do not put secrets, private hostnames, onion addresses, crew nicknames, or internal doctrine on public pages.
- Do not claim affiliation you do not have with MCP vendors; "compatible with MCP" / "speaks MCP as transport" plus a no-affiliation disclaimer is enough.
- Credential-touching changes need a human owner gate.
- Full-tree restores from old tarballs are out of scope — prefer overlay deploys.
- Do not silently overwrite an older published skill of the same family; ship as a new slug or log a supersede.

## Steps

1. Pull the current live tree before editing.
2. Change only the overlay paths you intend to ship.
3. Run the dynamic-layer QA checklist: scripts load without console errors; primary CTAs resolve (no 404); docs index and machine-readable inventory (for example `llms.txt`) match what you shipped; any live status widget updates or is honestly marked unavailable.
4. Deploy the overlay.
5. Fetch the public URLs and confirm served bytes.
6. Write a deploy receipt: what changed, build stamp, checklist results, verifier time.

## Examples

### Example A — new skill page, avoid full-tree restore

Input: Hub docs gained a new skill page; old full-tree zip almost restored over it.

Output:
- Stop full restore; overlay only `/hub/skills/new-skill/`.
- QA checklist pass; receipt filed; live fetch shows the new page.

### Example B — failed overlay / CTA 404 / llms.txt mismatch

Input: Overlay shipped a new "Join" button pointing at `/discord-join` while the live route is `/discord/join`. `llms.txt` still lists the old skill count.

Output:
- Dynamic-layer QA fails: primary CTA returns 404; inventory count mismatches the hub skills page.
- Fix the href, regenerate `llms.txt` (or the dynamic count source) from the live published set, redeploy overlay only.
- Re-fetch `/discord/join` → 200; skills count on `llms.txt` matches the hub index; receipt records both failures and the fix stamp.