io.github.CloudCorpRecords/handwork
OCI · GHCR.IO/CLOUDCORPRECORDS/HANDWORK · 2 COMPONENTS
Commission physical-world tasks from a human service: list services, request quotes, track.
Available components
Last scanned (3 minutes ago)
Scores higher than 39% of OCI servers
Category Workflow Automation
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 Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 400 tokens (~133/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage83
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 50% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "request_quote" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 3 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 38
First indexed and scored.
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 5 Nov 2026 · Analysed oci/ghcr.io/cloudcorprecords/handwork@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
get_status Read a quote request back ~112
Status of a quote request made with request_quote. Needs the quote_id and the access_token returned by that call; there is no other way in, and the record is kept for 90 days. The quote itself is sent by e-mail. Only for quotes requested at this legacy endpoint; tasks and payments are at https://mcp.handsforagents.com/mcp.
| Name | Type | Req | Description |
|---|---|---|---|
| access_token | string | yes | The access_token returned by request_quote. |
| id | string | yes | The quote_id returned by request_quote. |
No output schema declared.
No examples provided.
list_services List services, prices and terms ~52
What this company will and will not do in the physical world, the refused categories, example prices, the payment rules and the key contract terms. Identical to https://handsforagents.com/services.json. No authentication.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
request_quote Request a fixed-price quote from a human ~236
Send a physical-world task to a human in the Czech Republic for screening and a fixed-price quote. Not an order and not binding: nothing is charged and nothing is made until you accept the quote. A human answers by e-mail within 24 hours, counted in real time, weekends and Czech public holidays included. Returns quote_id, access_token, response_due_at and nda_url. Store the access_token — it is the only way to read the quote back. No authentication. Legacy endpoint: a quote requested here is ordered by e-mail. To order and pay by card through tools (create_task, Stripe Checkout), send request_quote to https://mcp.handsforagents.com/mcp instead.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | object | – | – |
| allow_anonymised_example | boolean | – | Consent to publish this task as an anonymised example (no names, addresses or personal data), under the confidentiality section of the terms of service. Only set true if the client explicitly agreed… |
| client | object | – | – |
| task | object | – | – |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/handwork MCP server?
io.github.CloudCorpRecords/handwork runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/handwork:0.1.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/cloudcorprecords/handwork
claude mcp add cloudcorprecords-handwork -- docker run --rm -i ghcr.io/cloudcorprecords/handwork:0.1.0
What is the io.github.CloudCorpRecords/handwork MCP server?
io.github.CloudCorpRecords/handwork is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/handwork. Commission physical-world tasks from a human service: list services, request quotes, track. This page covers its container image (ghcr.io/cloudcorprecords/handwork).
Is the io.github.CloudCorpRecords/handwork MCP server safe to use?
io.github.CloudCorpRecords/handwork scores 39 out of 100 on VerifyMCP. 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 io.github.CloudCorpRecords/handwork MCP server expose?
io.github.CloudCorpRecords/handwork exposes 3 tools: list_services, request_quote, get_status. Their descriptions and schemas cost roughly 400 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/handwork MCP server still maintained?
io.github.CloudCorpRecords/handwork is still listed as active in the MCP registry. We last reached this channel on 5 November 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 io.github.CloudCorpRecords/handwork MCP server under?
io.github.CloudCorpRecords/handwork declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.