Announcing CIMD Support for MCP
Blog post from PropelAuth
PropelAuth has added support for Client ID Metadata Documents (CIMD), the MCP authorization specification’s recommended alternative to Dynamic Client Registration (DCR). CIMD lets AI clients identify themselves through a URL-hosted JSON metadata document containing details such as the client name, redirect URIs, grant types, and authentication method, allowing PropelAuth to validate the client’s identity and requested redirect URI without requiring pre-registration or an Allowed MCP Clients entry. This approach addresses DCR’s limitation of allowing unverified clients to create authorization-server records, while preserving automatic, low-friction client setup. PropelAuth advertises CIMD support through its authorization server metadata and continues to support manual client creation and DCR for compatibility with older clients. Administrators can enable CIMD with a dashboard toggle, while scopes, sessions, token introspection, and audit logging continue to function as they do for other MCP OAuth clients.
| Trend | Post Mentions | Total Month Mentions | Posts | Companies | MoM |
|---|---|---|---|---|---|
| MCP | 18 | 2,241 | 148 | 72 | -74% |
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.