Hi community,
Thanks a lot for sharing your support for the UTCP launch. Since our goal behind the UTCP (in addition to the technical elegance) is that no single organization should have any control over the protocol that governs agent tool calling, therefore the main contributors behind UTCP don't belong to a single company or country, for that matter.
To make it even more grassroots and community-driven, we've also launched a RFC (Request for Comments). Please check it out, and let's collectively build a kickass protocol for agent tool calling:
https://www.utcp.io/RFC
Also, if you'd like to contribute, please reach out. Or just drop a on the GitHub to keep the flywheel going.
https://github.com/universal-too...
Without wrapper-driven standardization, how do you plan to prevent integration fragmentation that could hurt interoperability between tools?
UTCP
@vouchy we believe that communication transport layers have already been standardized enough (e.g, HTTP, gRPC), so we can just leverage the existing ones instead of creating a new transport standard (MCP)
In a nutshell, UTCP leverages the interoperability of current standards, while MCP requires an ecosystem-wide rebuild :)
I read about security issues in MCP, hope UTCP would focus on that, can give them edge (Similar to HTTPS came for web)
UTCP
@admiralrohan Absolutely, the idea is that by using the native endpoint, we leverage the existing security authentication, instead of needing to reimplement everything again and adding more moving parts