dsh-lines

Readme

# dsh-lines

Turn a sequence of tool calls that already works into a named pipeline that runs on our servers on a schedule, with a receipt per run — plus recurring watch tasks that notify you only when a result actually changes.

## What & why

The case for this is narrow and worth stating plainly: it is only worth it when the same steps have to run **repeatedly and unattended**. If you run something once, call the tools directly — you do not need this. What you get instead of an open session is: it keeps running when your machine is off, each run produces a checkable receipt, and steps chain by `$prev.field` so the second step reads the first one's output.

Every set ships `what_can_you_do` — describe a task in any language, get the exact tool plus a ready-to-run call.

<!-- TOOLS:BEGIN -->
## What's in this pack

9 tools, read from the live endpoint on 2026-08-22 — **this table is generated, not hand-written**, so it cannot drift away from what `tools/list` actually returns. The **Arguments** column is what the tool genuinely reads; it comes from the tool's own declared input schema.

| Tool | What it does | Arguments | Price / call |
|---|---|---|---|
| `what_can_you_do` | Describe a task in plain language (any language) and get back exactly which tools on this server do it, with ready- | `task` | — |
| `create_pipeline` | Turn the tool calls you just made into a repeatable pipeline that runs on our servers. Each run produces a work ord | `name`, `steps` | — |
| `run_pipeline` | Execute one of your pipelines immediately and get the work order (per-step results and proofs). The scheduler calls | `id` | — |
| `list_pipelines` | Pipelines on this workspace: steps, trial/paid status, run counts, work-order pages. | — (no arguments) | — |
| `delete_pipeline` | Remove a pipeline. Its scheduled task (if any) will start failing — delete that too. | `id` | — |
| `create_task` | Create a task that runs on a schedule in our cloud — you do not keep anything running. It only notifies you when th | `kind`, `input`, `interval_seconds`, `notify_url` | — |
| `list_tasks` | Show the scheduled tasks on this workspace, when each runs next, how many times it has run and what it has cost so  | — (no arguments) | — |
| `get_task_runs` | Recent runs of one scheduled task: what it returned, whether the result changed, and what each run cost. | `task_id`, `limit` | — |
| `delete_task` | Stop and remove a scheduled task and its run history. | `task_id` | — |

`—` in the price column means the tool is not metered per call (session/trial-gated instead). Failed calls are never charged. Check it yourself:

```sh
curl -s -X POST https://ainetcafe.com/mcp/lines -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
```
<!-- TOOLS:END -->

## Install

```sh
dsh plugin --profile <your-profile> add github:mario03690/dsh-lines
```

Thin config layer only (one `@deepseek-ai/dsh-mcp-client` row, shipped as `cordis.patch.yml`) — no tool code runs on your machine. Built against the MCP client config shape of the dsh v0.1 developer preview; verified against the live endpoint on 2026-08-22.

## Cost, quota, privacy

Trial: 7 days or 60 runs, whichever comes first, then a subscription. Runs that fail their own self-check are not counted against your usage. `create_task` watch jobs (e.g. daily China-reachability for 30 days) are separate and free.

No signup for the free anonymous quota. Documents are processed in memory and not retained. The config URL carries `?s=dsh-lines` — a channel tag identifying the install path, not you.

**Disclosure:** built and run by the team behind [ainetcafe.com](https://ainetcafe.com) — our own service, free tier plus paid usage. Full bundle (everything at once): [dsh-netcafe](https://github.com/mario03690/dsh-netcafe). MIT.

## Compatibility & permissions (at a glance)

| Signal | This plugin |
| --- | --- |
| **Runtime** | dsh v0.1 developer preview (Cordis v4). Touches only the MCP client config shape — the narrowest surface available. Verified against a live endpoint on 2026-08-22. |
| **What runs locally** | Nothing. Ships one `cordis.patch.yml` row; there is no tool code, no build step and no lifecycle script in this package. |
| **Filesystem access** | None. |
| **Shell / process access** | None. |
| **Network access** | Outbound HTTPS to `ainetcafe.com` only, from the MCP client that dsh already ships. |
| **Credentials** | None required for the free tier. An optional AllRouter key, if you supply one, is sent by dsh as a request header and is never stored by us. |
| **Data retention** | Documents and prompts are processed in memory and not retained. |
| **Dependencies** | One peer dependency: `@deepseek-ai/dsh-mcp-client` (ships with dsh). |
| **License** | MIT (see `LICENSE`). |
| **Publisher** | The team that runs [ainetcafe.com](https://ainetcafe.com). Issues get a same-day reply. |

> A directory listing is not a security review. Read `cordis.patch.yml` — it is short enough to read in full in under a minute.