Server Lazy Auth vs Everything
Side-by-side comparison of two Model Context Protocol servers. Pick the right one for Claude Desktop, Claude Code, or Cursor.
MCP App example demonstrating lazy (on-demand) OAuth: public tools work unauthenticated, protected tools return 401 + WWW-Authenticate so the host runs the OAut
Reference / test server with prompts, resources, and tools.
Comparison
| Feature | Server Lazy Auth | Everything |
|---|---|---|
| Pricing | Free | Free |
| Installs | — | — |
| Rating | — | — |
| Verified | ||
| Hosted | — | — |
| Tools | — | — |
| Category | development | development |
| Author | ochafik-ant | Community |
| Repo | modelcontextprotocol/ext-apps | modelcontextprotocol/servers |
When to pick Server Lazy Auth
MCP App example demonstrating lazy (on-demand) OAuth: public tools work unauthenticated, protected tools return 401 + WWW-Authenticate so the host runs the OAuth flow only when needed
When to pick Everything
Reference / test server with prompts, resources, and tools.
Looking for something else? Browse all MCPs or check trending this week.