FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

SEP-2351: Explicitly specify RFC 8414 well-known URI suffix for MCP by dend · Pull Request #2351 · modelcontextprotocol/modelcontextprotocol · GitHub

  1. modelcontextprotocol
  2. modelcontextprotocol

Repository navigation

SEP-2351: Explicitly specify RFC 8414 well-known URI suffix for MCP - #2351

Merged
mcp-commander[bot] merged 1 commit into
mainfrom
den/rfc-8414
Mar 28, 2026
ConversationCommits (1)ChecksFiles changed
Merged

SEP-2351: Explicitly specify RFC 8414 well-known URI suffix for MCP#2351
mcp-commander[bot] merged 1 commit into
mainfrom
den/rfc-8414

Conversation

dend commented Mar 4, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Summary

  • Explicitly state that MCP uses the default oauth-authorization-server well-known URI suffix defined in RFC 8414 Section 3.1, satisfying the RFC's requirement that applications specify their well-known URI suffix
  • Clarify that MCP does not define an application-specific well-known URI suffix

Fixes #1650

Test plan

  • Verify the draft spec renders correctly with npm run serve:docs
  • Confirm no new broken links introduced by changes

🤖 Generated with Claude Code

docs: explicitly specify RFC 8414 well-known URI suffix for MCP
fd43957 
Clarify that MCP uses the default oauth-authorization-server
well-known URI suffix per RFC 8414 Section 3.1, satisfying the
RFC requirement that applications specify their well-known URI
suffix. MCP does not define an application-specific suffix.

Fixes #1650
dend requested a review from a team as a code owner March 4, 2026 21:58
dend changed the title docs: explicitly specify RFC 8414 well-known URI suffix for MCP SEP-2351: Explicitly specify RFC 8414 well-known URI suffix for MCP Mar 4, 2026
dend self-assigned this Mar 4, 2026
dend mentioned this pull request Mar 4, 2026
Closed
dend added this to the 2026-06-30-RC milestone Mar 4, 2026
dend added SEP draft SEP proposal with a sponsor. labels Mar 4, 2026
dend moved this to In Review in SEP Review Pipeline Mar 4, 2026
pcarleton reviewed Mar 5, 2026
View reviewed changes

pcarleton left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

This is a pretty minor change, so seems fine, but in practice is this holding anyone back?

joshrotenberg mentioned this pull request Mar 5, 2026
Closed
wdawson reviewed Mar 6, 2026
View reviewed changes

wdawson left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

LGTM

sep-automation-bot Bot commented Mar 23, 2026

Copy link
Copy Markdown

Maintainer Activity Check

Hi @dend!

You're assigned to this SEP but there hasn't been any activity from you in 18 days.

Please provide an update on:

  • Current status of your review/work
  • Any blockers or concerns
  • Expected timeline for next steps

If you're no longer able to sponsor this SEP, please let us know so we can find another maintainer.

This is an automated message from the SEP lifecycle bot.

localden commented Mar 28, 2026

Copy link
Copy Markdown
Contributor

/lgtm force

SEP approved by Core Maintainer vote.

mcp-commander Bot added accepted SEP accepted by core maintainers, but still requires final wording and reference implementation. and removed draft SEP proposal with a sponsor. labels Mar 28, 2026
mcp-commander Bot moved this from In Review to Accepted in SEP Review Pipeline Mar 28, 2026
mcp-commander Bot approved these changes Mar 28, 2026
View reviewed changes

mcp-commander Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

Approved on behalf of @localden via /lgtm force.

mcp-commander Bot enabled auto-merge (squash) March 28, 2026 01:43
mcp-commander Bot merged commit 298498d into main Mar 28, 2026
21 checks passed
mcp-commander Bot deleted the den/rfc-8414 branch March 28, 2026 01:43
mcp-virtual-tpm Bot modified the milestone: 2026-06-30-RC Apr 17, 2026
localden assigned localden and unassigned dend Apr 27, 2026
mikekistler mentioned this pull request Apr 30, 2026
Closed
20 of 22 tasks
This was referenced Sep 9, 2026
Closed
Merged
Closed
Closed
Open
Merged
Closed
Open
This was referenced Sep 16, 2026
Open
Closed
Merged
ump45nose mentioned this pull request Sep 18, 2026
Closed
This was referenced Sep 19, 2026
Closed
Closed
Closed
Open
Merged
Merged
Closed
Open
This was referenced Sep 27, 2026
Closed
Closed
Open
Closed
Closed
Closed
Open
Open
Open
dependabot Bot mentioned this pull request Oct 7, 2026
Open

This branch was successfully deployed

1 active deployment
staging - docs — fd439575 Deployed Mar 4, 2026 by mintlify[bot]
View deployment
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
Show hidden characters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

pcarleton pcarleton left review comments
mcp-commander[bot] mcp-commander[bot] approved these changes
+1 more reviewer
wdawson wdawson left review comments
Reviewers whose approvals may not affect merge requirements

Assignees

localden

Labels

auth final SEP finalized. security SEP

Projects

2026-07-28 Spec Implementation
Status: Done
SEP Review Pipeline
Status: Final

Milestone

2026-07-28-RC

Development

Successfully merging this pull request may close these issues.

MCP doesn't sufficiently specify its integration with RFC 8414

4 participants

Back | FazBrowse Home | New Git URL