You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit cea8a93
Browse filesBrowse the repository at this point in the historyBrowse files
Make the template MCP server dual-era for spec revision 2026-07-28
This template is a generator: every project forked from it inherited a
2024-11-05 protocol pin, and scripts/eval.js asserted that handshake,
so the stale shape was test-enforced across all downstream forks.
- mcp-server.js: supportedVersions ["2026-07-28", "2024-11-05"]; add
server/discover (required by the new spec), resultType on every
result, ttlMs and cacheScope on tools/list, and -32022 with
data.supported for unsupported _meta versions. The legacy initialize
handshake is unchanged, and requests without _meta are served exactly
as before, so bare and handshake-less callers keep working.
- tests/fixtures/mcp-request.jsonl: legacy lines kept; added a modern
server/discover request carrying full _meta.
- scripts/eval.js: new "MCP dual-era contract" eval asserting the
discover shape, ttlMs and cacheScope on tools/list, and -32022 on a
bogus version. Existing legacy assertions still pass.
- PUBLISH-MCP.md: smoke tests carry the modern _meta envelope, plus a
short section on the stateless revision and dual-era posture.
- README.md: state the dual-era support so forks know what they get.
- MANIFEST.yaml: hashes refreshed via scripts/validate-hashes.sh.
node scripts/eval.js: 33/33 pass.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
-**Sortable tables** — click any column header to sort
66
-
-**Local MCP server** — optional read-only agent access through `mcp-server.js`; it runs separately from the static build
66
+
-**Local MCP server** — optional read-only agent access through `mcp-server.js`; it runs separately from the static build. Dual-era: speaks MCP spec 2026-07-28 (stateless, `server/discover`, cacheable tool lists) and legacy 2024-11-05, so generated projects work with both current and older MCP clients
67
67
-**Discovery files** — llms.txt, agents.json, RSS for machine consumption
68
68
-**Safe generated output** — generated links, CSS tokens, and client-side comparison labels are normalized or escaped
69
69
-**Subpath-safe deployment** — canonical, discovery, 404, and asset URLs preserve a configured path such as `/demo/`
0 commit comments