A202 MCP server
Commit Sep 24, 2026Enables verifiable commerce for agent-led transactions through delegated authority, negotiation state machines, and conformance checking.
Also known as a202-protocol/a202
- Stars
- 4
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 0.1.0
- Last commit
- Sep 24, 2026
- License
- Apache-2.0
What is A202 MCP?
A202 enables verifiable commerce for agent-led transactions through delegated authority, negotiation state machines, and conformance checking.
Summary generated from the project's README
About A202 MCP server
A202 provides a formal specification for verifiable commerce involving software agents or independent organizations. It establishes a framework for managing delegated commercial authority, negotiation states, and transaction conformance. This protocol is designed for agent-to-agent or agent-led transactions where parties need to ensure that commercial mandates and bilateral sessions follow strict rules regarding disclosure and state transitions.
Developers can use the included conformance suite to validate their implementations against the protocol. The suite uses a runner to check fixtures against JSON schemas and additional invariants that schema validation alone cannot capture. To use the runner, a system needs a Python environment with jsonschema version 4.18 or higher. The process involves executing the run-conformance.py script from the repository root to ensure that both positive and negative fixtures behave according to the manifest requirements.
What you can do with it
- 1Validate commercial agent implementationsAn engineer can run the conformance suite to ensure their software agent correctly follows the A202 negotiation state machine.
- 2Manage delegated commercial authorityA developer can implement typed objects to define how an agent is permitted to act on behalf of an organization.
- 3Verify transaction conformanceA user can test if their system correctly rejects invalid commercial documents using negative fixtures.
Written from the project's README. Every use case is checked against a quote from it.
How to install A202 MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall A202 MCP in Claude Code
$ claude mcp add a202 -- docker run -i --rm ghcr.io/a202-protocol/a202-mcp:0.1.0Install A202 MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"a202": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/a202-protocol/a202-mcp:0.1.0"
]
}
}
}Install A202 MCP in VS Code
.vscode/mcp.json
{
"servers": {
"a202": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/a202-protocol/a202-mcp:0.1.0"
]
}
}
}Install A202 MCP in VS Code CLI
$ code --add-mcp '{"name":"a202","type":"stdio","command":"docker","args":["run","-i","--rm","ghcr.io/a202-protocol/a202-mcp:0.1.0"]}'Install A202 MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"a202": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/a202-protocol/a202-mcp:0.1.0"
]
}
}
}Install A202 MCP in Codex
$ codex mcp add a202 -- docker run -i --rm ghcr.io/a202-protocol/a202-mcp:0.1.0Install A202 MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.a202] command = "docker" args = ["run", "-i", "--rm", "ghcr.io/a202-protocol/a202-mcp:0.1.0"]
Install A202 MCP in Gemini CLI
$ gemini mcp add -s user a202 docker -- run -i --rm ghcr.io/a202-protocol/a202-mcp:0.1.0Install A202 MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"a202": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/a202-protocol/a202-mcp:0.1.0"
]
}
}
}Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablea202-protocol/a202 is public and reachablegithub.com/a202-protocol/a202 ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-09-24github.com/a202-protocol/a202 ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubA202: the Verifiable Agreement Protocol for Agent-Led Commerce
Status: Informative in full.
A202 is verifiable commerce for agent-to-agent or agent-led transactions: an open specification of commercial authority, negotiation state, and verifiable conformance for transactions between independent organisations, including transactions conducted on their behalf by software agents.
It defines typed objects for delegated commercial authority, a state machine for the transaction and for each bilateral session inside it, rules for what may be disclosed to whom, and an executable conformance suite that turns each of those into a check an implementation either passes or fails.
The full statement of purpose, scope, and non-goals is in CHARTER.md.
Created and developed by A. A. Musse. See MAINTAINERS.md.
Status
Released, pre-1.0.
v0.1.0is the first tagged release of the set: a tag, a digest for every schema file, the conformance manifest, and release notes, published together. See RELEASES.md and CHANGELOG.md. Before 1.0 a MINOR increment may break compatibility, and any break carries migration notes.- The name is A202, spoken "A two-oh-two", and in full A202, the Verifiable Agreement Protocol for Agent-Led Commerce. The long form is a descriptor and not an expansion: the letters do not stand for it. The
202is HTTP 202 Accepted, which A202-0017 makes the status an accepted submission returns, because acceptance is the primitive the rest of the specification is built on. TheA202-reason-code prefix, theA202-NNNNproposal identifiers, and thea202-commercial/0.1specification version string all follow from the name. - A202™ is a trademark of Plural Worlds. Permitted use of the name is stated in TRADEMARK.md.
- Schema
$idvalues resolve underhttps://schemas.a202.org. Fixture hosts use reserved.invalidnames, because test data must never resolve. - Licensed under the Apache License, Version 2.0. One licence covers the whole repository: specification text, schemas, fixtures, manifest, runner, and informative documents. The licence carries an express patent grant from each contributor. See LICENSE and CONTRIBUTING.md.
- External contributions are accepted on the terms in CONTRIBUTING.md: inbound contributions under the same licence, with a developer certificate of origin sign-off.
Layout
| Path | Contents |
|---|---|
CHARTER.md |
Purpose, scope, non-goals, design principles |
GOVERNANCE.md |
How the project is run, and what the sponsor does and does not control |
MAINTAINERS.md |
Who maintains this repository |
CONTRIBUTING.md |
Contribution status, and the terms a contribution is accepted under |
SECURITY.md |
Private coordinated disclosure |
THREAT-MODEL.md |
Adversaries assumed, properties defended, and what is deliberately not defended |
CODE_OF_CONDUCT.md |
Expected conduct |
TRADEMARK.md |
The A202 name, and what use of it is and is not permitted |
RELEASES.md |
Versioning, what a release consists of, compatibility policy |
CHANGELOG.md |
What changed, and where the release notes required by RELEASES.md accumulate |
.github/ |
Review routing, the pull request and issue forms, and the workflow that runs the suite on every change |
proposals/ |
The A202 change proposal process |
schemas/ |
Canonical commercial model, transaction profile extension model, and the JSON schemas |
authority/ |
Commercial mandate: delegated authority, constraints, delegation, approval, revocation |
discovery/ |
Counterparty invitation: how an unregistered party enters one named transaction |
negotiation/ |
Transaction and session state machines, and auction event semantics |
conformance/ |
Fixtures, manifest, normative runner, and the conformance grade definitions |
Each specification document carries a status header stating which of its sections are normative and which are informative.
Running the conformance suite
The runner validates every fixture named in the manifest against the schemas, then applies the invariants that JSON Schema cannot express. Schema validity is not conformance, which is the reason the runner exists.
It needs jsonschema>=4.18. If that is not on the system interpreter, a virtual environment is enough:
python3 -m venv .venv && .venv/bin/pip install "jsonschema>=4.18"
Run it from the repository root:
python3 conformance/run-conformance.py --verbose
The expected result is every fixture passing and none failing, with the totals the manifest carries: the manifest is the single source for the count, and the runner prints it on every run. The runner also asserts that each negative fixture is refused for the reason code the manifest declares for it, wherever the normative layer raises codes at all. Run it before and after any schema change.
Every negative fixture is minimal: removing the single offending element must leave a document that validates cleanly. A negative fixture that fails for an incidental reason tests nothing, so verify that when adding one.
The suite does not depend on anyone remembering to run it. It runs, together with the reference implementation tests and the MCP server tests, on every pull request and on every push to the default branch, under .github/workflows/checks.yml. GOVERNANCE.md section 3.4 requires the suite to pass for any change to schemas, fixtures, the manifest, or the runner, and that workflow is what turns the requirement into a gate.
Where to start reading
- CHARTER.md for what this is and what it deliberately is not.
- schemas/canonical-commercial-model-v0.1.md for the object model, the envelope, and the invariants schema validation cannot express.
- negotiation/pilot-transaction-state-machine-v0.1.md for what moves state and what does not.
- conformance/manifest-v0.1.json for the fixtures that decide whether an implementation agrees with either of the above.
A202 MCP questions
How do I add A202 MCP to Claude Code?
Run claude mcp add a202 -- docker run -i --rm ghcr.io/a202-protocol/a202-mcp:0.1.0 in your terminal. Add --scope user to make it available in every project.
How do I add A202 MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What is the purpose of the A202 protocol?
It provides a specification for verifiable commerce in agent-to-agent or agent-led transactions, covering commercial authority, negotiation state, and conformance.
What is the current release status of A202?
The protocol is currently released as pre-1.0, with v0.1.0 being the first tagged release.