District MCP Server

MCP detected 2026-10-12

Details

Endpoint: https://mcp-server.district.in/mcp
Transport: streamable-http
Docs: https://district.in/llms.txt

Authentication

District MCP OAuth client/session oauth2 discovered Set up OAuth ↗

OAuth · resolves from well-known metadata

Use an MCP client that supports OAuth and Dynamic Client Registration against District's MCP server. The client can discover District's OAuth metadata at oauth-authorization-server metadata, register itself automatically via the listed registration_endpoint, then send you to District's consent flow and store the resulting access token. As OIDC metadata is also published at openid-configuration, the user-facing step is just approving access in the browser.