MCP Security and Compatibility#

Security properties that remain active while the customer tool runtime is unavailable.

Overview#

OAuth enforcement remains active even though the customer MCP tool runtime is not currently available.

Active Security Properties#

  • Protected requests require an accepted bearer token for the exact MCP resource.

  • Public clients use authorization code plus PKCE S256 and no client secret.

  • Dynamic registration accepts only approved exact callback forms.

  • Tokens, authorization codes, cookies, and PKCE verifiers must not be logged or shared.

  • Customer and employee systems remain separate; no internal registry is projected into this public status documentation.

Current Compatibility#

The Streamable HTTP route and OAuth metadata are active, but the protected runtime does not implement standard initialization or tool listing. There is no customer tool catalog or supported client setup yet.

Before a Client Is Supported#

A client setup will be published after one named version passes:

  1. discovery and exact resource selection;

  2. approved registration and PKCE browser authorization;

  3. MCP initialization and protocol negotiation;

  4. tool listing with only the approved customer catalog;

  5. a read-only call and its error path;

  6. token expiry or refresh behavior and disconnect;

  7. confirmation that no credential or private tool leaks into client logs.

An OAuth callback alone is not enough; the same test must reach tool discovery and a read-only call.