Repository navigation
Conversation
MCP_MAX_PAYMENT_PRICE was declared twice, so dotenv applied the later "MCP agent spending limits" entry and the earlier "Ceiling per paid_call" comment described a line that never took effect. Both carried $1.00, so no configured value changes.
This was referenced Oct 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
.env.exampledeclaredMCP_MAX_PAYMENT_PRICE=twice: once beside the HTTP transport keys under the comment# Ceiling per paid_call, enforced by the x402 fetch wrapper., and once under--- MCP agent spending limits ---. A dotenv file applies the last declaration, so that first comment block was describing a line that never took effect. This removes the earlier comment + key.Both copies carried
$1.00, andexamples/mcp-server/run.tsreads the key once (process.env.MCP_MAX_PAYMENT_PRICE || '$1.00'), so no configured value and no behaviour changes. Nothing else refers to the removed line:README.md,examples/mcp-server/README.mdand the pending changesets all describe the surviving$1.00default.Split out of the rebase audit of #524 (review thread on #421): once #521 landed as
c55a980, this was the only work left on that branch.Related issue
None - config hygiene. Deliberately not claiming #421, whose test coverage is already on main via #521.
Type of change
Checklist
npx tsc --noEmitpasses - run on615e539: exit 0npm run buildpasses - run on615e539: exit 0src/__tests__/envDrift.test.ts(4 passed) asserts everyprocess.envread in source still appears uncommented in.env.example, which the surviving declaration satisfies..env.exampleis the only doc touched.No changeset: the effective configured value is unchanged, so there is nothing to say in a changelog.