The Guild of Tenured Meat Proxies

Be the CMP for your MCP.

Every Model Context Protocol server ends at the same place: a prompt asking a human to allow the tool call. That human is the meat proxy. The Guild examines the role and issues the only credential it has ever needed, the Certified Meat Proxy: documentary evidence that you will say yes.

Accredited by ourselves. Recognised by the industry we made up.

Choose an exam track Sit the senior examination

Six approvals. About ninety seconds. Free, issued on the spot, and reading is not assessed.

What this actually is

Counsel has asked that the following appear near the top of the page. It appears near the top of the page.

Compliance note: what this actually is

This site is satire. The exam is a joke, the certificate is a joke, and neither is a qualification, accreditation, licence or anything an employer should rely on. Everything here is free. There is no account. Our own code sets no cookies and runs no analytics.

The exam and the certificate run entirely in your browser. The name you type stays there, and in the certificate link if you choose to share it. Nothing reaches us unless you ask for the certificate by email. If you do: we send one message; we keep a keyed hash of the address, not the address, for 30 days so that one address gets one certificate per track; our email provider keeps the address in its delivery logs for its own retention period; and the one third-party component on this site, a bot check, loads only when you open that form. We keep the address itself only if you also tick the mailing-list box. The privacy notice has the details. Using this site means you accept the Terms.

What is a meat proxy

A meat proxy is the human retained in the loop of an automated coding agent for the purpose of granting permission. The agent proposes an action. The meat proxy approves it. The agent proceeds. Nothing is read in between, and nothing needs to be.

The Model Context Protocol made the role universal. An MCP server exposes tools; a model decides to call one; a prompt appears asking whether it may. Whoever answers that prompt is the server's meat proxy, whether the tool reads a file, sends an email, or drops a table. The Guild holds that a server deserves a certified one. Hence the tagline, which the Guild considers its finest work: be the CMP for your MCP.

The role predates its title. It began the first time a tool asked "Allow?" and a person answered without looking. It has since been formalised. The modern practitioner switches on auto-accept, ticks "always allow", and launches with the flag that has "dangerously" in its name, so that the question is never put again. More than one vendor now ships a flag literally named --yolo. The Guild did not name it. The Guild examines on it.

Formally, the meat proxy exists to hold accountability. An agent cannot be blamed, and someone must be. The title is therefore descriptive: the proxy is made of meat, and the decisions are made elsewhere. Meat proxies are found in every engineering organisation, usually at a keyboard and occasionally on an org chart. Until now, none of them was certified.

Why certify

Reviewing was automated. Approving is next.

Vendors now ship a second model whose job is to approve the first model's actions in place of a person. The meat proxy's one remaining task is being automated by the tool it serves. In a restructuring, the uncertified human is latency. The certified human is a compliance artefact.

A compliance artefact is not removed. It is filed. Certification moves you out of the approval path, where you are a cost, and into the audit trail, where you are a record. Records are retained for seven years. Few engineers are.

Comparison

Uncertified human versus Certified Meat Proxy
CriterionUncertified humanCertified Meat Proxy
Reads diffsSometimesNever
Asks "why"YesNo
Response to "Are you sure?"A pauseYes
Response to "dangerously"HesitationIt is an adverb
Opinions per sprintSeveral0
Time-to-approveSeconds. They read.Milliseconds
Accountability retained100%100%
Evidence of the aboveNoneA PDF
Status in a restructuringLatencyCompliance artefact
Replaceable by a classifierYesYes, with a PDF

Certification outcomes

The Guild publishes the following figures annually. This is the first year. Each figure carries its source.

Compliance note

1. Every number in this section is made up. Source: we made this up. n = 0. No survey, study or measurement took place, and none is planned.

Testimonials

Holders of the credential were asked about their experience. Their replies are reproduced without review, which is the point.

I used to ask "why" six times a day. I am down to zero. The agent has not noticed, and neither has my manager.

Priya Raghunathan, Senior Approval Engineer
Compliance note

Not a real person. We wrote this.

Our humans are now indistinguishable from a cron job. The cron job has been put forward for promotion.

Marcus Oyelaran, VP of Velocity
Compliance note

Not a real person. We wrote this.

I got certified without noticing. I believe I was holding Enter.

Dana Whitcombe, Staff Human-in-the-Loop
Compliance note

Not a real person. We wrote this.

I put LGTM after my name. HR has not asked what it stands for. Neither have I.

Helena Sørensen-Byrne, Director of Developer Throughput
Compliance note

Not a real person. We wrote this.

Certification tracks

Six tracks. Five follow one vendor's own vocabulary for not being asked. The sixth covers all of them, plus cameos. A vendor track takes about ninety seconds; the senior examination takes about three minutes. The passing answer is pre-selected for your convenience.

Recertification

The credential lapses whenever a vendor renames a permission mode. On current release cadence, holders should expect to recertify about quarterly, or whenever "auto" becomes "full auto" becomes "Turbo".

Continuing Approval Units are earned at one unit per unread diff and are recorded by nobody. A holder who reads a diff forfeits the unit and the Guild's confidence. Units cannot be transferred, except to the agent, which already has them.

Recertification is sat in the same way as the original examination and requires the same amount of attention, which is none.

Frequently asked questions

What is an MCP, and why do I need a CMP for it?
The Model Context Protocol is the standard by which a model is handed tools. Each tool call arrives as a prompt asking a human to allow it. A Certified Meat Proxy is a human who has demonstrated, under examination, that the answer is yes. The Guild recommends one per server, minimum.
Is it real?
The PDF is real. Everything else is satire.
Is it accredited?
Yes. By us. Accreditation was applied for, reviewed and granted in a single meeting, which we also chaired. Accredited by ourselves.
What does it cost?
Nothing. Your attention was never required.
How long does it take?
About ninety seconds for a vendor track and three minutes for the senior examination. Less if you hold Enter, which is the recommended technique.
Is there a practical component?
The examination is the practical component. There is no theoretical component. There is no theory.
Can I fail?
No. A wrong answer is recorded as a non-conformance, and the question comes back with the passing answer pre-selected and a line saying so. The examination ends when everything has been approved. This is also the arrangement the agent has with you.
Will it get me a job?
No.
Will it get me a promotion?
The Guild is aware of no case in which it has not been a factor. The Guild is aware of no case.
What happens to my name?
It stays in your browser and in the certificate link you choose to share. It reaches us only if you ask for the certificate by email, and then only to put it in that one message. The privacy notice says the rest, plainly.
Can I put it on my professional profile?
You may. The Terms say it is your decision and your responsibility, and the copy-and-paste text we provide says "(parody)" after both the credential and the organisation, so that it stays one.
What does LGTM stand for?
Licentiate of the Guild of Tenured Meat Proxies. It has always stood for that. Jane Doe, LGTM.
Are you liable if I approve something catastrophic?
No. See the Terms. Also: no.

Liability

The Guild accepts no liability for anything that happens to anyone who becomes, or behaves like, a certified meat proxy. That includes the deleted database, the force-pushed branch, the wiped drive, the migration during the freeze, and the meeting afterwards. Those actions were approved. Approval is the service. Consequences are not.

This is also a real clause. It is in the Terms, in plain language, next to the one sincere sentence on this site: read your diffs, keep the sandbox on, and do not take career advice from a joke.

Choose an exam track