Federated through External Registry

Publisher

Cisco Systems, Inc. (Webex for Developers)

URL

https://developer.webex.com/mcp/docs/federated-through-external-registry

Published

unknown

Updated

unknown

Accessed

2026-09-05

HTTP status

200

License

Cisco proprietary documentation, all rights reserved; no-redistribution; short excerpts and locators only

Claims citing this source

• Every one of the 22 federated servers is listed with the same authentication type, OAuth2 authorization code, without exception. fact in context
• Cisco states that federated through external registry servers are developed by third parties, imported from an external registry, not owned by Cisco, and that functionality issues should be raised with the developer. fact in context
• Federation through an external registry is populated and live, with no beta, preview or coming soon language on its documentation page and every listed server present in the public marketplace. inference in context
• The federated through external registry page lists 22 named third-party servers, covering search, scraping, document signature, product analytics, automation, calendar, workspace, payment, developer tooling, database and network monitoring products. fact in context

Cite this source record

APA

WarmTransfer. (2026, September 5). Federated through External Registry. WarmTransfer. https://warmtransfer.net/knowledge/sources/webex-dev-federated-external-registry

BibTeX

@misc{warmtransfer-webex-dev-federated-external-registry,
  title  = {Federated through External Registry},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/sources/webex-dev-federated-external-registry},
  note   = {Cisco Systems, Inc. (Webex for Developers), accessed 2026-09-05}
}