--- title: "Outlit MCP server | Agent MCP Directory" description: "Outlit: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/outlit-ai site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Outlit MCP server | Agent MCP Directory > Outlit: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/outlit-ai Site: Agent MCP Directory Last reviewed: 2026-11-05 # Outlit: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Outlit at mcp.outlit.ai answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Outlit | | --- | --- | | Domain | outlit.ai | | Category | Developer Tools (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | 85, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for outlit.ai, a vendor-published score) | | Company found through | Ora's public leaderboard | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.outlit.ai/mcp | | --- | --- | | How it was found | listed in Ora's public leaderboard | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:03 UTC | | Handshake time | 1,012 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:58:46Z https://mcp.outlit.ai/mcp sent initialize result auth-required (HTTP 401) 1788 ms - 20:03:55Z https://mcp.outlit.ai/mcp sent initialize result auth-required (HTTP 401) 1012 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer error="invalid_token", error_description="Outlit MCP requires an Authorization: Bearer token. Use the workspace MCP URL and complete OAuth in your MCP client. Legacy or headless clients that do not support OAuth must send their configured bearer credential.", resource_metadata="https://mcp.outlit.ai/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.outlit.ai | | Authorization server metadata | clerk.outlit.ai | | Registration endpoint | https://clerk.outlit.ai/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.outlit.ai/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.outlit.ai/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://clerk.outlit.ai/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Outlit. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | Found: docs.outlit.ai (JSON, via a direct request). | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Not found (the crawl got a non-200 answer). | | A2A agent card | Found: outlit.ai/.well-known/agent-card.json answered with a valid document in the shared crawl. | | A2A agent card (older path) | Found: outlit.ai/.well-known/agent.json answered with a valid document in the shared crawl. | | agents.json | Not found (the crawl got a non-200 answer). | | OAuth authorization server metadata | Not found (the crawl got a non-200 answer). | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: ai.outlit/outlit | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/outlit-ai/index.md) ## Sources - [Ora score page for outlit.ai](https://ora.ai/score/outlit.ai?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 1 November 2026, read from GET /api/leaderboard) - [Where Outlit was found](https://registry.modelcontextprotocol.io/v0/servers?search=ai.outlit%2Foutlit), read 4 November 2026 - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=outlit), read 4 November 2026 - [Outlit website](https://outlit.ai), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026