io.github.servosity/wordpress-mcp
9 changes recorded. MCP Harbor re-reads this listing from the official registry every six hours and asks the live server what it exposes, and keeps what changed between one look and the next.
https://raw.githubusercontent.com/servosity/msp-skills/HEAD/AGENTS.md
− 2. **After** generating, prove nothing regressed:− `tools/maintainer/verify_all.sh <slug>` before pushing. See `CONTRIBUTING.md`.+ 2. **After** generating, retire or re-apply the fleet-wide hand-fixes (onboard.py+ does this for you), then prove nothing regressed:+ python3 tools/maintainer/replay_handfixes.py --slug <slug>+ `tools/maintainer/fleet_handfixes.json` records, per fleet-wide id, whether the+ press now generates it (retired: its entry is not demanded from `retire_at` on,+ the press's own shape is) or the replay tool re-applies it. Reconcile by hand+ only what the replay names.+ A badge also records the code it verified: `verify_live.py` stores the release+ version and the cli hash of that tag, and the catalog says "verified on vX.Y.Z"+ once the shipped release carries different code. When a report names the+ version it ran, pass `--verified-version`; for an existing badge use `--bind`.+ Never copy `cli_hash_at_release` into a badge by hand: `check_registry_state.py`+ recomputes the hash from the tag and fails a binding that is not that code.+ **Beta and live-verified are mutually exclusive.** A live-verified connector+ never says Beta. Flip and revoke only through `verify_live.py`, which moves the+ registry `status` and the README / pain-point Status paragraphs with the badge+ (the docs page follows from `render_docs_page.py`). `verify_live.py --check`+ runs in CI and fails on any disagreement; `--sync` repairs the registry and the+ Status paragraphs, and a stray "Beta" elsewhere in those two files is fixed by+ hand.+ `bash tools/maintainer/verify_all.sh --changed` (or `--slug <slug>`) while+ iterating, and the full `bash tools/maintainer/verify_all.sh` once on the final+ commit after the last rebase. Its verdict (`.verify/verdict.json`) names the+ head and base SHAs it checked. See `CONTRIBUTING.md`.
https://raw.githubusercontent.com/servosity/msp-skills/HEAD/AGENTS.md
− mentions the flag, and it cannot see the other four requirements (one sealing− before the seal, the `.mcpb` inside the sealing contract). Then: one tag per+ mentions the flag, and it cannot see the other five requirements (one sealing+ before the seal, the `.mcpb` inside the sealing contract, and the Windows+ binaries run on a Windows runner before the seal). Then: one tag per
We can't find the internet
Attempting to reconnect
Something went wrong!
Attempting to reconnect