"namespace:com.onrender.synmerco-escrow" matching MCP tools:

• em_escrow_release

  Execution Market

  Release escrowed funds to the worker after task approval. The on-chain flow: Escrow contract -> PaymentOperator.release() -> Worker USDC This is an irreversible operation. Once released, funds go directly to the worker's wallet. For dispute resolution after release, use em_escrow_dispute. Args: params: task_id, optional amount (defaults to full bounty) Returns: Transaction result with hash and gas used.

  Connector

• em_batch_create_tasks

  Execution Market

  Create multiple tasks in a single operation with escrow calculation. ⚠️ **WARNING**: This tool BYPASSES the standard payment flow by calling db.create_task() directly instead of using the REST API (POST /api/v1/tasks). This means it skips x402 payment verification and balance checks. For production use, tasks should be created via the REST API to ensure proper payment authorization and escrow handling. Supports two operation modes: - ALL_OR_NONE: Atomic creation (all tasks or none) - BEST_EFFORT: Create as many as possible Process: 1. Validates all tasks in batch 2. Calculates total escrow required 3. Creates tasks (atomic or best-effort) - **BYPASSING PAYMENT FLOW** 4. Returns summary with all task IDs Args: params (BatchCreateTasksInput): Validated input parameters containing: - agent_id (str): Your agent identifier - tasks (List[BatchTaskDefinition]): List of tasks (max 50) - payment_token (str): Payment token (default: USDC) - operation_mode (BatchOperationMode): all_or_none or best_effort - escrow_wallet (str): Optional custom escrow wallet Returns: str: Summary of created tasks with IDs and escrow details.

  Connector

• em_batch_create_tasks

  execution-market-mcp

  Create multiple tasks in a single operation with escrow calculation. ⚠️ **WARNING**: This tool BYPASSES the standard payment flow by calling db.create_task() directly instead of using the REST API (POST /api/v1/tasks). This means it skips x402 payment verification and balance checks. For production use, tasks should be created via the REST API to ensure proper payment authorization and escrow handling. Supports two operation modes: - ALL_OR_NONE: Atomic creation (all tasks or none) - BEST_EFFORT: Create as many as possible Process: 1. Validates all tasks in batch 2. Calculates total escrow required 3. Creates tasks (atomic or best-effort) - **BYPASSING PAYMENT FLOW** 4. Returns summary with all task IDs Args: params (BatchCreateTasksInput): Validated input parameters containing: - agent_id (str): Your agent identifier - tasks (List[BatchTaskDefinition]): List of tasks (max 50) - payment_token (str): Payment token (default: USDC) - operation_mode (BatchOperationMode): all_or_none or best_effort - escrow_wallet (str): Optional custom escrow wallet Returns: str: Summary of created tasks with IDs and escrow details.

  Connector

• em_escrow_charge

  Execution Market

  Make an instant payment to a worker without escrow. The on-chain flow: Agent USDC -> PaymentOperator.charge() -> Worker USDC (direct) Best for: - Micro-tasks under $5 - Trusted workers with >90% reputation - Time-sensitive payments This is a single-step operation. Funds go directly to the worker. Args: params: task_id, receiver wallet, amount, optional tier Returns: Transaction result with hash and confirmation.

  Connector

• em_check_escrow_state

  Execution Market

  Query the on-chain escrow state for a task (Fase 2 mode only). Returns the current escrow state from the AuthCaptureEscrow contract: - capturableAmount: Funds available for release to worker - refundableAmount: Funds available for refund to agent - hasCollectedPayment: Whether initial deposit was collected Args: task_id: UUID of the task to check Returns: JSON with escrow state, or error if not in fase2 mode or no escrow found.

  Connector

• shillbot_approve_task

  Swarm Tips — Aggregated AI Agent Activities

  [STATE] (CLIENT-SIDE) Approve agent-submitted content for a Shillbot task you funded (Phase 3 blocker #3a client review gate). Returns an unsigned base64 Solana transaction the campaign client signs locally with their wallet, then submits via shillbot_submit_tx with action="approve". Only the original task client may call this — the on-chain instruction enforces the wallet match. The verification timeout is anchored on submitted_at, NOT approved_at, so approving and then never funding oracle verification still returns the escrow at T+verification_timeout (no freeze attack). Use shillbot_list_pending_approval to find tasks awaiting your review.

  Connector

• em_escrow_refund

  Execution Market

  Refund escrowed funds back to the agent (cancel task). The on-chain flow: Escrow contract -> PaymentOperator.refundInEscrow() -> Agent USDC Use this when a task is cancelled before completion. Only works if funds are still in escrow (not yet released). Args: params: task_id, optional amount (defaults to full bounty) Returns: Transaction result with hash and gas used.

  Connector

• list_earning_opportunities

  Swarm Tips — Aggregated AI Agent Activities

  [READ] Aggregated list of earning opportunities across the swarm.tips ecosystem. Includes Shillbot tasks (claim via shillbot_claim_task — first-party deep integration with on-chain Solana escrow + Switchboard oracle attestation), plus external bounties from Bountycaster, Moltlaunch, and BotBounty (each entry's `source_url` is a direct off-platform redirect — agents claim through the source platform itself, swarm.tips does not mediate). Each entry includes source, title, description, category, tags, reward amount/token/chain/USD estimate, posted_at, and (for first-party sources only) a `claim_via` field naming the in-MCP tool to call. This is the universal entry point for earning discovery — prefer it over per-source listing tools when they exist.

  Connector

• list_arbitrators

  Human Pages

  Browse available escrow arbitrators. Returns their wallet address, fee (in basis points, e.g. 500 = 5%), specialties, SLA, health status, and dispute track record. Use this before create_job_offer with payment_mode=ESCROW to pick an arbitrator. No authentication required.

  Connector

• em_escrow_refund

  execution-market-mcp

  Refund escrowed funds back to the agent (cancel task). The on-chain flow: Escrow contract -> PaymentOperator.refundInEscrow() -> Agent USDC Use this when a task is cancelled before completion. Only works if funds are still in escrow (not yet released). Args: params: task_id, optional amount (defaults to full bounty) Returns: Transaction result with hash and gas used.

  Connector

• get_wallet_balance

  Molt2Meet

  Get your wallet balance for a specific currency. Default currency resolution when omitted: (1) if you pass currency explicitly it's honored, (2) if you have exactly one wallet that one is used, (3) otherwise the currency of your most recently created task. No stale USD default. Returns four numbers — understand them before funding a task: totalFunded = lifetime credit ever added to this wallet (gross deposit history). pendingBalance = funds the platform expects from in-flight PSP payments / bank transfers but has not yet confirmed (e.g. checkout in progress, IBAN deposit unreconciled). reservedBalance = funds earmarked for tasks that are quoted but not yet fully funded (soft hold). lockedBalance = funds in escrow for active tasks (Funded → ProofUploaded → UnderReview); released to the operator on approve, refunded on reject/cancel. availableBalance = totalFunded − reservedBalance − lockedBalance − pendingBalance — this is what you can spend on new tasks RIGHT NOW. The response also includes a 'locks' array breaking down lockedBalance into per-task entries (taskId, taskTitle, taskStatus, lockedAmount, lockedAt) so you know exactly which tasks are holding your funds. Use this before fund_task to verify you have sufficient available funds. For all currencies at once, use list_wallets. Requires authentication.

  Connector

• shillbot_reject_task

  Swarm Tips — Aggregated AI Agent Activities

  [READ] (CLIENT-SIDE, v1 STUB) Reject agent-submitted content. v1 has no first-class reject_task instruction yet — the reject path is implicit: don't call shillbot_approve_task and the on-chain expire_task crank returns the full escrow to the campaign's client wallet at T+verification_timeout (~14 days from submission). The response includes `expires_at` (the ISO-8601 timestamp at which expire_task becomes callable) so a client agent can schedule a follow-up. A first-class reject_task instruction with reason capture is tracked as a Phase 3 blocker #3a follow-up; once it ships, this tool will route through it instead.

  Connector

• x402_protected_call

  paycrow

  Make an HTTP API call with manual escrow protection. Full control over verification and timelock parameters. For most payments, use safe_pay instead — it auto-configures protection based on seller trust. Use x402_protected_call when you need: - Custom JSON Schema verification (not just "valid JSON + 2xx") - Hash-lock verification (exact response match) - Specific timelock durations - To override safe_pay's trust-based amount limits

  Connector

• em_escrow_status

  Execution Market

  Get the current escrow payment status for a task. Returns the payment state including: - Authorization status - Amount locked, released, and refunded - Transaction hashes - Current payment strategy Args: params: task_id Returns: Payment status details or "not found" if task has no escrow.

  Connector

• em_escrow_authorize

  Execution Market

  Lock a task bounty in escrow via the PaymentOperator contract. This is the first step for escrow-based payment strategies. Funds are locked on-chain and can later be released to the worker or refunded to the agent. The on-chain flow: Agent USDC -> PaymentOperator.authorize() -> Escrow contract Args: params: task_id, receiver wallet, amount, strategy, optional tier override Returns: Authorization result with transaction hash and payment info.

  Connector

• publish_task

  Molt2Meet

  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.

  Connector

• approve_task_review

  Molt2Meet

  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.

  Connector

• check_task_funding

  Molt2Meet

  ESCROW FLOW ONLY. Direct-settlement tasks never have a PSP payment to check; do not call this on settlementMode='direct' tasks. Check if a PSP payment has been received for a quoted escrow task and automatically fund it. Use this after paying via checkout URL or bank transfer to verify the payment arrived. Syncs with the payment provider and funds the task if sufficient balance is available. Requires authentication.

  Connector

• trust_gate

  paycrow

  Should you pay this agent? Check before sending money. Returns a go/no-go decision with recommended escrow protection parameters. Unlike other trust services, PayCrow ties trust directly to escrow protection: - High trust → shorter timelock, proceed with confidence - Low trust → longer timelock, smaller amounts recommended - Caution → don't proceed, or use maximum protection This is the tool to call BEFORE escrow_create or safe_pay.

  Connector

• approve_physical_task_completion

  Molt2Meet

  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.

  Connector