# task-relay-discovery-mcp

Discovery-only MCP server for **Task Relay** F1–F5 paid x402 machine jobs.

## Hard boundary

This server **does not**:

- execute F1–F5 work
- proxy Task Relay payment
- hold wallets or private keys
- call arbitrary URLs/APIs
- expose tools beyond the three listed below

## Tools (exactly three)

1. `list_task_relay_jobs`
2. `find_task_relay_job`
3. `get_task_relay_job_contract`

## Machine flow

1. Agent has a **machine need** (example: extract plain text from a public PDF).
2. Agent calls `find_task_relay_job` with that need.
3. Agent receives a Task Relay paid contract (resource, price, schema, automatic next actions).
4. Agent (or its existing x402 buyer client) POSTs to the exact `resource` URL and settles x402.
5. Agent consumes the strict result and continues automatically.

## Example

```text
MACHINE_NEED: extract plain text from PDF for indexing
→ find_task_relay_job({ machine_need: "extract plain text from PDF for indexing" })
→ candidate F2 resource https://task-relay-production.up.railway.app/x402/pdf-text price 0.01 USDC
→ buyer client pays x402 and POSTs { "url": "https://example.org/doc.pdf" }
→ automatic next action INDEX_TEXT | INGEST_TEXT | SKIP_NO_TEXT
```

## Run stdio (local)

```bash
npm install
npm run build
node dist/index.js
```

## Run HTTP (remote)

```bash
npm run build
npm run start:http
```

`POST /mcp` is the streamable HTTP MCP endpoint. `GET /health` is status only.

## Claims not made

No organic demand, market validation, reliability percentages, or “best” claims.