Guide · Updated weekly · 5 min read
Public MCP server examples you can try today
Direct answer: The fastest way to learn MCP is to connect to a real server. A handful are public (no auth) and safe to explore — docs and knowledge servers. Most production servers (Notion, Linear, Sentry, Stripe, GitHub) are also remote MCP servers but sit behind OAuth. Below are live-scored public examples, pulled from our weekly index.
Public, no-auth servers (great for learning)
These respond to an anonymous initialize handshake — paste any into the scanner or your MCP client:
Scores update weekly via the Public MCP Server Index. Want your server listed? Scan it.
Popular servers that require auth
These are remote MCP servers too, but you connect through OAuth with an account — you won't get an anonymous handshake:
| Server | What it does |
|---|
| Notion | Read/query your Notion workspace |
| Linear | Issues, projects, cycles |
| Sentry | Errors, issues, releases |
| Stripe | Payments, customers, invoices |
| GitHub | Repos, issues, PRs, actions |
A server requiring auth is a good sign for anything that touches private data — see the conformance checklist, step 9.
How to connect
- Add the HTTPS endpoint to your MCP client (Claude, Cursor, an agent framework) as a streamable-HTTP server.
- The client runs
initialize then tools/list to discover tools.
- Authenticated servers redirect you through OAuth first.
Building your own? Test it first.
Real handshake, conformance score, latency — free, 10 seconds.
Scan my server →