Skip to main content

First MCP Certification Arrives as EU Rules Make Agent Costs Auditable

Ilustrační obrázek
The Model Context Protocol now has a certificate. During the week of September 18, the Agentic AI Foundation opened MCPA — the Model Context Protocol Associate, a 120-minute proctored exam covering MCP architecture, security, governance and execution, and the first vendor-neutral credential aimed at the people who actually wire agents together. In the same seven days, Cisco introduced real-time AI cost attribution and forecasting, OpenText and Cohere pushed agentic models into sovereign and air-gapped clouds, and Europe's AI transparency obligations kept running in the background. The certificate is the least interesting part. The interesting part is that the industry finally started agreeing on what "an agent that works" is supposed to mean.

What the Agentic AI Foundation actually shipped

The weekly enterprise AI roundup from Solutions Review lists the certification alongside a pile of other agentic announcements, and the framing matters. For roughly a year, "supports MCP" has been a marketing checkbox: every vendor has a connector page, and almost nobody documents what happens when a tool call fails halfway through a transaction.

A vendor-neutral exam on architecture, security, governance and execution is a small thing, but it's the first attempt to define a baseline competence that isn't tied to one cloud. If you have ever debugged an agent that cheerfully hallucinated a customer's order status because a tool returned HTTP 200 with an error body, you know why execution deserves its own section.

Is a certificate proof of competence? No. We've watched enough vendor certifications become a PDF you attach to a procurement file. But it does give European integrators something they currently lack: a shared vocabulary when writing statements of work for agent projects, instead of arguing about what "production-ready MCP" means on every engagement.

Tokenomics: your agent finally has a meter

Cisco expanded Splunk AI into private and air-gapped environments via an AI POD built with NVIDIA, and shipped real-time AI cost attribution and forecasting features — "Tokenomics" in the company's own framing. Abacus, meanwhile, launched an initiative aimed at regulated industries trying to drag AI projects out of pilot purgatory, and Airrived added Agentic Observability to its Agentic OS, tracing agent ownership, PII movement, policy compliance and consumption cost.

Read those three together and a pattern appears: the industry is no longer selling agents, it's selling control surfaces for agents. That is a healthy sign. It's also an admission that the first wave of deployments went badly.

What a million agent tokens actually costs

Cost attribution only makes sense if you know the underlying price per token, so let's do the arithmetic on an illustrative agent workload — an internal assistant that burns 10 million input tokens and 2 million output tokens per month. That's not extreme: tool definitions, retrieved context and conversation history all land in the input column, and agents resend them constantly. The prices below are drawn from the provider pricing pages as published on 18 September 2026.

ModelInput / 1M tokensOutput / 1M tokensMonthly cost (10M in / 2M out)
GLM-5.3-Flash$0.15$0.50$2.50 (≈ €2.30)
GLM-5.3$1.40$4.40$22.80 (≈ €21.00)
Gemini 3.8 Flash*$1.50$7.50$30.00 (≈ €27.60)

*Google's published rate for Gemini 3.8 Flash moves to $1.50 / $7.50 per million tokens on January 1, 2027; until then an introductory rate applies. EUR figures are approximate conversions at roughly €0.92 per dollar and will shift with the exchange rate. GLM prices reflect Zhipu AI's published pricing page and Gemini prices reflect Google's Gemini API pricing page, both retrieved on 18 September 2026.

An order-of-magnitude spread sits between the cheapest and the most expensive line here for functionally comparable routing-level work. That's why cost attribution became a product category in 2026: at ten million tokens a month the difference is lunch money, but agents retry, re-plan and fan out across sub-agents. Multiply by an order of magnitude and the cheap model is a headcount decision. DeepSeek's official API pricing page, retrieved on 18 September 2026, lists a 50% off-peak discount — schedule the batch work, pay half.

We keep that discipline in AI Arena, our benchmarking rig on an RTX 5060 Ti 16 GB: tokens per second and time-to-first-token are only half the story if you never count the tokens the agent resends on every loop.

Sovereignty, air gaps and the European angle

The genuinely relevant item for European readers, as reported in the same weekly roundup, is OpenText integrating Cohere's North agentic model suites into its Aviator AI agents for sovereign, private and hybrid cloud deployments. Together with Cisco's air-gapped Splunk AI POD, this is the first wave of agent infrastructure designed for customers who cannot send telemetry across an ocean.

That is the market EU banks, insurers, hospitals and public administrations live in. If your data residency requirement says "stays in the EU", a cloud-only agent platform with US-based inference may be difficult to square with your obligations — but the actual answer varies by organisation and contract, and is not a blanket ban. Sovereign deployment options change the answer from no to maybe — which, in regulated European IT, is a large step.

Europe's rules didn't wait for the conference circuit

Here is the part vendors gloss over. Mandatory transparency rules under Article 50 of the EU AI Act are in force as of 2 August 2026, but they are not one blanket requirement. Systems intended to interact directly with people — chatbots, for example — must be designed so that users are told they are interacting with an AI system unless that is obvious. Separately, providers of generative-AI systems that generate synthetic audio, image, video or text must mark the output in a machine-readable format. Neither obligation automatically covers every internal agent or every general-purpose-AI output; applicability depends on the system and the use case. General-purpose AI provider obligations have been legally binding since August 2025, with active enforcement by the EU AI Office since August 2026.

Practically, that means an agent deployed in the EU now needs to answer questions its pilot never asked: can you log which agent produced this output, which tools it called, what personal data moved, and can you label the result? Airrived's tracing features and Cisco's cost attribution and forecasting sound like optimisation tools. In a European procurement, they're closer to compliance evidence.

One useful piece of breathing room: the AI Omnibus simplification regulation enacted in mid-2026 moved the Annex III high-risk compliance deadline from 2 August 2026 to 2 December 2027. If you are building a high-risk system — credit scoring, recruitment, critical infrastructure — that is roughly 16 months of additional runway. It is not permission to ignore Article 50, which applies now.

The pilot-to-production gap, measured

A Collibra survey of 306 decision-makers, cited in the same roundup, gives the unvarnished numbers: 72% blame weak data foundations for underperforming AI initiatives, 76% hit critical roadblocks moving agent programmes from pilot to production, 87% regularly re-verify agent context, and 51% spend significant staff time correcting agent output before it ships. A separate Acquia survey of 500 executives found only 41% of CMOs feel confident embedding AI governance.

According to the same weekly roundup, Factory raised $200 million at a $5 billion valuation — more than triple its $1.5 billion valuation from April — pushing total funding past $400 million. Capital is flowing to the layer that promises to make agents deterministic. Whether that promise holds is the open question of the next two quarters, not of this week's headline.

What to do on Monday

If you run agents in Europe, three things are worth doing before you evaluate another platform. Instrument token spend per workflow, not per API key — you cannot optimise what you bill in aggregate. Write down, in one page, which agent produced which output and where that data sits, because Article 50 questions arrive from legal before they arrive from engineering. And treat certification schemes like MCPA as a hiring signal, not a compliance shield.

Do I need MCPA certification to deploy MCP servers?

No. Nothing in the Agentic AI Foundation's announcement makes the credential a legal or technical requirement, and MCP itself remains an open protocol. It is a skills benchmark — useful when hiring, vetting integrators, or standardising an internal engineering ladder across teams that currently disagree on what "production-grade MCP" means.

Does Article 50 of the EU AI Act apply to my internal agent tooling?

Article 50 is a transparency obligation, not a blanket ban, and its practical reach depends on what the system does and who interacts with it. Chatbots that users talk to directly must disclose that they are AI, and providers of generative-AI systems must machine-readable mark synthetic outputs where the rules apply. Internal tools that never expose output to end users sit in a different position than a customer-facing assistant — which is exactly the assessment your legal team should document rather than assume.

Why does off-peak API pricing matter for agents?

Because agents generate far more tokens than chatbots. Retries, planning steps and multi-tool loops multiply input tokens quickly, so a 50% off-peak discount on batch-eligible workloads can outweigh a model's headline quality advantage for non-interactive tasks like overnight document processing or bulk classification.

Discussion

No comments yet — be the first to share your thoughts.
X

Don't miss out!

Subscribe for the latest news and updates.