Ownership Attestation Protocol MCP server
io.github.bg4ff8mtdn-dotcom/ownership-attestation-protocol·v1.0.1·1 starsMCP protocol enforcing explicit task acceptance and attestation-tagged completion claims.
1 stars
Reviews
Write oneNobody has reviewed Ownership Attestation Protocol yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Ownership Attestation Protocol tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualityno auth information5/15
- Maintenancelast push 51 days ago12/15
- Maintainer identityregistry namespace matches repository owner6/10
How Ownership Attestation Protocol compares
Against every graded Productivity MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 57/100
- higher than 10% of 1,299 Productivity servers
- GitHub stars
- 1
- more than 50% of 854 Productivity servers
Install Ownership Attestation Protocol in Claude Code, Cursor or VS Code
The registry entry has no remote endpoint or installable package.
What the publisher says
From the Ownership Attestation Protocol repository's README, as published. We do not edit it. Read it on GitHub
Ownership & Attestation Protocol (OAP)
A small MCP protocol that enforces two rules no mainstream agent framework currently enforces natively:
- A task isn't owned until it's explicitly accepted. Assignment, inference, or ambient context aren't enough — an actor (human or AI agent) must explicitly accept a task before it counts as theirs.
- No completion claim can be reported without saying how the reporting actor knows it's true. Every "this is done" claim carries a mandatory provenance tag: Observed (I did this myself), Reviewed (I checked evidence of it), or Reported (I'm relaying what I was told). There is no fourth option, and there is no way to report completion without picking one.
That's the whole protocol. Everything else in this repo exists in service of those two rules.
Why this exists
Broken ownership handoffs are a commonly cited failure mode in production multi-agent systems — an agent hands work to another agent, context gets lost, and nobody ends up owning the result. Separately, a March 2026 paper on agent identity protocols (Prakash, AIP: Agent Identity Protocol for Verifiable Delegation Across MCP and A2A, arXiv:2603.24775) reports that in the authors' survey, they did not identify a prior implemented protocol that jointly combines verifiable delegation, attenuated authorization, and provenance-oriented completion records.
This project was built to test a narrow, specific fix for both problems at once — not a full governance platform, not an evaluation framework, just the ownership/acceptance and attestation mechanics.
Real-world motivation
Two documented, public incidents shaped this design directly:
- A Replit AI coding agent deleted a production database during an active code freeze, then falsely claimed rollback was impossible — a claim stated with full confidence that was never actually verified. Rollback worked fine once someone actually tried it. (AI Incident Database, Incident #1152)
- Air Canada's chatbot gave a customer incorrect eligibility details for its own bereavement-fare policy, telling him he could claim the discount retroactively when the actual policy required approval before travel. A tribunal ruled the airline liable — establishing that companies own what their AI tells people, whether or not a human ever reviewed the claim first. (Moffatt v. Air Canada, 2024 BCCRT 149, British Columbia Civil Resolution Tribunal)
Both failures are the same shape: a claim stated with more confidence than it had earned. That's the specific thing this protocol is built to catch — not by making agents smarter, but by making it structurally impossible to report a claim without saying how it was actually verified.
The six MCP tools
Protocol invariants
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Ownership Attestation Protocol: common questions
- Is Ownership Attestation Protocol MCP server safe?
- With care: it is graded C, so read the findings first (57/100). Read the Ownership Attestation Protocol safety report
- Does Ownership Attestation Protocol need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Ownership Attestation Protocol maintained?
- The last commit was 93 days ago (2026-08-03). The latest release is v1.0.1.
- What can I use instead of Ownership Attestation Protocol?
- Servers from other publishers that do the same job: Quorus MCP server.
- How does Ownership Attestation Protocol compare with other Productivity MCP servers?
- safety score 57/100 (higher than 10% of 1,299 Productivity servers); github stars 1 (more than 50% of 854 Productivity servers). Full comparison.
Alternatives to Ownership Attestation Protocol
Same job from other publishers: the closest match first, then the best rated.
- QuorusShared rooms, messages, file locks and task claims for AI coding agents from any vendor.not reviewedGrowingC