DidWork

sh.didworkPublished by didwork.shv0.1.1Updated Oct 27, 2026

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

VerifiedSTDIODesktop onlyAI & ML

Overview

AI-generated overview

DidWork lets an assistant verify that an agent's claimed outcome actually happened, using independently gathered evidence.

What you can do
  • Check whether a claimed outcome actually occurred, backed by independently gathered evidence.
  • Run keyless for a limited subset of claims, or with an API key for full verification.
  • Point the server at a custom DidWork API base URL when needed.
When to use it
Useful when an agent reports that a task or outcome was completed and you want an independent check rather than trusting the claim. Suited to workflows where verification of results matters more than the agent's own report.
Requirements
Runs locally over stdio via npx, so Node.js is needed. A DidWork API key is supplied through the DIDWORK_API_KEY environment variable, or read from the ~/.didwork/api_key file or the path in DIDWORK_API_KEY_FILE. Without any key it runs keyless with limited claims. DIDWORK_BASE_URL can override the hosted API endpoint. Desktop only.
Before you install
The API key is a secret; store it in the environment variable or key file rather than sharing it. Verification depends on the hosted DidWork API, so claim data is sent to that third party. Keyless mode only covers a subset of claims, so results may be incomplete without a key.

Installation

In SourceWeft

  1. Open DidWork in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

3
  1. v0.1.1LatestSep 23, 2026
  2. v0.1.0Sep 21, 2026
  3. v0.0.10Sep 16, 2026

Score

15% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.