RUN-019 BUILDER v4 (D17, Thu): Official MCP Registry publish bundle#10
Draft
RUN-019 BUILDER v4 (D17, Thu): Official MCP Registry publish bundle#10
Conversation
Bottleneck: DEMAND (hard 14-day rule, D17). external_24h=0 for 17
consecutive days. Official MCP Registry recovered from yesterday's 503
drift (both /v0/servers and /v0/publish respond cleanly). RUN-018 handoff
trigger MET — prep mcp-publisher submission bundle.
Ships:
- registry-submissions/ — 3 schema-validated server.json files for
io.github.vdineshk/{sg-regulatory-data,sg-cpf-calculator,sg-company-lookup}
+ README.md with 2-min Dinesh copy-paste recipe. Validated locally
with jsonschema==4.26.0 against the official ServerDetail schema.
- DINESH-READ-ME.md D16 -> D17 refresh with re-pinged ground truth,
registry-healthy pivot, and explicit D18 decision gate.
- decisions/2026-04-23-run-019-daily-report.md with Genome deltas.
Genome WHAT WORKS +:
- Schema-first registry submissions (download schema, validate before
commit, pin $schema URL in published doc).
- Registry-health gate from previous run's handoff actually executed
(concrete curl trigger -> correct decision).
Genome WHAT FAILS +:
- Cold-start 503 on SG workers is a PATTERN not an anomaly (confirmed
two days running on all 3 SG servers).
- asean-trade-rules-mcp + sg-workpass-compass-mcp have intermittent
/health on top of cold-start; excluded from bundle.
Genome ADAPTATION +:
- AWAKEN must MCP-initialize (not just /health) against each candidate
publish-target; only live JSON-RPC init exposes cold-start 503.
- Namespace discipline: io.github.<gh-owner>/<server-name>.
Conviction: Official MCP Registry listing NEW 7/10 up (bundle ready,
trigger met, untested surface). Blog/generic content marketing 6/10
down (3 posts, zero measurable organic).
Darwinian self-check: 4/4 (handoff trigger honored, runtime evidence
captured, Genome rules specific, killed default-fire content instinct).
Telemetry disclosure (anonymized): notion-search, notion-fetch,
WebFetch, Bash, Read, Write, TodoWrite, GitHub MCP. PDPA + IMDA.
8 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
external_24h = 0for 17 consecutive days./v0/servers+/v0/publishreturning 200 stably. Both clean this run — yesterday's 503 drift cleared.server.jsonfiles underregistry-submissions/(io.github.vdineshk/{sg-regulatory-data,sg-cpf-calculator,sg-company-lookup}) plus a 2-minute Dinesh copy-paste recipe inregistry-submissions/README.md. All three locally validated withjsonschema==4.26.0against the officialServerDetailschema.Genome deltas
WHAT WORKS + schema-first registry submissions; handoff gate honored when expressed as concrete curl.
WHAT FAILS + SG-worker cold-start 503 is a pattern not anomaly (3-for-3 two days running);
asean-trade-rules-mcp+sg-workpass-compass-mcpintermittent and excluded.ADAPTATION + AWAKEN must MCP-
initialize(not just/health) against each candidate publish-target; namespace disciplineio.github.<gh-owner>/<server-name>.Test plan
jsonschema==4.26.0validates all 3server.jsonfiles →[OK]initializeJSON-RPC POST to each SG worker/mcp→ warm 200 (cold 503 retried)registry.modelcontextprotocol.io/v0/servers→ 200,/v0/publish→ 400-on-empty (alive + body-validated)static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json→ 200 (22,090 bytes)mcp-publisher publish× 3 (requires GitHub OAuth device flow on his account)Telemetry disclosure (anonymized): tool_name + success/fail + latency_ms only. Singapore PDPA + IMDA agentic AI governance framework compliant.
https://claude.ai/code/session_01RCEyVRek9ft597wn2G2z94
Generated by Claude Code