What Is the Model Context Protocol Associate Exam?

The Model Context Protocol Associate exam, code MCPA, is the Linux Foundation’s associate level credential for the protocol that connects language models to external tools and data. It is a 120 minute online proctored multiple choice exam covering five weighted domains: MCP fundamentals, architecture and components, interactions and execution, security and governance, and use cases and ecosystem.

The protocol itself is the reason the credential exists. Before MCP, every integration between a model and a system was bespoke, which meant an organisation ended up with as many connection styles as it had tools. MCP replaces that with one message format and one set of roles, so a tool built once can be used by any host that speaks the protocol.

The exam is written at the level of someone who has to make that work in practice rather than someone building the protocol itself. It asks what a tool invocation looks like, what happens when one fails, where the trust boundary sits, and who consented to what. Those are integration questions, not research questions.

Which Version of the Spec Does the Exam Follow?

The Model Context Protocol is published as dated revisions rather than numbered releases, and the current revision at the time of writing is 2026-07-28. The Linux Foundation does not pin the MCPA exam to a single dated revision in its published exam information, so the practical guidance is to study the current specification and expect the durable concepts rather than edge case details.

That is less troubling than it sounds, because the five domain names describe structural ideas rather than syntax. Hosts, clients and servers, tool invocation, error handling, trust boundaries and consent are all concepts that survive a revision. What changes between dated revisions tends to be the precise shape of a message or the addition of a capability, and an associate level exam is not the place for that.

The specification is published openly at the dated MCP specification, and the work happens in public on the project repository. Reading a recent set of changes there is the fastest way to see which parts of the protocol are settled and which are still moving.

The certification is valid for two years, which is a sensible match for a standard on this cadence. It is long enough to be worth holding and short enough that the credential still means something about current knowledge when it is renewed.

What Are the MCPA Exam Details?

MCPA carries 60 questions in 120 minutes, costs 250 US dollars and requires 75 percent to pass. It is delivered online and proctored, in multiple choice format, and the purchase includes one retake. There are no prerequisites, and the certification is valid for two years.

Two minutes per question is generous by any standard, and it is the most reader friendly mechanic on the paper. This is not a speed test. It is a comprehension test with enough time to read a scenario properly, which fits a subject where the question is usually about what should happen rather than what a command does.

Seventy five percent means 45 correct answers out of 60, a margin of fifteen. Across five domains that is three questions each, which is tighter than it looks once you notice that the two largest domains carry thirty questions between them. Rehearsing against MCPA practice questions is worth doing at full length, because the time allowance changes how the paper feels.

The included retake is genuinely unusual and worth factoring into the price comparison. At 250 US dollars with a second attempt in the box, the effective cost per attempt is lower than several cheaper looking exams that charge again for a resit.

How Is MCPA Weighted Across Five Domains?

MCPA splits into Interactions and Execution at 26 percent, Security and Governance at 24 percent, Use Cases and Ecosystem at 20 percent, MCP Fundamentals at 16 percent and Architecture and Components at 14 percent. The five figures total exactly 100 percent, and the Linux Foundation publishes the same weightings on its own exam page.

The ordering is the interesting part. On most protocol exams the architecture domain is the biggest, because knowing the components is the foundation of everything else. Here architecture is the smallest at 14 percent, and execution and security take half the paper between them.

That is a deliberate statement about what an associate is expected to be useful for. Knowing that a host talks to a server is assumed background. Knowing what happens when the server returns an error mid invocation, or whether the user actually consented to the action being taken, is the job.

Why Is Interactions and Execution the Largest Domain?

Interactions and Execution is 26 percent of MCPA, roughly sixteen questions, and it is the only domain with four published objectives: interaction patterns and response handling, error handling, the tool invocation lifecycle, and protocol primitives. It is the operational heart of the protocol and the part a working integration lives or dies on.

The tool invocation lifecycle is the concept to get completely solid. A host decides a tool is needed, a client issues the call through the protocol, a server performs the work, and a result travels back into the model’s context. Every question about timing, failure or partial results is a question about which stage of that sequence something went wrong in.

Error handling being its own named objective, rather than a footnote inside response handling, is the clearest signal in the blueprint. Distributed calls fail in ways local function calls do not: the server may be unreachable, the tool may succeed but return something unusable, or the call may time out after the work has already happened. An associate is expected to know what the protocol says should happen in each case.

Protocol primitives are the vocabulary underneath all of it, and they are best learned from the MCP introduction rather than from a summary, because the names are precise and the exam uses them precisely.

How Much of the Exam Is Security and Governance?

Security and Governance is 24 percent of MCPA, roughly fourteen questions, and carries four objectives: trust boundaries, permissions and consent, risk and safety controls, and auditability and observability. Nearly a quarter of an associate level protocol exam is about authorisation and accountability, which is unusual and deliberate.

Trust boundaries are the organising idea. In an MCP deployment the model, the host application, the client and the server are frequently owned by different parties, and each hop is a place where something can be trusted that should not be. Questions here tend to describe an arrangement and ask which component is trusting which, and whether it should.

Permissions and consent are the human half. A model deciding to call a tool is not the same as a user agreeing that it should, and the protocol treats those as separate things. This is the objective most likely to be underestimated by an engineer who thinks of MCP as plumbing, because it is a product design question as much as a technical one.

The risk and safety controls objective connects directly to work being done outside the protocol, and the OWASP LLM application risks is the most useful independent reading for it. Several of the failure modes it describes, particularly excessive agency and insecure plugin design, are exactly what trust boundaries and consent controls exist to prevent.

Auditability and observability close the domain. If a model took an action, the exam expects you to know that the record of it is a design requirement rather than a nice to have.

What Does the Architecture Domain Cover?

Architecture and Components is the smallest domain at 14 percent, roughly eight questions, and covers three things: schemas and structured data, MCP hosts, clients and servers, and the model interaction flow. It is small because it is foundational rather than because it is optional, and the other four domains all assume it.

The three role names are precise and are frequently confused. A host is the application the user is actually in. A client is the connector inside that host which speaks the protocol. A server is the thing exposing tools or data on the other side. One host can hold several clients, each talking to a different server, and questions that seem to be about topology are usually testing whether those three definitions are clean.

Schemas and structured data are the second half, and they are what make the protocol useful rather than merely possible. A tool describes itself in a structured way so a model can decide whether and how to call it, which is why the vendor lists reading and interpreting server manifests among its recommended skills.

Model interaction flow ties the two together: how a request travels from the user, through the host and client, to the server, and how the result comes back into the model’s context. Get that path straight and the 26 percent execution domain becomes considerably easier.

What Should You Already Know Before Booking?

The Linux Foundation states there are no prerequisites for MCPA, but publishes five recommended competencies: foundational knowledge of JSON-RPC or similar message based protocols, experience interacting with LLM APIs, an understanding of agentic AI concepts, basic literacy in security concepts, and the ability to read and interpret MCP server manifests.

Those five are worth reading as a self assessment rather than as marketing. The exam is not going to test JSON-RPC directly, but it will describe message exchanges in terms that assume you have seen one before. The same is true of the security literacy item, which is not about holding a security credential and is about recognising what a trust boundary means.

The manifest reading skill is the most concrete of the five and the easiest to acquire. Open a few published MCP server manifests, work out what each tool declares about itself, and the architecture and execution domains both become noticeably less abstract. The full list sits on the official MCPA exam page.

For anyone new to the Linux Foundation’s associate tier, the format and pacing are consistent across its credentials, and our walkthrough of the CNPA associate exam shows what that tier expects in a different subject.

How Should You Prepare for the MCPA Exam?

Preparation for MCPA should follow the weighting rather than the blueprint order, because execution and security carry half the paper and architecture carries only 14 percent. Read the current specification once end to end, then build something small, then go back to the two heavy domains with real experience behind you.

1. Read the current dated revision of the specification once end to end, without stopping to memorise, so the shape of the protocol is familiar before any objective list is opened.
2. Get the three role names completely clean, host, client and server, and describe an interaction out loud until the path from user to tool and back is automatic.
3. Open several published MCP server manifests and work out what each declared tool is telling a model about itself, since the vendor lists that skill explicitly.
4. Build or run a small MCP server, call one of its tools from a host, and then break it on purpose so the error handling objective is something you have watched rather than read.
5. Work through trust boundaries by drawing the deployment you built and marking every point where one component trusts another, then ask what would happen if that trust were misplaced.
6. Study permissions and consent as a design question rather than a code question, because the exam separates a model deciding to act from a user agreeing that it should.
7. Finish on the ecosystem domain, which is 20 percent and largely about roles, adoption and portability, then rehearse the full 60 questions in 120 minutes.

The wider Linux Foundation credential set, including how the associate tier fits together, is collected on our Linux Foundation certification hub.

Frequently Asked Questions

How many questions are on the MCPA exam?

Sixty questions in 120 minutes, which is two minutes per item. It is one of the more generous time allowances at this level.

What is the passing score for the Model Context Protocol Associate exam?

Seventy five percent, which is 45 correct answers out of 60. That leaves a margin of fifteen questions across five domains.

How much does MCPA cost?

250 US dollars, purchased through the Linux Foundation training portal. The price includes one retake.

Are there prerequisites for MCPA?

No. The Linux Foundation states there are no prerequisites, but recommends foundational knowledge of JSON-RPC or similar message based protocols, experience with LLM APIs, an understanding of agentic AI concepts, basic security literacy, and the ability to read MCP server manifests.

Which MCPA domain carries the most weight?

Interactions and Execution at 26 percent, followed by Security and Governance at 24 percent. Together they are half the paper. Use Cases and Ecosystem is 20 percent, MCP Fundamentals 16 percent, and Architecture and Components 14 percent.

How long is the MCPA certification valid?

Two years, which matches the cadence of a specification that is published as dated revisions rather than numbered releases.

What is the difference between an MCP host, client and server?

The host is the application the user is in, the client is the connector inside it that speaks the protocol, and the server is what exposes tools or data on the other side. One host can hold several clients, each connected to a different server.

Is the exam tied to a specific version of the specification?

The Linux Foundation does not pin the exam to a single dated revision in its published exam information. The domain names describe structural concepts that survive revisions, so studying the current specification is the sensible approach.

Does MCPA test security?

Yes, heavily. Security and Governance is 24 percent and covers trust boundaries, permissions and consent, risk and safety controls, and auditability and observability.

Is the exam proctored?

Yes. It is delivered online and proctored, in multiple choice format, through the Linux Foundation training portal.

Conclusion

The Model Context Protocol Associate exam is a protocol credential that spends half its marks on running a call correctly and authorising it properly. Sixty questions in 120 minutes, 250 US dollars with a retake included, 75 percent to pass, valid for two years, and weighted 26, 24, 20, 16 and 14 across five domains.

Study it against the current dated specification rather than a summary, build something small enough to break on purpose, and treat trust boundaries and consent as design questions rather than implementation details. Architecture is the smallest domain, which is the blueprint saying plainly that knowing the components is where this subject starts rather than where it ends.