Ownership Attestation Protocol vs DottedSign

A side-by-side look at the Ownership Attestation Protocol and DottedSign MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Ownership Attestation Protocol logoOwnership Attestation ProtocolAgreements & Coordination · Remote HTTP/SSEMCP protocol enforcing explicit task acceptance and attestation-tagged completion claims.39FairAuth: not declaredDottedSign logoDottedSignAgreements & Coordination · Remote HTTP/SSEAutomate eSignature workflows and signing tasks via natural language commands.43FairAuth: not declared

Verdict: choose Ownership Attestation Protocol for agreements & coordination work over a hosted endpoint; choose DottedSign for agreements & coordination over a hosted endpoint. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Ownership Attestation Protocol logoChoose Ownership Attestation Protocol when

  • You need dedicated capabilities in the Agreements & Coordination domain.
  • You prefer a remote HTTP/SSE transport.
  • You have the keys it needs: DATABASE_URL, MCP_ACCESS_TOKEN.
Explore Ownership Attestation Protocol

DottedSign logoChoose DottedSign when

  • You need dedicated capabilities in the Agreements & Coordination domain.
  • You prefer a remote HTTP/SSE transport.
Explore DottedSign

Feature & specification comparison

Rows where the two servers differ are marked.

SpecOwnership Attestation Protocol logoOwnership Attestation ProtocolDottedSign logoDottedSign
CategoryAgreements & CoordinationAgreements & Coordination
Quality signal39/100 · Fair43/100 · Fair
Install commandConfirmedConfirmed
TransportRemote HTTP/SSERemote HTTP/SSE
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsDATABASE_URLMCP_ACCESS_TOKENNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars1142
Directory activity 2 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Ownership Attestation Protocol tools

No tool names declared yet. Check the project README from the listing page.

DottedSign tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Ownership Attestation Protocol

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "ownership-attestation-protocol": {
      "url": "http://localhost:5000/mcp"
    }
  }
}

DottedSign

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "dottedsign": {
      "url": "https://mcp.dottedsign.com/dottedsign-api/mcp"
    }
  }
}

Frequently asked questions

Ownership Attestation Protocol is categorized under Agreements & Coordination and uses a remote HTTP/SSE transport. DottedSign belongs to Agreements & Coordination and uses a remote HTTP/SSE transport. Pick Ownership Attestation Protocol for agreements & coordination work and DottedSign for agreements & coordination.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Ownership Attestation Protocol has no declared pricing — check the project's own site. DottedSign has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add ownership-attestation-protocol and dottedsign as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Ownership Attestation Protocol has a quality signal of 39/100 (Fair) with 2 views, 0 installs and 1 GitHub stars. DottedSign has 43/100 (Fair) with 0 views, 0 installs and 142 GitHub stars.