Skip to content

feat(mcp): supply a rotating signer credential to the gateway - #40

Open
eliteprox wants to merge 2 commits into
mainfrom
feat/signer-credential-provider
Open

feat(mcp): supply a rotating signer credential to the gateway#40
eliteprox wants to merge 2 commits into
mainfrom
feat/signer-credential-provider

Conversation

@eliteprox

Copy link
Copy Markdown
Collaborator

Summary

  • runInference builds one gateway per call with a signerHeaders provider backed by resolveSignerSession.
  • The first exchange is seeded so the provider does not mint twice on first use.
  • Drops the outer SignerRefreshRequired catch-and-rebuild. The library now rotates the bearer itself (expiry skew + HTTP 480).

Depends on @pymthouse/gateway-web@^0.4.0 (pymthouse/gateway-web#23 — number may differ). Merge after that package is published; pnpm-lock.yaml is left on the currently resolved version so CI does not pick up a file: path. After 0.4.0 is on npm, run pnpm update @pymthouse/gateway-web and land the lockfile.

Test plan

  • pnpm typecheck and pnpm lint against local gateway-web 0.4.0
  • Snyk Code: 0 issues on lib/mcp/gateway.ts

…tion source to inference requests

- Bumped the version of @pymthouse/gateway-web in package.json.
- Added attributionSource parameter to inference requests in gateway.ts.
- Introduced gatewayRequestId in mcp-server.ts for tracking requests.
- Updated Asset type in store.ts to include gatewayRequestId for better tracking.
Build one gateway per inference call with a signerHeaders provider
backed by resolveSignerSession, seeding the first exchange so we do
not mint twice. Drop the outer SignerRefreshRequired rebuild — the
library now refreshes the bearer itself.
@vercel

vercel Bot commented Sep 3, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
console Error Error Sep 3, 2026 5:14am UTC

Request Review

@eliteprox
eliteprox changed the base branch from feat/request-id to main September 9, 2026 15:56
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