MCP Authorization with Dynamic Client Registration
In the previous series, we built the server side of the spec, leaving the client side up to the reader since obtaining OAuth clients is usually fairly opinionated in enterprise environments.The MCP Authorization spec actually has opinions about how MCP clients (and thus, OAuth clients) should be created. The idea behind the spec is to allow MCP clients and servers to be “plug and play” automatically. The process starts when an MCP client makes a request for a resource it is not authenticated for (HTTP 401).
- ▪In the previous series, we built the server side of the spec, leaving the client side up to the reader since obtaining OAuth clients is usually fairly opinionated in enterprise environments.The MCP Authorization spec actually has opinions a
- ▪The idea behind the spec is to allow MCP clients and servers to be “plug and play” automatically.
- ▪The process starts when an MCP client makes a request for a resource it is not authenticated for (HTTP 401).
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Christian Posta |
| Canonical URL | https://blog.christianposta.com/understanding-mcp-authorization-with-dynamic-client-registration/ |
| Publication time | Fri, 26 Jun 2026 06:41:40 +0000 |
| Retrieval time | 2026-06-26T07:07:29.748Z |
| Last seen | 2026-06-26T07:07:29.748Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | AjU5mAvVFq6O |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
MCP Authorization With Dynamic Client Registration Posted Jul 10, 2025 By Christian Posta 9 min read MCP Authorization With Dynamic Client Registration Contents MCP Authorization With Dynamic Client Registration This is a bonus post following on from my Understanding MCP Authorization three part series covering building (and understanding) an MCP HTTP based server and implementing the MCP Authorization spec (2025-06-18). In the previous series, we built the server side of the spec, leaving the client side up to the reader since obtaining OAuth clients is usually fairly opinionated in enterprise environments.The MCP Authorization spec actually has opinions about how MCP clients (and thus, OAuth clients) should be created.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Christian Posta.
Discussion
0 commentsMore from Christian Posta
