DidWork
NPM · @DIDWORK/MCP · SCANNED SEP 23
Verify that an agent's claimed outcome actually happened, using independently gathered evidence
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 32 of 97 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 0 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1835 tokens (~183/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 60% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the DidWork MCP server?
DidWork runs locally as an npm package, launched with npx -y @didwork/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @didwork/mcp
claude mcp add sh-didwork-didwork -- npx -y @didwork/mcp
{
"mcpServers": {
"sh-didwork-didwork": {
"command": "npx",
"args": [
"-y",
"@didwork/mcp"
]
}
}
} {
"servers": {
"sh-didwork-didwork": {
"command": "npx",
"args": [
"-y",
"@didwork/mcp"
]
}
}
} codex mcp add sh-didwork-didwork -- npx -y @didwork/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sh-didwork-didwork": {
"type": "local",
"command": [
"npx",
"-y",
"@didwork/mcp"
],
"enabled": true
}
}
} openclaw mcp add sh-didwork-didwork --command npx --arg -y --arg @didwork/mcp
mcp_servers:
sh-didwork-didwork:
command: "npx"
args: ["-y", "@didwork/mcp"] {
"McpServers": {
"sh-didwork-didwork": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@didwork/mcp"
]
}
}
} assistant mcp add sh-didwork-didwork -t stdio -c npx -a -y @didwork/mcp
{
"mcpServers": {
"sh-didwork-didwork": {
"command": "npx",
"args": [
"-y",
"@didwork/mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 23 Sept 26 −1
- Schema quality: 134 → 183 ▼ functional
- Package version: 0.1.0 → 0.1.1 functional
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 0
- Tool coverage: 67% → 60% ▼ functional
- Schema quality: 1120 → 1344 ▼ functional
- Security disclosure: fail → unverified ▼ functional
- Package version: 0.0.10 → 0.1.0 functional
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 23 Sept 2026 · Analysed npm/@didwork/mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 97 packages
| Packages resolved | 97 |
|---|---|
| Stale | 31 |
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
did_get ~28
Fetch a verification by id (poll a pending async verification).
| Name | Type | Req | Description |
|---|---|---|---|
| verification_id | string | yes | – |
No output schema declared.
No examples provided.
did_get_run ~34
Read an outcome run by id. Running, failed and unknown are not completed success.
| Name | Type | Req | Description |
|---|---|---|---|
| run_id | string | yes | – |
No output schema declared.
No examples provided.
did_inspect_tool ~293
Capability Trust: before calling an agent tool with real-world consequences (money, email, deploys, deletes, permissions), ask what it can actually affect. DidWork statically analyses the tool implementations in a project — MCP server.tool / registerTool handlers and did.tool() declarations, TypeScript/JavaScript only — and returns a capability profile per tool: evidenced capabilities (e.g. financial.refund, communication.external, data.delete) each backed by file:line evidence, a risk level (low/moderate/high/critical/unknown), a separate confidence level, and a status: verified (profile established), failed (DECLARATION_MISMATCH: the implementation exceeds what did.tool() declares), or unknown (insufficient evidence). Treat unknown as 'not shown to be safe', never as low risk; it usually means the tool calls something injected at runtime or loads code dynamically. Omit `tool` for the project summary and one row per tool; pass `tool` for the full profile with evidence and gaps. Runs locally, reads source only, no API key needed, nothing is uploaded.
| Name | Type | Req | Description |
|---|---|---|---|
| max_depth | integer | – | Project-internal calls to follow from each handler (default 8) |
| root | string | – | Project directory to inspect (default: the directory the host launched the server in) |
| tool | string | – | Tool name for the full profile; omit for the summary |
No output schema declared.
No examples provided.
did_list ~30
Recent verifications for this API key — the developer log, evidence included.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
did_unwatch ~23
Stop a watch by id.
| Name | Type | Req | Description |
|---|---|---|---|
| watch_id | string | yes | – |
No output schema declared.
No examples provided.
did_usage ~15
Verifications performed, by month.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
did_verify ~727
Independently verify that an intended outcome is actually true. Sends claim fields (including private repository identifiers, branches and commit SHAs), optional subject/account labels and tool profiles to the configured DidWork API (default https://api.didwork.sh). DidWork reads provider state without modifying it, but authenticated verification creates a DidWork record containing the claim, verdict, timestamps and evidence, which may include provider response data. Verification evidence is retained under the account plan (Free: 7 days; Pro: 365 days). Keyless http.ok does not store a verification record. Host approval rejection means the tool was blocked, not a failed or unknown DidWork verdict; report it separately and do not retry through another route. Send a claim (type + expected); DidWork gathers evidence from the authoritative system and returns a verdict: verified, failed, or unknown. Gate your next action on the verdict — an agent should not grade its own work. Treat unknown as 'do not proceed yet'. Prefer the most specific claim type for the outcome; http.ok is the fallback and is unauthenticated, so it cannot see private repos, dashboards or anything behind a login — against those it reports a 404 as failed, which says nothing about whether the work landed. Claim types, by provider (connect providers at https://didwork.sh/console): stripe.refund, stripe.payment_succeeded, stripe.subscription_active, stripe.subscription_cancelled, stripe.invoice_paid, stripe.checkout_completed, stripe.payout_paid, stripe.payment_method_attached; github.pr_merged, github.workflow_passed, github.issue_closed, github.release_published, github.commit_in_branch, github.file_exists, github.deployment_succeeded, github.pr_review_approved, github.branch_exists; gitlab.mr_merged, gitlab.pipeline_passed, gitlab.issue_closed, gitlab.commit_in_branch, gitlab.file_exists, gitlab.release_published; linear.issue_completed, linear.issue_in_state, linear.issue_assigned; jira.issue_done,…
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | Which connected account to verify against, by the label the user gave it in the console (e.g. 'acme'). Omit to try every account connected for the provider. |
| expected | object | yes | The claim's expected fields. For github.commit_in_branch use { repository: 'owner/repo', branch: 'main', commit: 'full-sha' }; for stripe.refund use { payment: 'pi_123', amount: 4999 }. |
| subject | string | – | Optional caller-side reference id |
| tools | array | – | The tools that performed the work, as profiles from did_inspect_tool or { name, capabilities } records. Recorded on the receipt as caller-reported context (what the tools could affect); the verdict d… |
| type | string | yes | Claim type, e.g. 'stripe.refund' or 'http.ok' |
| wait | boolean | – | false = return a pending verification immediately and poll with did_get |
No output schema declared.
No examples provided.
did_verify_contract ~257
Verify a reviewed version 2 outcome contract. Pass the requirements unchanged; never remove or weaken requirements to obtain a pass. The caller must load the contract from the trusted source. DidWork records caller-supplied provenance, independently gathers claim evidence and returns a run. Reuse the same idempotency_key after an interrupted request. A verified run covers only its required checks. Requires an API key. Sends claim fields (including private repository identifiers, branches and commit SHAs), optional subject/account labels and tool profiles to the configured DidWork API (default https://api.didwork.sh). DidWork reads provider state without modifying it, but authenticated verification creates a DidWork record containing the claim, verdict, timestamps and evidence, which may include provider response data. Verification evidence is retained under the account plan (Free: 7 days; Pro: 365 days). Keyless http.ok does not store a verification record. Host approval rejection means the tool was blocked, not a failed or unknown DidWork verdict; report it separately and do not retry through another route. The full contract and caller-supplied provenance are also sent and stored on the outcome run.
| Name | Type | Req | Description |
|---|---|---|---|
| contract | object | yes | – |
| idempotency_key | string | yes | – |
No output schema declared.
No examples provided.
did_watch ~410
Continuously re-verify a claim on an interval (e.g. '10m', '1h'). DidWork notifies the webhook_url on the first run and on verdict transitions. Plan limits apply: a free key may run one watch, hourly at most ('1h'), and a shorter interval or a second watch is refused with 402 watch_cadence_requires_pro or 402 watch_limit_reached. Pro keys run unlimited watches down to '5m'. If a watch is refused, say so — do not retry at the same cadence. Sends claim fields (including private repository identifiers, branches and commit SHAs), optional subject/account labels and tool profiles to the configured DidWork API (default https://api.didwork.sh). DidWork reads provider state without modifying it, but authenticated verification creates a DidWork record containing the claim, verdict, timestamps and evidence, which may include provider response data. Verification evidence is retained under the account plan (Free: 7 days; Pro: 365 days). Keyless http.ok does not store a verification record. Host approval rejection means the tool was blocked, not a failed or unknown DidWork verdict; report it separately and do not retry through another route. Stores the schedule and webhook URL in DidWork; sends notifications to that URL.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | Which connected account to verify against, by the label the user gave it in the console (e.g. 'acme'). Omit to try every account connected for the provider. |
| every | string | – | Interval like '10m', '1h', '1d' (default 1h) |
| expected | object | yes | The claim's expected fields. For github.commit_in_branch use { repository: 'owner/repo', branch: 'main', commit: 'full-sha' }; for stripe.refund use { payment: 'pi_123', amount: 4999 }. |
| type | string | yes | – |
| webhook_url | string | – | – |
No output schema declared.
No examples provided.
did_watches ~18
List active watches with their last verdicts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the DidWork MCP server?
DidWork is an MCP server listed in the public MCP registry as sh.didwork/didwork. Verify that an agent's claimed outcome actually happened, using independently gathered evidence. This page covers its npm package (@didwork/mcp).
Is the DidWork MCP server safe to use?
DidWork scores 73 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the DidWork MCP server expose?
DidWork exposes 10 tools: did_verify, did_get, did_verify_contract, did_get_run, did_list, and 5 more. Their descriptions and schemas cost roughly 1,835 tokens of context every time the server is loaded.
Is the DidWork MCP server still maintained?
DidWork is still listed as active in the MCP registry. We last reached this channel on 23 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the DidWork MCP server under?
DidWork declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.