mcp-server
Use when implementing the Node composition app for the W9 MCP server.
- License 许可
- MIT
- 所属仓库
- jeswr/solid-sdk
- 最近更新
- 2026-11-15
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- mcp-server
- description
- Use when implementing the Node composition app for the W9 MCP server.
02 资源文件 25
- 脚本api/index.ts201 B
- 参考文档package.json1.1 KB
- 参考文档README.md8.6 KB
- 脚本src/config.ts2.1 KB
- 脚本src/handler.test.ts20.4 KB
- 脚本src/handler.ts16.4 KB
- 脚本src/index.ts550 B
- 脚本src/lws.test.ts4.5 KB
- 脚本src/node-handler.test.ts12.1 KB
- 脚本src/node-handler.ts3.2 KB
- 脚本src/persistence.test.ts2.8 KB
- 脚本src/persistence.ts3.6 KB
- 脚本src/pod.test.ts4.4 KB
- 脚本src/pod.ts4.4 KB
- 脚本src/security.ts2.8 KB
- 脚本src/single-user.test.ts5.8 KB
- 脚本src/single-user.ts3.9 KB
- 脚本src/vercel.test.ts1.1 KB
- 脚本test/connectors.e2e.test.ts25.1 KB
- 脚本test/css.e2e.test.ts11.5 KB
- 脚本test/css.ts14.0 KB
- 脚本test/navigation.ts525 B
- 参考文档tsconfig.json250 B
- 参考文档vercel.json194 B
- 脚本vitest.config.ts337 B
03 SKILL.md 正文
<!-- AUTHORED-BY Codex GPT-6.1-Sol -->
MCP server composition
Read the W9 specs/mcp/DESIGN.md and MCP-11 task in the planning repository before
composing transports, OAuth or consent. This is a private Node >=24 ESM app, with a
plain node:http entry and an exported Web Request → Promise<Response> handler.
The app composes the existing MCP HTTP transport, OAuth core, encrypted atomic vault,
and broker sessions. Browser completion requires the flow cookie, callback state,
same-origin form POST and single-use CSRF-protected consent. Never expose the core's
trusted authorize seam as an unauthenticated route. OAuth records and the signing key
share the vault; Vercel requires shared KV. Single-user mode requires a separate MCP
bearer and keeps CSS DPoP credentials server-side. Preserve read-only defaults.
Fragment WebID login resolves the profile issuer and binds the callback to that exact
verified WebID. Native continuation links preserve form-action 'self' without scripts.
Keep the app's CSS adapter fail-closed: verify actual LDP types before translating
create-only container conflicts, and byte-verify strong binary validators with unique
memory-mutex ownership markers. Never adopt a replaced lock or a weak validator.
Internal dependencies must use workspace:*. Use fixtures and injected services in tests. Run lint, build, typecheck and test through pnpm. Do not deploy or publish from this task.
Connector acceptance lives in test/connectors.e2e.test.ts; test:e2e runs it and the
original CSS suite sequentially, while test:e2e:connectors selects it alone. Reuse
test/css.ts for native browser forms, CSS controls, account seeding and TLS lifecycle.
Discover endpoints from the protected-resource challenge/AS metadata, retain Claude's
and ChatGPT's exact HTTPS callback URIs, and intercept callbacks before network access.
Both CIMD and DCR are advertised and must pass. Keep metadata serving on local TLS,
CSS behind the loopback-only Unix-socket proxy, and non-local client fetches refused.
Search tests use generic notes outside private/pkg; do not expose protected PKG memory
to satisfy generic search. Pin current agent/context listing behavior until sst-5ax.38,
with its named acceptance todo. Use a shared issuer/key/store for wrong-audience tests.
04 同仓库更多 Skills
storage-conformance
Work on @jeswr/storage-conformance, the shared storage conformance suite package in the Solid SDK workspace.
fetch-rdf-engine-tests
Maintain fetch-rdf's real Node WASM parser integration tests without introducing a reverse engine dependency in fetch-rdf.
alpha
Use when checking fixtures, including folded YAML descriptions.
widget
Use when testing package skills: YAML quoting works.
web-seo
Use when improving technical and entity SEO for a modern personal, portfolio, documentation, or marketing site, including crawlable HTML, canonical metadata, sitemap and robots, Person/ProfilePage JSON-LD, Core Web Vitals, and honest ranking expectations.
solid-wac
Use when implementing or auditing Solid server WAC authorization, ACL creation and inheritance, auxiliary-resource escalation, method-to-mode mapping, 401 versus 403 challenges, WAC-Allow, or defensive typed ACL parsing with @solid/object and @rdfjs/wrapper.