# Application creation vira DCR from 3rd parties spam

**URL:** <https://community.auth0.com/t/application-creation-vira-dcr-from-3rd-parties-spam/197352>\
**Category:** Get Help\
**Tags:** apis, application\
**Created:** [February 17, 2026, 4:46pm UTC](https://community.auth0.com/t/application-creation-vira-dcr-from-3rd-parties-spam/197352 "2026-02-17T16:46:40Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![danderson](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/danderson/32/78461_2.png) [@danderson](https://community.auth0.com/u/danderson)\
**Post date:** [February 17, 2026, 4:46pm UTC](https://community.auth0.com/t/application-creation-vira-dcr-from-3rd-parties-spam/197352/1 "2026-02-17T16:46:40Z")

</div>

Hello

Im building a webapp that uses auth0 DCR to let third parties create applications allowing users to sign into my service through their page.

The problem is that every time a user logs in it creates a new app and I hit my allowed number of apps pretty fast.

It might be an issue with the host (claude.ai) handles client registration, but if anyone has any suggestions would be very excited to hear them.

---

<div class="post-metadata">

**Author:** ![gerald.czifra](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/gerald.czifra/32/75301_2.png) [@gerald.czifra](https://community.auth0.com/u/gerald.czifra)\
**Post date:** [February 17, 2026, 11:09pm UTC](https://community.auth0.com/t/application-creation-vira-dcr-from-3rd-parties-spam/197352/3 "2026-02-17T23:09:13Z")

</div>

Hi @danderson

Welcome to the Auth0 Community!

I believe the reason why a new application is created each time a user logs could be because your application is calling the [Dynamic Client Registration](https://auth0.com/docs/get-started/applications/dynamic-client-registration) endpoint ( `oidc/register` ) on each login. This endpoint is designed to create a new application each time it is called.

My recommendation is to store and reuse the `client_id` and `client_secret` from each third-party application after it’s initial registration. This way, when a login attempt is made from the same third-party app, your system should retrieve the stored `client_id` and `client_secret` from your database and use them for the authentication flow, rather than calling the DCR endpoint again.

Allow me to share some documentations that outline some additional information on this matter:

- [Dynamic Client Registration and Quota](https://community.auth0.com/t/dynamic-client-registration-and-quota/100969);
- [Dynamic Client Registration (DCR) Tagging](https://community.auth0.com/t/dynamic-client-registration-dcr-tagging/190318);
- [Model Context Protocol (MCP) Common Questions](https://support.auth0.com/center/s/article/Model-Context-Protocol-MCP-Common-Questions).

In addition to this, I cannot confirm that it’s directly related, but I was able to find the following [bug reported on GitHub](https://github.com/anthropics/claude-ai-mcp/issues/5) regarding Claude Desktop that breaks custom OAuth Connectors. Sharing it in case this might be related and to provide visibility.

Hope this helped!  
Gerald

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [March 3, 2026, 11:09pm UTC](https://community.auth0.com/t/application-creation-vira-dcr-from-3rd-parties-spam/197352/4 "2026-03-03T23:09:17Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
