PulseAugur
EN
LIVE 12:18:38
Français(FR) Comment un connecteur personnalisé Claude trouve-t-il le serveur OAuth d'osFoundry, et pourquoi l'accès est-il vérifié à chaque appel ?

Claude and ChatGPT connectors use OAuth metadata for osFoundry authentication

The osFoundry platform's OAuth server provides metadata that custom connectors for AI models like Claude and ChatGPT can use to find the authorization and token endpoints. When a client attempts to call a tool without a valid token, the server responds with a 401 error containing a `resource_metadata` header. This header, compliant with RFC 9728, directs the client to the correct endpoints for authentication. The platform's design allows for dynamic client registration and uses PKCE for authorization code verification, ensuring that access is checked at each call to maintain security. AI

IMPACT Explains how AI connectors discover and authenticate with external services, crucial for integrating AI agents into broader workflows.

RANK_REASON The article details how specific AI tools (Claude, ChatGPT) interact with a platform's (osFoundry) authentication mechanisms, providing technical implementation details.

Read on dev.to — MCP tag →

AI-generated summary · Google Gemini · from 8 sources. How we write summaries →

Claude and ChatGPT connectors use OAuth metadata for osFoundry authentication

How we ranked this

Signal score
27 / 100
Composite score across the factors below. Higher = stronger signal that this story matters right now.
Newsworthiness bucket
Tool
The article details how specific AI tools (Claude, ChatGPT) interact with a platform's (osFoundry) authentication mechanisms, providing technical implementation details.
Source corroboration
8 independent sources
Strong cross-source corroboration — multiple independent publishers covered this within the clustering window.
Topics
product, infra
Editorial topic classification. Feeds into how the story surfaces on /topic/<slug> hub pages and into the per-entity coverage mix.
AI-industry relevance
High
Clearly on-topic for AI-industry coverage.
Story freshness
Breaking (< 6h)
Fresh story with cross-source coverage still developing. Ranking may shift as more sources report.

Full methodology in our editorial standards.

COVERAGE [8]

  1. dev.to — MCP tag TIER_1 中文(ZH) · BBT ·

    How does Claude custom connector find osFoundry's OAuth server and why does it check access permissions on every call?

    <p>遠端 MCP client 在沒有 token 的情況下呼叫 <a href="https://osfoundry.io/zh" rel="noopener noreferrer">osFoundry</a> 的工具時,會拿到下面這個回應。這個請求是 2026-11-06 在東京用一台 Mac 透過 curl 送出的:<br /> </p> <div class="highlight js-code-highlight"> <pre class="highlight plaintext"><code>$ curl -s -D - -X POST h…

  2. dev.to — MCP tag TIER_1 한국어(KO) · BBT ·

    How does Claude custom connector find osFoundry's OAuth and why does it check permissions every time?

    <p>토큰 없이 <a href="https://osfoundry.io/ko" rel="noopener noreferrer">osFoundry</a>의 원격 MCP 서버에 tool을 호출하면 이런 응답이 온다. 2026-11-06에 도쿄에 있는 Mac에서 curl로 직접 찔러 본 결과다.<br /> </p> <div class="highlight js-code-highlight"> <pre class="highlight plaintext"><code>$ curl -s -D - -X POST http…

  3. dev.to — MCP tag TIER_1 Bahasa(ID) · BBT ·

    How does the Claude custom connector find the osFoundry OAuth server, and why is access checked on every call?

    <p>Ini yang diterima client MCP remote saat memanggil tool <a href="https://osfoundry.io/id" rel="noopener noreferrer">osFoundry</a> tanpa token. Request-nya dikirim dengan curl dari sebuah Mac di Tokyo pada 2026-11-06:<br /> </p> <div class="highlight js-code-highlight"> <pre cl…

  4. dev.to — MCP tag TIER_1 Italiano(IT) · BBT ·

    How does a custom Claude connector find the osFoundry OAuth server, and why is access checked on every call?

    <p>Ecco cosa riceve un client MCP remoto quando chiama uno strumento di <a href="https://osfoundry.io/it" rel="noopener noreferrer">osFoundry</a> senza token. La richiesta è stata inviata con curl da un Mac a Tokyo il 2026-11-06:<br /> </p> <div class="highlight js-code-highlight…

  5. dev.to — MCP tag TIER_1 Français(FR) · BBT ·

    How does a custom Claude connector find the osFoundry OAuth server, and why is access verified on every call?

    <p>Voici ce que reçoit un client MCP distant quand il appelle un outil d'<a href="https://osfoundry.io/fr" rel="noopener noreferrer">osFoundry</a> sans jeton. La requête a été envoyée avec curl depuis un Mac à Tokyo le 2026-11-06 :<br /> </p> <div class="highlight js-code-highlig…

  6. dev.to — MCP tag TIER_1 Deutsch(DE) · BBT ·

    How does a Claude Custom Connector find the osFoundry OAuth server, and why is access checked on every call?

    <p>Das bekommt ein Remote-MCP-Client zurück, wenn er ein Tool von <a href="https://osfoundry.io/de" rel="noopener noreferrer">osFoundry</a> ohne Token aufruft. Die Anfrage wurde am 2026-11-06 mit curl von einem Mac in Tokio geschickt:<br /> </p> <div class="highlight js-code-high…

  7. dev.to — MCP tag TIER_1 Español(ES) · BBT ·

    How does Claude's custom connector find the osFoundry OAuth server and why is access checked on every call?

    <p>Esto es lo que recibe un cliente MCP remoto cuando llama a una herramienta de <a href="https://osfoundry.io/es" rel="noopener noreferrer">osFoundry</a> sin token. La petición se hizo con curl desde un Mac en Tokio el 2026-11-06:<br /> </p> <div class="highlight js-code-highlig…

  8. dev.to — MCP tag TIER_1 English(EN) · BBT ·

    How does a Claude custom connector find osFoundry's OAuth server, and why is access checked on every call?

    <p>This is what a remote MCP client gets when it calls an <a href="https://osfoundry.io" rel="noopener noreferrer">osFoundry</a> tool without a token. The request was sent with curl from a Mac in Tokyo on 2026-11-06:<br /> </p> <div class="highlight js-code-highlight"> <pre class…