UTCP
The scalable, secure alternative to MCP for tool calling
Start new thread
Zac Zuo

UTCP - The open, direct alternative to MCP for tool calling

by
Flowtica Scribe
•
UTCP (Universal Tool Calling Protocol) is an open standard for AI agents to call tools directly, positioned as a lightweight alternative to MCP. It eliminates the "wrapper tax" for lower latency by using a simple JSON manifest to connect to native APIs.

Add a comment

Replies

Best
Zac Zuo
Hunter
📌
Hi everyone! In the world of AI agents, the Model Context Protocol (MCP) has quickly become the dominant, industry-backed standard for tool calling. But a new, community-driven challenger has emerged with a completely different philosophy: the Universal Tool Calling Protocol (UTCP). UTCP's approach is all about direct connection. Instead of requiring a wrapper server like MCP, it lets an agent call a tool's native endpoint (like a REST API) directly. This means lower latency, no "wrapper tax," and you can reuse all your existing security and auth. While UTCP is still in its early days and doesn't have MCP's massive ecosystem backing, I don't expect it to challenge that dominance overnight. But sometimes the opposite of a good strategy is also a good strategy. I believe UTCP has the potential to grow a new ecosystem. After all, change, innovation, and competition are what ultimately make everything better.
Van de Vouchy

Without wrapper-driven standardization, how do you plan to prevent integration fragmentation that could hurt interoperability between tools?

Juan Viera Garcia
Maker

@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 :)

Joey Judd

Cutting out that "wrapper tax" with just a simple JSON manifest? That’s honestly genius, fr. Been waiting for something like this—props to the team!

Chris Messina

@juan_viera_garcia1 @aliraza36580 why not move your UTCP discovery endpoint to ‎`/.well-known` since .well-known URI path is a special directory defined by the IETF in RFC 5785. It allows web services to expose information or configuration files in a predictable, standardized location.

Juan Viera Garcia
Maker

@chrismessina Chris that’s a great idea actually! Appreciate it

Juan Viera Garcia
Maker

@chrismessina created a ticket (link) 💪

Juan Viera Garcia
Maker

What do you think, is it possible to create a popular protocol that rivals MCP?

Chris Messina

@juan_viera_garcia1 highly unlikely unless you 1) have a load of funding or 2) get one of the major labs to support it.

That's how we got OAuth adopted — a bunch of scrappy upstarts got together to define the protocol and then once Google came onboard, that gave it the legitimacy and visibility it needed to take off.

Juan Viera Garcia
Maker

@chrismessina Hi Chris, totally agree

That's why we're proactively reaching out to the major labs to find a collaboration together

However, if you know anyone that might be a good lead, would be great to connect!

Ali Raza
Maker

@chrismessina read how DeWitt Clinton came aboard the OAuth project, and then you developed it very closely with the Google team. Was this something planned from your side, or serendipity? And if you could draw parallels, what could be a good strategy to go down the same path with UTCP?

Chris Messina

@aliraza36580 primarily serendipity... just as I did with the hashtag, I did a lot of ground work to lay the foundation by soliciting lots of feedback, input, and trial and error improvements so that by the time Google came along (and to be fair Dewitt was already active in the OSS community), we'd already established our goals, had rough consensus and running code.

We also took care to license OAuth using a framework that could be adopted by the major platforms: the OWFa 1.0 Agreement.

Ali Raza
Maker

@chrismessina thanks for sharing Chris! We're definitely focusing on the groundwork and working very closely with the community to shape UTCP, let's see where serendipity takes it.

Nader Ikladious

This sounds like a solid move toward more open, efficient tool integration for AI agents. Love the focus on reducing wrapper overhead. Looking forward to trying it out when I can. Congrats on the launch 🚀

Rachit Magon

Appreciate the fresh perspective UTCP brings with direct API calls. How do you see it handling security concerns compared to MCP’s wrapper server approach? @aliraza36580

Ali Raza
Maker

@rachitmagon Thanks! UTCP leverages the tool’s native, battle-tested security and is thus able to call any tool while guaranteeing the same security as if the tool was called by a human.

MCP, on the other hand, introduces a security tax by requiring authentication and authorization to be re-implemented and managed at the MCP layer. This is not scalable and introduces a lot of new attack vectors.

Rachit Magon

@aliraza36580 Got it, appreciate the breakdown.

Pulkit Garg

UTCP.io seems like an elegant solution love how it centralizes team communications with secure, customizable workspaces. Quick question are you planning to add integrations with popular project management tools like Jira or Trello to streamline workflows even further?

Juan Viera Garcia
Maker
Samanvaya Pant

Open API alternatives are critical. What’s your approach to keeping the tool-calling secure?

Alexandru Comanescu

This is amazing! I never understood why MCP as a protocol needs an extra server when your actual server already has an API layer.