Skip to main content
Glama
task-relay-discovery-mcp

task-relay-discovery-mcp

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

Related MCP server: PreFlight

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

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)

npm install
npm run build
node dist/index.js

Run HTTP (remote)

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.

Available Tools

3 tools
find_task_relay_jobA

Find Task Relay F1-F5 contracts matching a machine need (deterministic local match only; Task Relay jobs only)

Inputs: machine_need (required), max_price_usdc.

get_task_relay_job_contractA

Get exact public Task Relay job contract for F1-F5 (discovery only)

Inputs: franchise_id (required).

list_task_relay_jobsB

List Task Relay F1-F5 paid job contracts (discovery only; does not execute jobs)

Inputs: task_type, max_price_usdc.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct verb (find, get, list) targeting different operations: matching a need, retrieving a specific contract, and listing all contracts. No overlap.

    Naming Consistency5/5

    All names follow a consistent verb_noun pattern in snake_case: find_task_relay_job, get_task_relay_job_contract, list_task_relay_jobs.

    Tool Count5/5

    Three tools is well-scoped for a discovery-focused server. Each tool serves a specific and necessary purpose without redundancy.

    Completeness5/5

    The tool set covers the core discovery operations: finding by need, retrieving details, and listing all contracts. No obvious gaps for the stated 'discovery only' scope.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers