[fernando-mendoza]

Adds CI for packages/mcp (npm: nirium-mcp). Before this the package had no CI, which is how 0.6.1 reached npm without dist/. The new mcp-ci.yml follows the clean-install job in sdk-test.yml: same path-filter shape, Node 22, actions/checkout@v4 / actions/setup-node@v4, and a pack-and-install script like packages/sdk/scripts/clean-install-check.mjs.

How each "Done when" item is met

• Triggers: pull_request with paths packages/mcp/** and the workflow file itself, plus push to main with the same paths, as in sdk-test.yml.
• Build, pack, install, start the bin: npm run build (tsc), then node scripts/clean-install-check.mjs, which:
  • runs npm pack --json
  • installs the tarball into an empty temp project outside the monorepo
  • starts node_modules/.bin/nirium-mcp and sends an MCP initialize over stdio (the bin has no --help)
  • requires a valid serverInfo whose version matches package.json
  • closes stdin and requires the process to exit 0
  • initialize needs no network, the env has no secret key, and no tool is called
• Fails on a broken tarball: if dist/, main or the bin target is missing; if any *.test.* file would be published; if the bin exits before answering; or if it doesn't answer within 20 s.
• Install flags explained: both are commented where they are used.
  • --legacy-peer-deps: @stellar/mpp@0.7.1 peer-requires @stellar/stellar-sdk@^15.1.0, while nirium-mcp pins ^14, so a plain npm install fails with ERESOLVE. Tracked in packages/mcp: align @x402 and stellar-sdk with the SDK (2.28 / 16.3) #125.
  • Temporary viem install in the scratch project: mppx imports viem but declares it only as a required peer, so a clean install of 0.6.3 dies with ERR_MODULE_NOT_FOUND: viem. That bug is nirium-mcp needs viem installed by hand (missing peer of mppx, not covered by peerDependenciesMeta) #118 (fix in fix(mcp): add viem as direct dependency to resolve mppx peer import (#118) #124) and out of scope here. Once fix(mcp): add viem as direct dependency to resolve mppx peer import (#118) #124 lands, removing the viem@^2.51.0 argument makes this check cover that bug too.

Local validation (Node 22.23.3, npm 10.9)

• Replayed the workflow from a clean state (no node_modules, dist, or lockfile): install, build and the check all exit 0.
  • packed nirium-mcp-0.6.3.tgz: 4 files, no *.test.* files
  • ok: nirium-mcp answered initialize as nirium-mcp-server 0.6.3 and exited 0
• The check, run inside a network namespace with no route out (npm from cache), passes: starting the bin needs no network.
• Broken-tarball cases, each exiting 1:
  • dist/ removed: tarball is missing dist/index.js
  • dist/index.test.js added: tarball ships test files: dist/index.test.js
  • bin that throws on start: bin exited (1) before answering initialize
  • bin that hangs: no initialize response in 20s
  • without the viem workaround: ERR_MODULE_NOT_FOUND: viem (the nirium-mcp needs viem installed by hand (missing peer of mppx, not covered by peerDependenciesMeta) #118 bug)
• actionlint 1.7.12 on mcp-ci.yml and sdk-test.yml: no findings.

Closes #144

[fernando-mendoza]

@Eras256 este PR resuelve #144 y está listo para revisión cuando tengas chance. Es independiente de los demás, así que lo puedes revisar en el orden que prefieras. ¡Gracias! Nota: incluye un workaround temporal para viem (#118) que se puede quitar cuando se mergee #124.