PulseAugur
EN
LIVE 19:39:28

MCP OAuth 2.1 bug hides server tools from directories

A bug in the MCP protocol's OAuth 2.1 implementation causes remote servers to appear as if they have no tools available, rendering them invisible to discovery directories. This issue arises because directory crawlers, which lack user accounts, receive a 401 Unauthorized response when attempting to access the `tools/list` endpoint, leading them to incorrectly report zero capabilities. The proposed solution involves separating public methods like `tools/list` from authenticated, credit-spending operations, ensuring that server capabilities are discoverable without requiring user authorization. AI

IMPACT This technical issue could hinder the adoption and integration of MCP-based tools by making them undiscoverable through standard directories.

RANK_REASON The item describes a technical bug and its solution within a specific software protocol (MCP), impacting its discoverability and functionality.

Read on dev.to — MCP tag →

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

MCP OAuth 2.1 bug hides server tools from directories

COVERAGE [1]

  1. dev.to — MCP tag TIER_1 English(EN) · Leo Kadieff ·

    If your MCP server uses OAuth, every directory thinks it has zero tools

    <p>We shipped a remote MCP server, registered it everywhere, and then noticed<br /> something odd: every directory listed it as having <strong>no tools at all</strong>.</p> <p>Not the wrong tools. Not a stale count. Zero.</p> <p>glama's API returned this:<br /> </p> <div class="h…