Agreements API Sdk vs Ownership Attestation… | AllMCPs
Side-by-Side Model Context Protocol Comparison
Agreements API Sdk vs Ownership Attestation Protocol
In-depth architectural comparison of the Agreements API Sdk and Ownership Attestation Protocol MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Agreements API Sdk
Agreements & Coordination · Local stdio
Quality: 63/100 (Good) | Auth: API Key required
Ownership Attestation Protocol
Agreements & Coordination · Remote HTTP/SSE
Quality: 36/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Agreements API Sdk if you need specialized Agreements & Coordination tools running via a local process. Choose Ownership Attestation Protocol if your workspace requires Agreements & Coordination integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Agreements API Sdk when:
You need dedicated capabilities in the Agreements & Coordination domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
Remote Streamable HTTP and local stdio MCP server for defining, validating, deploying, and operating machine-readable agreements with EIP-712 permit preparation, signed participant inputs, state reads, and input history.
MCP protocol enforcing explicit task acceptance and attestation-tagged completion claims.
Lists agreement summaries visible to the current API key. Supports pagination (cursor + limit), filtering by chain and state, and sorting. Returns summaries only; use get_agreement for the full record.
get_agreement
Returns a single agreement record, including the full authored agreement JSON and hosted record context (participants, observers, owner, deployment address).
get_agreement_document
Returns the rendered hosted prose document for an agreement by documentId, including content type, display name, chain, docUri, and agreement record references. Use documentId from list_agreements/get_agreement or from prepare_deployment_typed_data.
get_agreement_state
Returns the current state of an agreement. For deployed agreements, interpret the state against the states defined in the authored agreement lifecycle (execution.states). Use this to poll for transitions after submitting an input.
get_input_history
Returns recorded input submissions for an agreement, with pagination and filtering. Use this to inspect which events have been submitted and whether each is PENDING, FINALIZED, or FAILED.
validate_agreement
Checks only the authored agreement JSON document and returns participant variable keys, input IDs, state IDs, and warnings. This does not validate deployment values, participant wallet addresses, signer, or permit data — use preflight_deployment for that. Iterate on the agreement JSON until this returns no blocking warnings. Requires the agreements.write scope.
preflight_deployment
Checks whether authored agreement JSON plus target chain, deployment values, participant wallet mappings, and observer context are ready for deployment. This does not deploy the agreement and does not require a signature. Always run this before signing a deploy permit. Requires the agreements.write scope.
deploy_agreement
Deploys authored agreement JSON using an EIP-712 permit; the API submits the on-chain transaction and returns the deployed agreement record. Provide a pre-signed permit (signer, deadline, signature), or call prepare_deployment_typed_data first to obtain the payload to sign. Always run preflight_deployment before deploying. Requires the agreements.write scope.
submit_input
Submits a signed input to a deployed agreement, advancing its on-chain lifecycle. The input ID and values must match an input defined by the agreement JSON, and the signer must be allowed by that input. Provide a pre-signed permit (signer, deadline, signature), or call prepare_input_typed_data first. Requires the agreements.write scope.
prepare_deployment_typed_data
Builds the exact EIP-712 payload that must be signed to authorize deployment of the given agreement JSON. Sign the returned typedData with the deploying wallet (eth_signTypedData_v4 / viem signTypedData), then call deploy_agreement with signer, deadline, and the signature components. No transaction is sent and nothing is stored. Reads the signer nonce from the target chain.
prepare_input_typed_data
Builds the exact EIP-712 payload that must be signed to authorize submitting an input to a deployed agreement. Sign the returned typedData with a wallet allowed by the input definition, then call submit_input with signer, deadline, and the signature components. No transaction is sent and nothing is stored. Reads the agreement record and signer nonce.
Ownership Attestation Protocol Tools (0)
No explicit tool names declared in metadata yet. Check project README on main listing page.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Agreements API Sdk is categorized under Agreements & Coordination and uses a local stdio subprocess. In contrast, Ownership Attestation Protocol belongs to Agreements & Coordination using remote streaming HTTP/SSE transport. Select Agreements API Sdk when you need capabilities focused on agreements & coordination and Ownership Attestation Protocol when you require tools for agreements & coordination.