Awaitless
PYPI · AWAITLESS-RUNNER · SCANNED AUG 20
Durable execution and named concurrency queues for coding agents across local, SSH, and Slurm.
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 →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 2 of 31 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- 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
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability62
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1434 tokens (~130/item across 11 items; 11 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 Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
pypi · awaitless-runner
claude mcp add xpluspro-awaitless -- uvx awaitless-runner
codex mcp add xpluspro-awaitless -- uvx awaitless-runner
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"xpluspro-awaitless": {
"type": "local",
"command": [
"uvx",
"awaitless-runner"
],
"enabled": true
}
}
} openclaw mcp add xpluspro-awaitless --command uvx --arg awaitless-runner
mcp_servers:
xpluspro-awaitless:
command: "uvx"
args: ["awaitless-runner"] {
"mcpServers": {
"xpluspro-awaitless": {
"command": "uvx",
"args": [
"awaitless-runner"
]
}
}
} 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.
- 20 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Aug 26 +1
- Stability: 0.27 → unverified ▼ security
- Malware scan: pass → unverified ▼ security
- Schema quality: 67 → 86 ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: pass → fail ▼ functional
- First check of Schema quality: unverified functional
- Schema quality: fair → good functional
- Package version: 0.4.0 → 0.8.0 functional
- Package version: 0.4.0 → 0.7.0 functional
- 17 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Aug 26 +15
- Malware scan: unverified → pass ▲ security
- Security disclosure: unverified → fail ▼ functional
- 11 Aug 26 −12
- Malware scan: pass → unverified ▼ security
- Schema quality: 506 → 610 ▼ functional
- Security disclosure: fail → unverified ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Package version: 0.3.0 → 0.4.0 functional
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 10 Aug 26 58
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 20 Aug 2026 · Analysed pypi/awaitless-runner@0.8.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Dependencies 31 packages
| Packages resolved | 31 |
|---|---|
| Stale | 1 |
| No linked repository | 1 |
| Tree resolution | Complete |
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.
cancel_job ~37
Cancel a durable job without relying on a client-side process handle.
| Name | Type | Req | Description |
|---|---|---|---|
| grace_seconds | number | – | – |
| job_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
create_queue ~34
Create an immutable named FIFO queue with a fixed concurrency limit.
| Name | Type | Req | Description |
|---|---|---|---|
| concurrency | integer | yes | – |
| name | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_job_logs ~99
Inspect bounded stdout and stderr tails for a known failed or stalled job. Use after a terminal wait reports failure, timeout, stall, or loss and its bounded result needs focused diagnostics. Do not use as a progress stream, do not repeatedly tail a running healthy Job, and do not use it instead of wait_for_job to learn that work completed.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
| max_bytes | – | – | – |
| tail | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_job_status ~83
Get one immediate, non-waiting state snapshot for a known job_id. Use only when the caller needs current status now. Do not use this to wait for completion or build a polling loop; use wait_for_job for one Job or wait_for_completions for several. This tool never starts or retries work.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_jobs ~42
List recent durable jobs, optionally filtered by state or host.
| Name | Type | Req | Description |
|---|---|---|---|
| host | – | – | – |
| limit | integer | – | – |
| queue | – | – | – |
| state | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_queues ~21
List named queues and their current queued/active job counts.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
run ~248
Default tool for starting one non-interactive command of uncertain duration. Every command is a durable Job from launch. Commands that finish within the inline timeout return their ordinary bounded result. Longer or queued work returns a detached Job handle without cancelling the workload. Omit queue to use an operator-configured default queue for the selected target. Do not use this tool for explicit fire-and-forget or batch fan-out; use submit_job. Do not use it when an MCP Tasks handle is explicitly required; use run_job. Do not use it to resume an existing job_id; wait for or inspect that job instead. If a detached handle is returned, keep its job_id and call wait_for_job once when the result is needed rather than polling status.
| Name | Type | Req | Description |
|---|---|---|---|
| artifacts | – | – | – |
| backend | – | – | – |
| capture_logs | – | – | – |
| client_request_id | – | – | – |
| command | array | yes | – |
| cwd | – | – | – |
| env | – | – | – |
| host | – | – | – |
| inline_timeout_seconds | – | – | – |
| name | – | – | – |
| queue | – | – | – |
| resources | – | – | – |
| slurm_options | – | – | – |
| stall_timeout_seconds | – | – | – |
| timeout_seconds | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
run_job ~189
MCP Tasks compatibility entry point for explicitly creating a Task handle. A client declaring io.modelcontextprotocol/tasks receives a Task handle immediately. Older clients block and receive the ordinary final tool result. The stable client_request_id makes a lost creation response safe to retry. Do not choose this for ordinary command execution: use run. Do not choose it for generic asynchronous submission or fan-out: use submit_job. Only retry a lost Task creation with the same client_request_id and identical arguments.
| Name | Type | Req | Description |
|---|---|---|---|
| artifacts | – | – | – |
| backend | – | – | – |
| capture_logs | – | – | – |
| client_request_id | string | yes | – |
| command | array | yes | – |
| cwd | – | – | – |
| env | – | – | – |
| host | – | – | – |
| name | – | – | – |
| queue | – | – | – |
| resources | – | – | – |
| slurm_options | – | – | – |
| stall_timeout_seconds | – | – | – |
| timeout_seconds | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
submit_job ~269
Explicitly submit one asynchronous or fan-out job without waiting. Omitted backend and host values use the Awaitless configuration defaults. Reuse client_request_id only when retrying the same logical submission; an identical retry returns the original job and a conflicting retry is rejected. A named queue provides FIFO, non-preemptive admission for local or SSH work. Slurm options may contain account, constraint, cpus_per_task, gres, mem, nodes, ntasks, partition, qos, or time. Cluster config supplies defaults. Do not use this as the default for a single command with uncertain duration; use run. Do not use it for MCP Tasks creation; use run_job. Do not resubmit merely because a client disconnected or a wait timed out: keep the original job_id, or retry the identical logical submission with the same client_request_id if the creation response was lost.
| Name | Type | Req | Description |
|---|---|---|---|
| artifacts | – | – | – |
| backend | – | – | – |
| capture_logs | – | – | – |
| client_request_id | – | – | – |
| command | array | yes | – |
| cwd | – | – | – |
| env | – | – | – |
| host | – | – | – |
| name | – | – | – |
| queue | – | – | – |
| resources | – | – | – |
| slurm_options | – | – | – |
| stall_timeout_seconds | – | – | – |
| timeout_seconds | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
wait_for_completions ~168
Collect durable terminal results across multiple known jobs after a cursor. Existing completions return immediately. Otherwise the call waits until at least one selected job completes or the optional call-level timeout expires. Reusing the same cursor replays results; advancing to next_cursor consumes the returned batch. A timeout never cancels a managed job. Submit all independent jobs before calling this tool. Treat delivery as at-least-once: process and deduplicate by completion_id before advancing the cursor. Do not use this for one job, do not poll get_job_status between continuation calls, and never resubmit active jobs after a waiter disconnects.
| Name | Type | Req | Description |
|---|---|---|---|
| after_cursor | – | – | – |
| job_ids | array | yes | – |
| limit | integer | – | – |
| timeout_seconds | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
wait_for_job ~105
Wait once for a known job_id and consume its durable terminal result. Returns state, exit code, bounded logs, and declared Artifacts. A client-side timeout or disconnect does not cancel the Job; call this tool again later with the same job_id. Do not use it to start work, do not poll it repeatedly, and use wait_for_completions instead when collecting several independent Jobs.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
| timeout_seconds | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.