DidWork MCP Server

Verify that an agent's claimed outcome actually happened, using independently gathered evidence

Local serverstdio

What is the DidWork MCP Server?

DidWork is an MCP integration. Verify that an agent's claimed outcome actually happened, using independently gathered evidence.

Packages and local setup

The published npm package is @didwork/mcp, version 0.1.1. Its declared MCP transport is stdio.

The package declares DIDWORK_API_KEY: DidWork API key, free at https://didwork.sh/console. Optional: the server falls back to the ~/.didwork/api_key file (or DIDWORK_API_KEY_FILE); with no key at all it runs keyless and only http.ok claims verify.; DIDWORK_BASE_URL: Override the DidWork API base URL (defaults to the hosted API).

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project website. This profile uses version 0.1.1 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related other integrations MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
DIDWORK_API_KEYDidWork API key, free at https://didwork.sh/console. Optional: the server falls back to the ~/.didwork/api_key file (or DIDWORK_API_KEY_FILE); with no key at all it runs keyless and only http.ok claims verify.Optional
DIDWORK_BASE_URLOverride the DidWork API base URL (defaults to the hosted API)Optional