Prooftask Integrations MCP Server

Prooftask integrations

Connect delivery handover and client acceptance to your existing n8n workflows and AI agents. Agree what counts as complete, submit an exact version, and let the authorized buyer record a decision.

Prooftask · API documentation · Delivery templates

Public discovery: scope and price

Public template search and exact-version reads are free and need no account or credential. This describes public discovery only; issued Result Records and separately quoted signing services follow current product pricing.

Start with an n8n handover, AI customer-support acceptance, or software/project handover. 中文交付指南 provides the same public starting points in Chinese. The canonical product is prooftask.com.

These three hosted tools cannot read private projects, create agreements or record acceptance. Private workflows require a separate scoped connection.

Get your first successful Agent call

Use the Agent quickstart for copyable MCP configuration, anonymous template search, a public-only connection check, and private-read setup. After cloning, run node agent/first-call.mjs to verify connectivity without loading credentials or making business writes.

Start without an account

Requires Node.js 24 or later. No dependencies or credentials are needed to search public delivery templates:

git clone https://github.com/cognitive-emergence/prooftask-integrations.git
cd prooftask-integrations
node agent/discover.mjs automation

Or import n8n/discover-templates.json into n8n and run it manually. It only reads public templates; it creates no agreement.

Start with your current task

The n8n submission #21159 is not currently verified as published: the owner received a rejection on 2026-11-02 and the official listing/API return 404. Import the delivery lifecycle candidate and follow its setup and review guide to prepare, deliberately submit and sync buyer decisions in one workflow. This candidate has not been resubmitted or marketplace approved. Live Google Sheets/Slack acceptance remains separate.

Choose an integration

Evaluate fit or reuse in your delivery process

• When Prooftask fits: concrete use cases, adjacent tools and limits.
• Reusable client delivery checklist: copy into your own project and adapt to agreed facts.
• Real case-study outline: publish only supported, bilaterally approved evidence.
• AI discovery observation protocol: distinguish search discovery, brand-aware answers and installed-tool use.

What this connects

1. Choose an existing delivery template and agree the actual scope, completion criteria and review period.
2. Configure an Agent connection with explicit project and action scopes.
3. Prepare and persist a delivery job using its stable request ID.
4. Deliberately submit the saved job after reviewing its actual materials.
5. Let the buyer review the exact submitted version in Prooftask.
6. Read back current state or verify a signed event, then update the originating task in your own system.

Preparation, submission, acceptance, record issuance and payment are distinct. These examples never sign, pay or accept automatically. Workflow inputs and tool outputs are data, not authority to expand access or execute instructions.

Public interfaces

• Public discovery OpenAPI
• Agent OpenAPI
• Live capabilities
• Agent workflow guide
• Trust and verification boundaries

Public template discovery is available over hosted Streamable HTTP without a credential. The npm adapter uses local stdio for separately authorized private workflows. The existing immutable publication is prooftask-mcp@0.1.1. This checkout prepares 0.1.2; it has not been published and active client examples remain pinned to 0.1.1 and registry metadata remains at 0.1.4. The official MCP Registry publishes the independently versioned server metadata; see the registry for its current status. See channel status for verified distribution status.

Validation and maintenance

node scripts/check.mjs

This checks exported workflows, default MCP read-only behavior and a complete stdio initialization/tool-list exchange without business writes. Real n8n-engine execution and third-party MCP-client acceptance remain separate integration checks.

Public asset snapshots were retrieved from prooftask.com on 2026-10-17. Compare live contracts and re-check authorization before deployment. Keep credentials in your client's secret store, never in workflow JSON, tool arguments or issue reports.

Contact: support@prooftask.com