Using XMPP for the implementation of thing registries has several benefits: it allows for ad hoc connections and real-time communication between peers, regardless of obstacles in the network topology imposed by firewalls. It automatically forwards the network identity of all actors in the network in a way that cannot be spoofed easily. It is also federated, which makes it globally scalable and avoids the creation of centralized bottlenecks. While Thing Registries imply some form of centralization, at least of the bulletin board, the federated aspect of XMPP allows anybody to create their own bulletin boards (registries).

There is also an open extension available for Thing Registries in XMPP. It is defined in XEP-0347. It also defines a mechanism for publishing thing registries: they are made available as components on the XMPP server. A thing, controller, or the owner using a custom XMPP client can automatically detect the registry by browsing available components on its broker. If participants use the same broker, they will automatically find the same registry, regardless of where they are located on the internet, and can, therefore, use it to exchange identities securely. It also allows for the use of Thing Registries to be reachable at other locations.