COOCON joins AAIF to connect payments and MCP in AI agents

That payment companies start orbiting the MCP ecosystem is no accident: it signals that Anthropic's protocol has stopped being exclusive territory for tool developers and is beginning to attract sectors with real money on the table. Last Friday, June 12, News-Press NOW reported that COOCON, a South Korean fintech company specializing in financial data and payment processing, formally joined the AAIF (AI Agent Interoperability Foundation), a global foundation focused on standardizing AI agents.

What is AAIF and what role does COOCON play

AAIF is not an Anthropic project nor directly linked to the MCP specification, but it has adopted MCP as one of its reference standards for communication between agents and external tools. The foundation's stated objective is to enable agents from different providers to interoperate seamlessly: share context, invoke tools, and increasingly, execute economic transactions.

That's where COOCON comes in. The company brings two concrete assets to this equation: its infrastructure for scraping and aggregating financial data, widely used in Korea for bank account consolidation, and its ability to process payments on behalf of third parties. Within the AAIF framework, COOCON intends to expose both capabilities as MCP servers, so an agent can check balances, execute transfers, or verify financial identities directly from its execution context.

Why this matters for the MCP ecosystem

Until now, most published MCP servers solve productivity problems: web search, database access, calendar management, or SaaS API integration. The incorporation of a regulated financial sector player points to a different layer: agents that not only manage information but move money.

This raises several technical and governance questions that the ecosystem hasn't fully resolved. How are permissions modeled in an MCP server that can initiate a bank transfer? Who audits the chain of invocations when a sub-agent calls another that calls the payments server? Claude Code already supports hooks on events like `PreToolUse` and `PostToolUse`, which allows intercepting and validating tool calls before execution, but authorization logic for financial operations demands far more than a shell script.

Who this is relevant for

If you develop agents with Claude Code or integrate MCP servers into enterprise workflows, this news affects you in two ways:

• Short term: COOCON has announced plans to publish its capabilities as MCP servers accessible to AAIF members. If you work with clients in Asian markets or with Korean financial data requirements, it's worth tracking their roadmap.
• Medium term: COOCON's move is probably the first in a series. A fintech with regulatory experience deciding to structure its business around MCP validates the protocol beyond internal use in development tools.

What remains unclear is how AAIF plans to manage certification of MCP servers operating in regulated sectors. Publishing an MCP server that returns search results is one thing; publishing one that executes payments on behalf of an autonomous agent is another with legal implications in virtually any jurisdiction.

---

From our perspective, we see this as a signal of ecosystem maturity rather than a milestone in itself: that companies with financial compliance experience start speaking the language of MCP indicates the protocol no longer needs introduction. What it does urgently need is a clear framework for authorization and auditing of this type of integration.