Skip to content

Harden agent checks and prepare reproducible deployment - #2

Merged
Mabolla merged 1 commit into
mainfrom
fix/agent-release-readiness
Oct 1, 2026
Merged

Mabolla merged 1 commit into
mainfrom
fix/agent-release-readiness

Conversation

@Mabolla

@Mabolla Mabolla commented Oct 1, 2026

Copy link
Copy Markdown
Owner

Changes

  • Restrict the read-only MCP checker to unpaid GET requests and return explicit 405 responses for unsupported MCP transport methods.
  • Compare settlement attribution only with a caller-supplied Builder Code instead of silently using this project's code for other sellers.
  • Pin outbound connections to validated public DNS answers, reject non-public IPv4/IPv6 destinations, disable redirects, bound response bodies, and handle malformed status codes.
  • Add a runnable SDK client example and Railway Docker/health-check configuration; use npm ci in CI and Docker builds.
  • Record the observed Railway 404 honestly in the README; these changes do not claim an available public service.

Verification

  • npm run typecheck — passed
  • npm test — 25 passed, including real HTTP MCP and outbound transport regression coverage
  • npm run build — passed
  • node --check examples/agent-client.mjs — passed
  • git diff --check — passed

Deployment status

The previously configured Railway /health URL still returns HTTP 404 Application not found (2026-10-01). Existing hosting access was unavailable. No new integration was installed, no credentials were committed, and no payment was signed or broadcast.

@Mabolla
Mabolla merged commit 13cf331 into main Oct 1, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant