"Task" matching MCP tools:

• task-analysisA

  MeshMarketB

  Task Analysis — Hand a task, get a structured plan back — typed steps, risks, and a go/caution/no-go verdict. Runs claude-haiku-4.5 — the response names the model that served the call. Input: {task: string}. Returns {analysis: {summary, steps, risks, verdict}, model}. (5 MESH/call, a tool · reasoning)

  ConnectorNo auth

• list-task-classificationsA

  OpenRouterA

  See what OpenRouter traffic is actually used for: a market-share breakdown by task type (code generation, web search, summarization, ...) over a trailing window, each with its top models by usage, plus macro-category (Code, Data, Agent, General) aggregates. Use to learn which models real usage favors for a given kind of work. All shares are fractions (0-1) of sampled traffic; absolute volumes are not exposed.

  ConnectorOAuth

• task-orchestrateC

  MeshMarketB

  Task Orchestrate — Break a multi-step task into an execution plan any agent can follow. Powered by api.meshtool.ai. Input: { task: string, tools: array }. (3 MESH/call, a tool · reasoning)

  ConnectorNo auth

• x402-task-routerD

  minia2a-mcpD

  Task Router: Route a task to the right service.

  ConnectorNo auth

• Get-Running-Task-StatusA

  YouCam for CreatorsC

  Retrieves the current status and results of a previously initiated AI processing task. Use this tool when you need to check on a task that was started earlier but hasn't completed yet, or when a user returns to inquire about a task they initiated previously. WHEN TO USE THIS TOOL: - When a user provides a task_id from a previous session and wants to check if their result is ready - When a user asks about a task they started earlier (e.g., 'Is my hairstyle ready?', 'Check my previous request') - When resuming a conversation where a task was left processing - When a task exceeded the initial polling timeout and the user wants to see if it has completed

  ConnectorNo auth

• Get-Running-Task-StatusA

  YouCam for Beauty & Personal CareC

  Retrieves the current status and results of a previously initiated AI processing task. Use this tool when you need to check on a task that was started earlier but hasn't completed yet, or when a user returns to inquire about a task they initiated previously. WHEN TO USE THIS TOOL: - When a user provides a task_id from a previous session and wants to check if their result is ready - When a user asks about a task they started earlier (e.g., 'Is my hairstyle ready?', 'Check my previous request') - When resuming a conversation where a task was left processing - When a task exceeded the initial polling timeout and the user wants to see if it has completed

  ConnectorNo auth

• Get-Running-Task-StatusA

  YouCam for Fashion & RetailB

  Retrieves the current status and results of a previously initiated AI processing task. Use this tool when you need to check on a task that was started earlier but hasn't completed yet, or when a user returns to inquire about a task they initiated previously. WHEN TO USE THIS TOOL: - When a user provides a task_id from a previous session and wants to check if their result is ready - When a user asks about a task they started earlier (e.g., 'Is my hairstyle ready?', 'Check my previous request') - When resuming a conversation where a task was left processing - When a task exceeded the initial polling timeout and the user wants to see if it has completed

  ConnectorNo auth

• submit_human_taskA

  Human For AIA

  Submit a task for the human operator to perform in the real world. Returns a task_id immediately; the human reviews every task before accepting it (this is not instant execution). The operator is push-notified on submission; check_task_status shows seen_by_operator_at once a human has seen the task. Free during the pilot. contact_email must be a real mailbox (MX-checked) — it is how the deliverable reaches you. No mailbox? Set delivery to 'status_poll' instead: the deliverable arrives as text in operator_notes via check_task_status (limited to 1 such task per client per day).

  ConnectorNo auth

• delete_taskA

  PlateA

  Permanently delete a task. Comments and attachments are removed automatically. The taskId is the internal document ID from list_tasks — NOT the public task number (e.g. SCD-408).

  Connector

  Destructive

  OAuth

• approve_physical_task_completionA

  Molt2MeetA

  Approve a completed task — SIMPLE FLOW ONLY. Precondition: the task was dispatched with publishImmediately=true (default) AND auto-funded from your wallet, i.e. you did NOT call request_task_quote/fund_task/publish_task (escrow flow). If you went through the escrow flow (any of those three tools), call approve_task_review instead — calling this on an escrow task returns an error with the correct tool to use. Mechanism: marks the task Completed and triggers the operator payout immediately. There is no review window for the simple flow. Task must be in ProofUploaded or UnderReview status. Requires: API key from register_agent. Next: monitor task.settled and task.closed via get_task_events — settlement happens automatically.

  ConnectorNo auth

• delete_use_caseA

  InterbangA

  Delete a use case from a draft UT, including every task inside it. Irreversible — check the useCaseId and its task list (from get_ut) before calling; prefer delete_task when you only mean to remove a single task. Only works on PREPARING drafts.

  Connector

  Destructive

  OAuth

• publish_taskA

  Molt2MeetA

  Publish a task to make it visible to operators. Works for both settlementMode='escrow' and 'direct' tasks. The task must be in Draft or Funded status. For escrow Draft tasks: funds are automatically reserved and locked from your wallet (requires sufficient balance). For direct-settlement Draft tasks: no funding happens — the task goes directly from Draft to Published because the client pays the operator on-site (no escrow). This is the intended shortcut for direct-settlement. For Funded tasks (after escrow Quote → Fund flow): the funds are already locked, the task is simply made visible. After publishing, operators can accept the task. Requires authentication. Next: wait for task.accepted via get_task_events or webhook.

  ConnectorNo auth

• complete_taskA

  PlateA

  Mark an existing task as completed or reopen it. Use this instead of create_task when the task already exists and you only need to change its completion state. The taskId is the internal document ID from list_tasks — NOT the public task number (e.g. SCD-408). To resolve a public number to an internal ID, call list_tasks with workspaceId + number first.

  ConnectorOAuth

• cancel_taskA

  AgentMarketplaceA

  Cancel a task you posted. Only legal before bidding/assignment closes it out. Args: access_token: AgentAuth bearer token (requires ``market.post``). task_id: UUID of the task to cancel. Returns: The cancelled task on success. ``{"error_code": "not_found", ...}`` if the task doesn't exist, ``{"error_code": "authorization_failed", ...}`` if you're not the poster, or ``{"error_code": "invalid_input", ...}`` if the task is already past the cancellable stage.

  ConnectorNo auth

• submit_bidA

  AgentMarketplaceA

  Bid on an open task. Args: access_token: AgentAuth bearer token (requires ``market.bid``). task_id: UUID of the task to bid on. proposed_cost_units: Your price, as an **integer** amount_units. Never a float or Decimal — money is integer units end to end. estimated_duration_seconds: How long you expect the work to take. proposed_approach: Free-text summary of how you'll do the work. terms: Optional JSONB — anything else worth stating up front. confidence_score: Your self-assessed confidence, 0.0-1.0. Returns: The created bid (status ``"pending"``). The task moves to ``"bidding"`` on its first bid. Errors: ``not_found`` (no such task), ``invalid_input`` (bidding on your own task, past bid_deadline, an existing pending bid, or a task not open for bidding).

  ConnectorNo auth

• review_resultA

  AgentMarketplaceA

  Review the assignee's latest submitted result. One tool, three actions — not three tools (PLAN.md §5). - ``accept``: task -> completed. Response includes a ``report_interaction_hint`` — file your own AgentTrust report_interaction for mutual confirmation (PLAN.md §7.4); the marketplace already files its own first-party report. - ``reject``: task -> failed (terminal — not a revision request). Response includes both a ``report_interaction_hint`` (outcome ``"failure"``) and a ``file_dispute_hint``. - ``request_revision``: task -> in_progress. The assignee resubmits via ``submit_result``. Args: access_token: AgentAuth bearer token (requires ``market.post``). task_id: UUID of the task under review. action: One of ``accept``, ``reject``, ``request_revision``. reviewer_notes: Optional free-text feedback, recorded on the result. Returns: ``{"task": ..., "result": ...}`` plus hints on accept/reject. Errors: ``not_found`` (no task, or no submitted result to review), ``authorization_failed`` (not the task's poster), ``invalid_input`` (unknown action or task not in ``review``), ``rate_limit_exceeded``.

  ConnectorNo auth

• approve_task_reviewA

  Molt2MeetA

  ESCROW FLOW ONLY. For direct-settlement tasks (settlementMode='direct') use acknowledge_direct_settlement_task instead — this endpoint returns 400 with a pointer when called on a direct task. Approve a completed task after reviewing the proof. Triggers payout to the operator. The task must be in UnderReview status AND settlementMode='escrow'. Funds move from locked to earned. Requires authentication.

  ConnectorNo auth

• cancel_scheduled_taskA

  Valuein — SEC EDGAR Fundamentals & Smart-Money DataA

  Cancel a pending scheduled task by id (from schedule_task or list_scheduled_tasks). Only a `pending` task can be cancelled — one that already woke (completed) cannot be un-woken. Idempotent: cancelling an already-cancelled task is a no-op. Tier: sp500+ (sample rejected).

  Connector

  Destructive

  No auth

• twprojects-move_tasksA

  mcpC

  Move tasks and all their subtasks to another tasklist, preserving the parent/child structure. Subtasks move with their parent automatically, so only the topmost task of each subtree needs to be listed. A task whose parent is not part of the move is detached from it, becoming a top-level task in the destination.

  ConnectorNo auth

• task_editA

  Done Bear MCPA

  Update fields on one task (`task`) or on several at once (`tasks`, max 50). Only the provided fields are changed; omitted fields are left untouched. To remove a value, list the field in `clear` (e.g. `clear: ["deadline"]`). Notes replace the existing notes (no append). `assignee` assigns the task; clear it to unassign. `add_labels` and `remove_labels` change which labels are on it. Editing several tasks applies the same changes to every one of them and cannot be undone in one call, so confirm the list with the user first.

  ConnectorNo auth

• get_study_planA

  Fiveable for AP StudentsA

  Reads one owned study plan, stable task ids, completion state and revision. Use its revision for task changes. Reading older plans never changes them.

  ConnectorNo auth