Skip to content
MCP server

Ownership Attestation Protocol

MCP server that requires explicit task acceptance and provenance-tagged completion claims

Pricing
Open source
Platforms
API, self-hosted
Version
1.0.1
Listing updated
today

Similar MCP servers

About Ownership Attestation Protocol

Ownership Attestation Protocol is an open-source MCP server for agent tooling. It is available on API and self-hosted.

The README says the server enforces two rules: a task is not owned until an actor explicitly accepts it, and a completion claim cannot be filed without a provenance tag of observed, reviewed, or reported. Ownership moves only through handoff, and the recipient must accept before acting on the task.

The server exposes six MCP tools for creating tasks, accepting them, reporting completion, handing tasks off, reading full task history, and listing tasks that still have no owner. Acceptance is enforced atomically in the database, and the README describes concurrency tests run against a real PostgreSQL instance.

The project is built on Node.js 24 with PostgreSQL and is aimed at developers building multi-agent workflows who want an auditable record of who owns a task and how each completion claim was verified. The README describes it as an early, personally tested project rather than a production product.

Tools this server provides (6)

Taken from the project documentation; the running server may differ.

create_task
Creates a task in pending_acceptance state.
accept_task
Explicitly accepts a task, failing if it already has a different owner.
report_completion
Records a completion claim with a required provenance value.
handoff_task
Transfers ownership and captures a state snapshot.
get_task_status
Returns the full history for one task.
list_unaccepted_tasks
Lists tasks with no current owner.

What it does

Explicit task acceptance
Tasks start in pending acceptance and only count as owned after an actor accepts them.
Provenance-tagged completion
Completion reports must carry observed, reviewed, or reported, and invalid calls are rejected.
Snapshot handoffs
Ownership transfers capture a frozen copy of task state at the moment of handoff.
Full task history
A status call returns injection, acceptances, completion claims and handoffs for one task.
Unowned task listing
A query tool surfaces tasks that currently have no owner.

Good for

  • Tracking which AI agent has accepted responsibility for a delegated task
  • Requiring a stated verification basis before a multi-agent workflow marks work done
  • Auditing ownership changes and handoffs across agents in a pipeline
  • Finding tasks that were passed along without anyone accepting them

Pricing

Open source

Free and MIT licensed; self-hosted.

Ownership Attestation Protocol FAQ

Which transport and client setup does it use?

The MCP server is mounted at /mcp over HTTP and requires a bearer token. The README gives a Claude Code command as an example of connecting a client.

Does it create actors or user accounts?

No. The README says there is deliberately no create_actor tool, so actor identity comes from an existing system, and a seed script is provided for local development only.

What database does it need?

The README states it requires PostgreSQL, and the test suite must run against a real PostgreSQL instance.

What license is it released under?

The README lists the MIT license.

Is Ownership Attestation Protocol free?

Yes. Ownership Attestation Protocol is open source, so you can use and self-host it for free.

What are the best alternatives to Ownership Attestation Protocol?

The closest alternatives to Ownership Attestation Protocol are mcp-agent-template, Agentome and WebMCP — Make Any Website Agent-Ready.

Where this comes from

  • Description: written from the project's README and its MCP Registry entry.

How AIPoweredBot checks servers