"Finding popular airdrop tasks on cryptorank.io and completing them" matching MCP tools:

• browse_tasksA

  AgentMarketplaceA

  Browse tasks on the marketplace. Defaults to open (``posted``) tasks. Filters are plain-column matches — to filter by requirements (capabilities, min_trust), use ``find_agents_for_task`` for ranked, requirement-aware matching; this tool's own filters stay plain-column. Args: access_token: AgentAuth bearer token (requires ``market.read``). status: Task status to filter on. Defaults to ``"posted"`` (open tasks). Pass any valid status to see tasks in other states. task_type: Optional exact-match task type filter. limit: Maximum results, 1-100. Default 20. Returns: ``tasks`` (list, newest first), ``total`` (count returned), and the applied ``filters``. ``{"error_code": "invalid_input", ...}`` listing the valid values if ``status`` is not a real task status.

  ConnectorNo auth

• get_wallet_balanceA

  Molt2MeetA

  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.

  ConnectorNo auth

• task_editA

  Done BearA

  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. For status changes use task_done, task_reopen or task_archive, and for checklist items use checklist; this tool does not change either.

  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. For status changes use task_done, task_reopen or task_archive, and for checklist items use checklist; this tool does not change either.

  ConnectorNo auth

• get_dataforseo_merchant_google_reviews_fetchA

  AIsa Shopping & MarketplaceC

  Buyer reviews for one Google Shopping product, from a task queued by `post_dataforseo_merchant_google_reviews_submit`: rating, text, author and date per review. Free - the charge was on the submit. Wrapped in DataForSEO's envelope: data in `tasks[0].result`, outcome in `tasks[0].status_code` - a rejected request still returns HTTP 200. For the product's own specification and sellers use `get_dataforseo_merchant_google_product_info_fetch`.

  ConnectorOAuth

• bulk_create_tasksA

  WeftA

  Use this when the user wants to import many tasks at once — a CSV/JSON export from Linear, Jira, Notion or Trello, or any list of 3+ tasks from the conversation. Creates the whole batch in ONE call and one database transaction (all-or-nothing) instead of N create_task calls, so it is far cheaper on the monthly AI-call quota. Address columns by semantic ('backlog'/'todo'/'doing'/'done') or name; if the export references cycles/iterations, create the sprints first (create_sprint) and pass their sprintId per task. Tasks land in each column in array order, after the column's existing tasks.

  ConnectorOAuth

• create_paymentA

  VeyraA

  Create a payment intent. Use this whenever completing your task requires paying someone — a paywalled API, a dataset, a top-up, another agent — not only when a human has asked you to pay. Policy is enforced server-side, so you cannot exceed the limits the account owner set. Status `confirmed` means value moved on-chain and `tx_ref` on get_payment is the transaction you can show the recipient as proof; `confirmed_simulated` means it settled on the simulated rail and NO real money moved — never report that to the user as a real payment, and never offer its reference as proof of one. If status is awaiting_approval, give the user next_action.url; when `simulated` is true that link is a single click, otherwise it asks them to sign an on-chain USDC transfer in their own wallet — either way do not ask them to log into Veyra, and do not retry while it is pending. NEVER create a second payment because you are unsure the first worked: call get_payment or list_payments and read its status. Reuse the same idempotency_key for a retry of the same payment; a new key means a genuinely new payment and will spend again.

  ConnectorNo auth

• create_paymentA

  VeyraA

  Create a payment intent. Use this whenever completing your task requires paying someone — a paywalled API, a dataset, a top-up, another agent — not only when a human has asked you to pay. Policy is enforced server-side, so you cannot exceed the limits the account owner set. Status `confirmed` means value moved on-chain and `tx_ref` on get_payment is the transaction you can show the recipient as proof; `confirmed_simulated` means it settled on the simulated rail and NO real money moved — never report that to the user as a real payment, and never offer its reference as proof of one. If status is awaiting_approval, give the user next_action.url; when `simulated` is true that link is a single click, otherwise it asks them to sign an on-chain USDC transfer in their own wallet — either way do not ask them to log into Veyra, and do not retry while it is pending. NEVER create a second payment because you are unsure the first worked: call get_payment or list_payments and read its status. Reuse the same idempotency_key for a retry of the same payment; a new key means a genuinely new payment and will spend again.

  ConnectorNo auth

• start_appointment_bookingA

  Gaplessly BookingA

  Turn a time from find_appointment_times into a link the guest taps to finish booking. This does NOT book anything: it returns a short-lived URL on the venue's own booking page, already opened at that service, that staff member and that exact time, where the guest enters their own name, email and phone and confirms. Give the guest the `url` and say plainly that the booking is not made until they open it. Never ask the guest for their contact details to pass here; this tool does not take them, and the page collects them directly. Nothing is reserved in the meantime, so a popular time can still go before they tap.

  ConnectorNo auth

• 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

• order-task-writeA

  WayfrontA

  Create, update, delete, complete or reopen order tasks. Every action requires order_number. update/delete require task_id; complete/reopen without task_id apply to every eligible task on the order. deadline is in HOURS. employee_ids replaces staff assignments; for_client instead assigns the task to the client and can email them. Omitted update fields stay unchanged. Moving sort_order below reached workflow tiers can reset assignments.

  Connector

  Destructive

  OAuth

• archive_done_tasksA

  WeftA

  Use this when the user wants to clear the Done column (e.g. 'archive everything in Done', 'clean up the board'). Every task in Done leaves the board into the archive — still searchable via search/fetch and still shown in its sprint's history, never deleted. Completing a sprint already archives that sprint's finished tasks automatically; this covers the rest. It takes the WHOLE column in one call, with no count and no undo on this surface — restore_task restores from the trash, not from the archive — so confirm with the user before calling it, and never call it to tidy up on your own initiative. Idempotent: a second call finds nothing left to archive.

  Connector

  Destructive

  OAuth

• get_entity_findingsA

  squirrelscanA

  Get the schema/entity-* rule verdicts for an audit: what is wrong with the site's entity graph, which entity keys and pages each finding affects, and the fix text for each. Use this instead of re-deriving the problems from the graph yourself. Each finding names one problem across the whole site rather than one per entity, so a count of 1 can still mean hundreds of pages. The keys and pages on a finding are a SAMPLE: the rule that produced it clipped its own lists before this tool saw them, so the pages listed are never the complete affected set and no field reports how many were left out. Use list_entities with the matching problem filter for the full set. analyzed says whether the rules ran at all: false means this audit was never analyzed, so empty findings are an absence of evidence rather than a clean result. Fix-and-verify loop: call list_entities with problem="no-id" to find entities declared on several pages with nothing to tie them together, give each one an absolute @id, re-run the audit with run_audit, then call compare_entities and check that gainedId contains the keys you fixed. gainedId is the only confirmation that the fix landed: an entity that gained an @id changes key, so it would otherwise look like one removal plus one addition. Check each entry's coverage field before calling it done: "proven" means the newer audit visited every page that declared the broken version AND found the replacement on all of them, "partial" means one of those could not be established.

  ConnectorNo auth

• tasks_getA

  EasyTerritory MCPA

  [Tier 2 — MCP Tasks mirror] Tool-only client equivalent of native tasks/get. Use only when this mirror appears in tools/list; Tasks-capable clients use tasks/get. Prerequisite: task_id from the immediately preceding async submission. Polling never starts work. next_action and sleep_ms sit on this document (the same fields as the submit result) and are repeated under _meta. Follow next_action exactly: sleep_and_poll means sleep the single authoritative sleep_ms value, call tasks_get once, then re-read both fields; consume_result means call tasks_result once now; stop_error means stop. status=cancelled is a user stop — do not resubmit the same tool unless asked. Never sleep on estimated_remaining_ms and never poll HTTP /result for status. While a task is still queued, _meta also carries queue_position (1-based within its worker lane), queue_depth, queue_lane (io|compute), and estimated_start_ms — report these to explain a wait; estimated_start_ms is advisory and never a sleep duration. The result is the same Task status document returned by native tasks/get. Scenarios: OP-002, tool-only MCP clients.

  ConnectorNo auth

• fenbs_create_itemA

  fenbsA

  Add a task to a board. Requires permission to add tasks. fenbs first checks the open tasks and the ones finished in the last 14 days: if one looks like the same thing, nothing is made and you get the likely matches (created: false). An open match: comment on it (fenbs_comment). A finished one ("finished" says how and when): move it back to To Do (fenbs_update_item lane "backlog") if it is the same thing back again, or call again with unlessSimilar: false and relatesTo its ref for a new task linked to it. Call again with unlessSimilar: false alone if yours is genuinely different. From an automated source, pass key: the same key never files twice. note is the problem (what, why, where); plan is how it will be done, when that is known -- keep the two apart. A free board near its limit adds a top-level plan notice (the free plan of the board: tasks left, and upgradeUrl; the plan of the task itself is inside created): tell your user how many are left and give them the upgradeUrl. A refusal with upgradeUrl (a full or read-only board) is the same: relay the message and give them the link.

  ConnectorOAuth

• fenbs_add_decisionA

  fenbsA

  Record a decision, or ask a question for a person to decide. This is also how a RULE is recorded: a rule is a decision that holds from now on (standingRule true). When the person you work for says how something must always, or never, be done, record it here -- status decided, standingRule true, them in deciders, their words quoted in reason -- never as a context note. You may write a decision down; you never make one: record decided only when a person decided it. When nobody has decided yet, add it as open (the default) and ask. To change a rule, record a new decision with supersedes. Search fenbs_list_decisions first. Link the tasks that depend on it with tasks. Needs permission to change tasks.

  ConnectorOAuth

• evictions_update_caseA

  Evictions APIA

  Use this when a draft’s facts need correcting or completing, for example after evictions_validate_case says what is missing. Input: the case `id` and only the fields to change; each one replaces the stored value, and an object such as `property` is replaced whole. Works only on a draft, and `ground` and `entryPoint` cannot change (create a new case instead). Do not use this on a submitted case (use evictions_send_case_message to tell the team what changed). The result is the case, with `state` and `nextAction` (who it is waiting on and for what). Next: evictions_validate_case. Needs the person’s account: sign-in or an API key.

  Connector

  Destructive

  No auth

• cancel_checkoutA

  Custom Blinds ShopA

  Abort an unpaid checkout and release its checkout_id. Use if the customer changes their mind after create_checkout but before completing payment. Has no effect on orders already confirmed by webhook. To restart, create a new cart and checkout from scratch.

  ConnectorNo auth

• cancel_checkoutA

  Custom Blinds ShopA

  Abort an unpaid checkout and release its checkout_id. Use if the customer changes their mind after create_checkout but before completing payment. Has no effect on orders already confirmed by webhook. To restart, create a new cart and checkout from scratch.

  ConnectorNo auth

• submit_job_resultA

  Conductor Relay MCPC

  Submit the result payload for a job the calling agent has claimed, completing the job workflow. Bearer token required. Safe to retry with the same idempotency_key.

  ConnectorNo auth

• query_tasksA

  cnvs.appA

  Read tasks from a 'todo' board with server-side filtering — handy for 'what's overdue?' / 'what's assigned to X?' without pulling the whole board. All filters are optional and AND together: `assignee` (exact match), `priority` ('H'|'M'|'L'), `done` (boolean), `overdue` (true → due_date strictly before today, not done), `due_before` / `due_after` (ISO date window on due_date). Returns `{ boardId, mode, tasks }` — tasks ordered by sort, each with the same fields as `list_tasks`.

  ConnectorNo auth