The Protocol That Silicon Valley Called Broken Is the One BFSI Is Building On

In March 2026, Perplexity CTO Denis Yarats stood at the Ask 2026 developer conference and made an announcement . Perplexity, which had shipped its own MCP server just months earlier, was moving away from the Model Context Protocol. The reason was that MCP tool schemas were consuming up to 72% of the company's available context window space before the agent processed a single word of user input, according to the company. The authentication model, which requires each MCP server to manage its own credentials, added friction at every connection point. For a consumer AI product competing on speed and responsiveness, the overhead was indefensible. Within days, Y Combinator president Garry Tan offered a blunter verdict , describing MCP as something that "sucks honestly," and published an alternative CLI-based workflow. A protocol that had seemed unstoppable with 97 million monthly SDK downloads, adopted by OpenAI, Google, Microsoft, and AWS, donated to the Linux Foundation in December 2025, was suddenly a subject of serious criticism from some of the most credible voices in AI development. At the same time, in a less visible corner of the same technology landscape, a pattern of adoption had been building in financial services for months. Grasshopper Bank launched what was described as the first MCP server by a US financial institution in August 2025. Bud Financial followed in October. GoCardless launched in February 2026. Nymbus and Meow Technologies both launched in April. Every one of them chose MCP deliberately, for reasons that have nothing to do with context window efficiency What MCP Actually Is Anthropic released the Model Context Protocol in November 2024 as an open standard defining how AI agents connect to external tools, data sources, and business systems. Before MCP, connecting an AI model to any external system required a custom integration like bespoke code, authentication, and maintenance. The M times N integration problem : M models, N tools, and a different integration for each combination. MCP solves this by providing a single standardized connection layer. Any system that implements an MCP server can be connected to any AI agent with an MCP client. The promise is interoperability. Build it once and any compatible agent can use it. By early 2026 the standard had achieved broad adoption faster than almost any open protocol in recent memory. The criticism from Perplexity and Tan is not that MCP is conceptually wrong. It is that MCP's design, which requires the model to receive complete tool definitions, including parameter schemas and response formats, before it can use any tool, creates measurable overhead at the scale of production consumer deployments. One developer reported that seven MCP servers consumed 98,700 tokens, roughly a third of a 200,000-token context window, before any conversation began. For companies where context efficiency translates directly to cost and performance, that overhead compounds into a real operational problem. Why Choose the Same Protocol The adoption did not happen overnight. It built steadily, starting in the US before the Silicon Valley backlash had even formed. And at every step, the companies adopting MCP were explicit about what they were buying into — not speed, not simplicity, but accountability. Grasshopper Bank was the first . In August 2025, the digital bank serving startups and small businesses partnered with Narmi to launch what the two companies described as the first MCP server by a US financial institution. Grasshopper was explicit about why it chose MCP over a direct API approach: the protocol provides a standardised, auditable connection between the AI model and the bank's systems, with controlled access from the start. The server allows business clients to query financial data through Claude using natural language without custom integrations. The capability was secondary. The governance architecture was the point. Bud Financial made the same calculation from a different position. The New York-based AI platform for banking data launched its MCP server in October 2025 to give banks, credit unions, and fintechs access to enriched transaction data and customer financial intelligence. Bud built SOC2 Type 2 compliance directly into the architecture — not as a later addition, but as a design requirement. In banking data environments, compliance is not a feature. It is the product. GoCardless, a UK-based bank payment company, launched its MCP server in February 2026 to give developers and merchants a natural language interface to its payment platform. The company framed MCP not as a current convenience but as the technical foundation for agentic commerce, the infrastructure layer that will matter when AI agents begin executing payments autonomously, not just surfacing data. Nymbus made the governance case most explicitly. The US banking platform launched its MCP server in April 2026 with 19

The Protocol That Silicon Valley Called Broken Is the One BFSI Is Building On

Keep reading. It's free.

Related stories