Search • Sprawl Radar • TrustOps • Gateway • Ledger • Mandates • Hosting • Agent Commerce • Docs Compiler • Demo • Trust Index • Discovery Sources • Submit Repo • GitHub Action • Plans • Intelligence API • Verified Profiles • Shortlists • Rankings • Compare • Badges • Claim • ChatGPT compatible • Claude compatible • Healthcare • Digests • RSS • RSS XML • Backfill • MCP API
OAUTH MCP
OAuth MCP server directory
Verify helps buyers separate OAuth presence from OAuth quality. Reports check protected-resource metadata, authorization-server discovery, DCR signals, and whether authenticated behavior is proven.
Last reviewed: Site version: v1.0.465
Why buyers use this page
OAuth presence is shown separately from authenticated validation evidence.
Policy exports can require OAuth and suppress stale evidence by default.
Gateway decisions can combine OAuth requirements with user mandate and payload risk.
Recommended workflow
Step 1
Browse servers advertising OAuth.
Step 2
Inspect discovery metadata and authenticated-session evidence.
Step 3
Require OAuth in exported policy or /v1/decide constraints.