Skip to content

Grant permanent MCP Events subscriptions on explicit ttlMs null - #5

Merged
VeraPyuyi merged 3 commits into
mainfrom
feat/dot-permanent-subscription
Oct 23, 2026
Merged

VeraPyuyi merged 3 commits into
mainfrom
feat/dot-permanent-subscription

Conversation

@VeraPyuyi

Copy link
Copy Markdown
Owner

Per the official MCP Events contract, an explicit ttlMs: null requests a subscription without expiration; the server grants it and returns refreshBefore: null.

Permanence is a persisted flag with zero expiry; zero expiry alone never grants it. Omitted TTL keeps the one-hour default and numeric TTL keeps the 60s..24h range, so a numeric refresh downgrades a permanent grant. Delivery still requires enabled state and callback verification, and unsubscribe, revoke, disable, auth continuity changes and signing-secret replacement keep their existing invalidation rules. Event and bridge grants are intersected. Status reports an active permanent subscription with omitted dates.

Verified: RED then GREEN lifecycle, downgrade, HTTP-null and status tests; focused race; full go test -race ./... passed in 137.58s; vet, gofmt and diff checks clean.

@VeraPyuyi
VeraPyuyi marked this pull request as ready for review October 23, 2026 12:01
@VeraPyuyi
VeraPyuyi merged commit 3f169b8 into main Oct 23, 2026
5 of 6 checks 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