DidWork
Verify that an agent's claimed outcome actually happened, using independently gathered evidence
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
@didwork/mcpclaude mcp add didwork -e 'DIDWORK_API_KEY=<your didwork_api_key>' -e 'DIDWORK_BASE_URL=<DIDWORK_BASE_URL>' -- npx -y @didwork/mcp@0.1.1
{
"mcpServers": {
"didwork": {
"command": "npx",
"args": [
"-y",
"@didwork/mcp@0.1.1"
],
"env": {
"DIDWORK_API_KEY": "<your didwork_api_key>",
"DIDWORK_BASE_URL": "<DIDWORK_BASE_URL>"
}
}
}
}
Environment variables
DIDWORK_API_KEYsecret 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_URLOverride the DidWork API base URL (defaults to the hosted API)
Frequently asked questions
What is DidWork?
Verify that an agent's claimed outcome actually happened, using independently gathered evidence
How do I install DidWork?
It runs on your machine. In Claude Code: claude mcp add didwork -e 'DIDWORK_API_KEY=<your didwork_api_key>' -e 'DIDWORK_BASE_URL=<DIDWORK_BASE_URL>' -- npx -y @didwork/mcp@0.1.1. For other clients, paste the JSON configuration from this page into their MCP settings.
Does DidWork need an API key?
Yes. It expects DIDWORK_API_KEY, which you set in its configuration.
Who maintains DidWork?
It is published by sh.didwork. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.